dotnet-architecture

Structure a .NET microservice using Clean Architecture by dividing it into API, Application, Domain, Infra, and Tests projects. This blueprint enforces a strict layered setup to standardize project structures and ensure consistent dependency injection wiring.

Yes, you can implement native CQRS in .NET without MediatR. This architecture demonstrates how to handle commands and queries directly within the Application layer, reducing external dependencies while maintaining strict separation of concerns.

Organize .NET Domain and Infra layers by isolating business logic in the Domain layer and implementing data access via the repository pattern in Infra. This separation enforces dependency inversion and uses EF Core for data operations.

Set up global exception handling and validation by configuring DI wiring in the API layer and integrating FluentValidation in the Application layer. This ensures consistent error handling across the entire .NET project structure.

Apply the repository pattern with EF Core when you need to abstract data access and centralize query logic within the Infra layer. This is especially useful when restructuring large legacy projects into a standardized layered setup.

No specific external dependencies are required to start. The blueprint relies on native .NET patterns for CQRS and DI, while providing integration samples for EF Core and FluentValidation to guide your implementation.