How jamshed34/cleanarchitecturegeneric works
Project Type & Purpose
• This is a backend “Clean Architecture” template for a micro-service/monolith API built on .NET 9, implementing IdentityServer4 for authentication, CQRS via MediatR for business logic, and EF Core (SQL Server) for persistence. It uses .NET Aspire (AppHost) as a lightweight service host/orchestrator.
Core Layers & Directories
• AppHost (src/AppHost)
• Hosts and wires up all services (IdentityServer, Web API).
• Presentation/WebApi (src/Presentation/WebApi)
• Exposes HTTP endpoints (Controllers, Swagger).
• Application (src/Application)
• Business logic: Commands, Queries, DTOs, AutoMapper mappings, MediatR handlers; registered via ApplicationServiceRegistration.
• Domain (src/Domain)
• Core entities (User), interfaces (IUserRepository, IUnitOfWork).
• Infrastructure (src/Infrastructure)
• Data (ApplicationDbContext, EF Migrations, Seed Data), Identity (IdentityServer4 config & migrations), Repositories (UserRepository), plus service registrations (InfrastructureServiceRegistration).
• tests (UnitTests & IntegrationTests)
External Dependencies
• SQL Server (AspNetUsers, AspNetRoles, Clients, PersistedGrants)
• External clients (web front-ends, Postman, mobile apps) consuming the API
• IdentityServer4 endpoints (/connect/token, /.well-known/openid-configuration)
Architectural Patterns & Principles
• Clean Architecture (onion/hexagonal layering): outer layers depend on inner abstractions only.
• CQRS: separate Commands (CreateUserCommand) and Queries (GetUserByIdQuery) handled by MediatR.
• Repository + Unit of Work: Domain interfaces implemented by Infrastructure.
• DI & Orchestration: .NET Aspire in AppHost configures all layers centrally.
• External Clients → (HTTPS + OAuth2) → IdentityServer4 (in AppHost/Infrastructure/Identity)
• External Clients → (Bearer Token) → WebApi Controllers
• Controllers → MediatR → Application Handlers (Commands/Queries)
• Application Handlers → Domain Interfaces (IUserRepository, IUnitOfWork)
• Infrastructure Repositories → EF Core → SQL Server
• AppHost → DI Container → wires Presentation, Application, Infrastructure, IdentityServer