microservice-architecture-ai-kit

Structure a .NET Clean Architecture microservice by separating API, Application, Domain, Infrastructure, and Persistence layers, using Mediator for CQRS command/query handler patterns. This enforces strict layer dependencies and consistent controller conventions to keep backend services maintainable as complexity grows.

Prevent invalid cross-layer dependencies in a .NET microservice by using architectural tests like NetArchTest to validate layer dependency rules before changes land. This automated guardrail ensures API, Application, Domain, and Infrastructure layers remain strictly separated during development.

Clean Architecture works with EF Core persistence in microservices by providing explicit persistence integration points, including EF Core context interfaces, implementations, configurations, and migrations. The per-layer dependency injection registration keeps database wiring consistent across the Domain and Infrastructure layers.

The best way to enforce CQRS patterns with Mediator in .NET is to standardize command/query/handler implementations across the Application layer. Combined with per-layer Add* dependency injection registration, this maintains consistent Mediator wiring and separates read operations from write operations effectively.

Set up versioned REST APIs in a .NET Clean Architecture project by standardizing v{version}/ routing and controller behavior via shared conventions. This ensures consistent API exposure across microservices that communicate with other services or a Backend-for-Frontend.

You need architectural testing for microservices when building domain-owning backend services and want automated enforcement of layer dependency rules. It validates that API, Application, Domain, and Infrastructure layers maintain strict separation before code changes land in the repository.