architecture-advisor

Choosing the right .NET architecture requires assessing domain complexity, team size, system lifetime, and integration patterns. A structured questionnaire evaluates these requirements to recommend the best-fit architecture, preventing misaligned structural decisions before scaffolding begins.

Vertical Slice Architecture suits simple applications where Clean Architecture introduces unnecessary ceremony. Use Clean Architecture or DDD + Clean Architecture when domain complexity, compliance boundaries, and system scale demand stricter separation of concerns and explicit domain boundaries.

A Modular Monolith is an architectural style organizing a single deployment into independent modules. It is recommended for .NET projects needing strict module boundaries and domain isolation without the operational complexity of distributed microservices.

Yes, DDD + Clean Architecture is explicitly recommended for complex .NET systems. It combines strict domain-driven design boundaries for complex business logic with the dependency inversion and layered structure of Clean Architecture to maintain long-term maintainability.

Applying Clean Architecture to simple CRUD operations introduces unnecessary abstraction layers and boilerplate, creating an anti-pattern. It overcomplicates basic data access, reducing development speed without providing meaningful architectural benefits for straightforward domain logic.