nestjs

Structure NestJS applications by applying hexagonal architecture and CQRS patterns to separate concerns across API controllers, application commands and queries, domain entities, and infrastructure adapters. This modular structure maintains clear boundaries and improves testability for scalable API backends.

The best way to separate reads and writes in a NestJS backend is using CQRS patterns. This Skill implements distinct command and query buses, isolating write operations in application commands and read operations in application queries to optimize scalability and maintainability.

Use ports and adapters in a NestJS project when you need to abstract external services behind ports and implement flexible adapters. This hexagonal architecture approach isolates infrastructure dependencies, ensuring your domain entities remain testable and independent from external service implementations.

Yes, this Skill provides a guided directory layout example separating modules into api/controllers, application/commands and queries, domain/entities, and infrastructure adapters. It includes a sample Users feature demonstrating a controller, command, query, and in-memory adapter.

Implementing hexagonal architecture in NestJS typically requires manual module setup to define boundaries, but this Skill provides a guided structure and sample Users feature to accelerate the process. It establishes clear separation between API, application, domain, and infrastructure layers automatically.

Separating domain logic from infrastructure matters in NestJS backends because it enforces clear separation of concerns, ensuring scalable module boundaries. This isolation prevents infrastructure changes from affecting core domain entities and significantly improves overall application testability.