microservice-architecture-ai-kit

What problem does it solve?

It helps you structure .NET microservices so teams stay maintainable as complexity grows, preventing broken dependencies between API, Application, Domain, Infrastructure, and (optionally) Persistence.

Core Features & Use Cases

• Clean Architecture + CQRS microservice blueprint: Enforces layer separation and CQRS patterns using Mediator (commands/queries/handlers).
• Versioned REST API + controller conventions: Standardizes v{version}/routing and controller behavior via shared conventions.
• Dependency injection per layer: Supports per-layer Add* registration (Api/Application/Infrastructure/Persistence) to keep wiring consistent.
• Architectural test guardrails: Uses architectural tests (e.g., NetArchTest) to validate layer dependency rules before changes land.
• Database-aware guidance: Provides explicit persistence integration points (EF Core context interface/implementation, configurations, migrations) when a database is included.

Use it when you are building a domain-owning backend service that persists data (EF Core) and exposes APIs to other services or a BFF, and you want consistent structure plus automated architectural enforcement.

Quick Start

Ask for a ready-to-implement solution structure by saying: "Generate a Clean Architecture + CQRS .NET microservice skeleton for an AssetPrice domain using Mediator, versioned controllers, per-layer Add* DI, and architectural dependency tests, including EF Core persistence when a database is required."