02-modular-project-structure

What problem does it solve?

EN: A domain-first backend structure clarifies boundaries so a teammate can open a domain folder (e.g., catalog, billing, identity, notifications) and immediately understand where requests enter, where business rules live, where data access happens, and where tests belong. ES: Un backend orientado a dominios clarifica las fronteras para que un compañero pueda abrir una carpeta de dominio (por ejemplo, catalogo, facturación, identidad, notificaciones) e entender de inmediato dónde entran las solicitudes, dónde viven las reglas de negocio, dónde ocurre el acceso a datos y dónde pertenecen las pruebas.

Core Features & Use Cases

• Per-domain module with a clear entry point and public boundary.
• Keeps controller/handler, service/use-case, repository, DTOs, entities, and tests together in the same domain.
• Supports scalable depth by adding transport/, application/, domain/, and infrastructure/ subfolders as the project grows.

Quick Start

Create one folder per business area under the source root (e.g., src/modules/ or src/features/) and place the domain's controller, service, repository, DTOs, entities, and tests beside each other.