How ibrahimkahramann/dotnet-dietitian works
Main System Components
a. Client UI (Web/Mobile)
b. API Layer (Dotnet-Dietitian.API)
c. Application Layer (Dotnet-Dietitian.Application)
d. Domain Layer (Dotnet-Dietitian.Domain)
e. Persistence Layer (Dotnet-Dietitian.Persistence)
f. Infrastructure Layer (Dotnet-Dietitian.Infrastructure)
g. External Services & Infrastructure
• Relational Database (EF Core)
• MongoDB (NoSQL)
• Redis (Caching)
• RabbitMQ (Message Bus/ESB)
• SignalR (Real-time Notifications)
• Authentication (JWT Issuer)
Relationships & Data Flows
• Client UI → HTTP/HTTPS → API Layer Controllers
• Controllers → (via DI) → Application Layer’s Mediator (Commands & Queries)
• Mediator Handlers → Domain Entities + Services → Persistence Repositories
• Repositories → EF Core DbContext → SQL Database
• Repositories may also connect to MongoDB for document storage
• Caching layer (Redis) is consulted by Services/Repositories for hot data
• Domain events or integration events published → RabbitMQ → other services
• API Layer hosts SignalR Hubs → push notifications to Client UI
• Authentication middleware validates JWT tokens on incoming requests
Architectural Patterns & Principles
• Onion Architecture: concentric rings (API → Application → Domain → Infrastructure)
• CQRS & Mediator: separate read/write Models, Commands & Queries handled by Mediator
• SOLID: each layer and class has a single responsibility
• Repository Pattern: Persistence abstractions in Application.Interfaces, implemented in Persistence
• Dependency Injection: ServiceCollectionExtensions wiring all services
Technologies & Frameworks
• ASP.NET Core Web API (Controllers, Middleware)
• MediatR or Custom Mediator (in Application.Features.Mediator)
• Entity Framework Core (Dotnet-Dietitian.Persistence)
• MongoDB & Redis (configured in Infrastructure/Services or DI extensions)
• JWT Authentication (Infrastructure/Services/JwtTokenGenerator + Application.Tools)
• SignalR Hubs (in API Layer)
• RabbitMQ Client Libraries (for ESB/integration events)
Final Checklist
• JWT Authentication flow: client login → AuthController → JwtTokenGenerator → token returned