A Clean Architecture solution template for ASP.NET Core with Angular, React, or Web API options, powered by Aspire.
Clean Architecture Solution Template is a .NET project template that provides a structured foundation for building enterprise applications using Clean Architecture principles with ASP.NET Core. It enables developers to quickly generate solutions with optional Angular or React frontends, multiple database providers, and integrated testing frameworks. The template addresses the complexity of setting up a maintainable, scalable architecture from scratch.
Enterprise developers and teams building ASP.NET Core applications who want to adopt Clean Architecture patterns without extensive initial setup. It's ideal for those creating new projects that require separation of concerns, testability, and modern frontend integration.
Developers choose this template because it offers a production-ready, opinionated starting point that enforces best practices and reduces boilerplate. Its flexibility in frontend and database choices, combined with Aspire integration for cloud-native development, provides a comprehensive solution that accelerates project kickoff while maintaining architectural integrity.
Clean Architecture Solution Template for ASP.NET Core
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports Angular, React, or API-only setups, allowing teams to choose based on expertise without extra configuration, as highlighted in the multi-framework support feature.
Offers SQLite, PostgreSQL, and SQL Server options, enabling easy switching and local development with defaults like SQLite, per the database flexibility section.
Includes NUnit, Shouldly, Moq, and Respawn for unit and integration testing, reducing setup time and enforcing testability from the start.
Integrated with .NET Aspire for orchestration and cloud-native patterns, streamlining deployment and monitoring in modern environments.
Enforces Clean Architecture principles with layered projects, which can be overwhelming for teams new to this pattern, requiring significant onboarding time.
Relies on multiple third-party libraries (e.g., MediatR, AutoMapper), increasing maintenance risks and potential compatibility issues with updates.
Only supports Angular and React, excluding other popular options like Vue.js or Svelte, which may force teams into a specific technology stack.