clean-architecture

Structure a NestJS module using clean architecture by separating domain, application, and infrastructure layers. This blueprint enforces domain-layer purity, explicit dependency injection via factories, and consistent boundaries for controllers, modules, and repository adapters.

The best way to keep domain logic pure is to prohibit framework imports within the domain layer. This blueprint enforces layer rules where domain interfaces remain independent, utilizing infrastructure factories for wiring and repository adapters.

Yes, this clean architecture blueprint works with Drizzle ORM. It provides reference implementation patterns for use with NestJS and Drizzle ORM in a TypeScript monorepo setup, ensuring scalable and testable backend components.

Migrate an existing backend module to clean architecture by applying this canonical blueprint to standardize directory layout and wiring. It guides module review and migration tasks to ensure explicit dependency injection and clear infrastructure boundaries.

No, you do not need external dependencies beyond TypeScript to enforce clean architecture in NestJS. This blueprint requires no runtime dependencies, relying instead on a reference implementation pattern using domain interfaces and factory providers.