How feriel214/asp.net-core-cleanarchitecture-cqrs-identity works
Project type and purpose
• This is an ASP.NET Core 8.0 Web API implementing Clean Architecture with CQRS (commands/queries via MediatR), Identity for role and user management, JWT authentication/authorization, Entity Framework Core (for migrations & identity tables), and Dapper (for optimized queries).
• Its purpose is to expose endpoints (AuthController, UserController, RoleController) for clients to perform authentication, user, and role operations against a SQL Server database.
File structure
• Top-level solution “Authentication.sln” contains four main projects:
• Naxxum.JobyHunter.Authentication.Api: the Web API entry point (Controllers, Program.cs, appsettings.json).
• Naxxum.JobyHunter.Authentication.Application: application‐level logic (CQRS commands & queries, DTOs, dependency injection).
• Naxxum.JobyHunter.Authentication.Domain: domain entities (User, Role via BaseEntity), repository interfaces for commands/queries.
• Naxxum.JobyHunter.Authentication.Infrastructure: concrete implementations (EF Core DbContext, Migrations, Dapper/EF repositories, IdentityService, TokenGenerator).
• There’s also a UnitTests project for testing Application & Domain layers.
README for additional insights
• Clean Architecture pattern separates concerns into independent layers.
• CQRS: Commands (write) and Queries (read) classes under Application/Commands and Application/Queries.
• Uses EF Core and Dapper in Infrastructure, AutoMapper for mapping, MediatR for dispatching commands/queries, JWT for token-based security.
Detail without over-complicating
• API: Controllers (Auth, User, Role), appsettings.json
• Application: Commands, Queries, DTOs, DependencyInjection.cs
• Domain: Entities, IRepository interfaces
• Infrastructure: ApplicationDbContext & Migrations, CommandRepository, QueryRepository, IdentityService, TokenGenerator
• Data flow for both a write operation (e.g., CreateUserCommand) and a read operation (GetUserQuery) to illustrate CQRS.