Sairyss/domain-driven-hexagon
This system is a NestJS-based application implementing Domain-Driven Design principles, specifically utilizing CQRS and event-driven architecture. It manages user and wallet domains, supporting data operations via HTTP, GraphQL, CLI, and message queues. The codebase enforces strict architectural boundaries and uses modern tooling like Zod for validation and Slonik for database interactions.
48.8
Weak · 4 August 2026
5.5k
lines of production code
TypeScript
with JavaScript
1
bus factor · 21 authors in all
3
measurements over time
How it got here
2020 · User module refactoring and architecture simplification
This period focused on stripping away legacy abstractions, base classes, and HTTP controllers to simplify the user module's architecture. The team migrated the database layer from TypeORM to Slonik, introduced GraphQL support, and enforced stricter architectural boundaries and validation rules.
17 changes
2021 · User and wallet domain modeling
This period focused on implementing core user and wallet functionality, including creating, deleting, and querying users via multiple interfaces (CLI, HTTP, GraphQL). It also introduced structured exception handling, TypeScript utility types, and automatic wallet provisioning upon user registration.
11 changes
2022 · Domain-Driven Design and API standardization
This period focused on establishing the foundational architecture for the application, introducing Domain-Driven Design patterns and standardized API response structures. The work included implementing core domain models for users and wallets, setting up database migrations, and creating shared test utilities to support these new components.
8 changes
Survey your own repository
Sairyss/domain-driven-hexagon was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point the surveyor at a repository you know and see whether you agree with it.
About this page
- The description of this project is derived from its own commit history, not from its README.
- The score is its highest published measurement, taken on 4 August 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit 5c2d15a7e2 — the exact code this score is about.
- Scored under rubric rubric-2026.08.19. Score the same commit under that rubric and you get the same number.