screaming-architecture

Screaming architecture organizes a project structure into domain-first boundaries, making the system's business purpose obvious by naming top-level folders after business capabilities rather than technical layers like controllers or services.

To structure a project by domain, create a domain-first root using top-level folders named after business capabilities. Ensure feature self-containment so each domain package owns its models, services, routes, and tests independently.

Refactor to a domain-driven folder structure when starting a new project or reorganizing a large codebase. It is ideal for teams needing to reflect real business boundaries and enforce framework-at-the-edge separation.

Yes, domain-first architecture provides framework-at-the-edge guidance. It keeps framework-specific code isolated at the outer layers while ensuring the core domain logic remains completely framework-free.

The best way to organize folders around business capabilities is enforcing feature self-containment. Each domain package should own its models, services, routes, and tests, ensuring the root structure screams the system's intent.

Yes, screaming architecture applies to major refactors of existing projects. It transforms the current project layout into domain-first boundaries, reorganizing the codebase around core business concepts to reduce confusion.