How faliush/contactmanager works
Project type and purpose
• This is a full-stack, multi-service contact management application.
• BlazorClient – a Blazor WASM/Razor frontend
• IdentityServer – an OAuth2/OpenID Connect auth server (IdentityServer4)
• Faliush.ContactManager.Api – an ASP.NET Core Minimal API following Vertical Slice/CQRS
• Persistence – PostgreSQL via EF Core, plus Redis for caching and RabbitMQ for messaging
• Purpose: let users authenticate, view/create/update/delete “Person” and “Country” entities, with logging, validation, caching, paging.
File structure
• Top-level folders:
• BlazorClient/ – UI project (components, pages, DTOs, custom auth handler, Dockerfile, nginx.conf)
• IdentityServer/ – MVC/Razor auth server (Controllers, Data, ViewModels, Views, migrations, Dockerfile)
• Faliush.ContactManager.Api/ – Minimal API endpoints, Definitions folder for DI, CORS, Serilog, HealthChecks
• Faliush.ContactManager.Core/ – Business logic layer (Commands & Queries per entity, FluentValidation, AutoMapper, OperationResult, DI)
• Faliush.ContactManager.Infrastructure/ – Data access (DbContext, Repositories, UnitOfWork, Migrations, ModelConfiguration)
• Faliush.ContactManager.Models/ – Shared domain models
• Faliush.ContactManager.UnitTests & IntegrationTest – test projects
• docker-compose.yml & per-service Dockerfiles
README for additional insights
• Project Architecture: three services (Client, Auth Server, API)
• API: Vertical Slice, Minimal API, CQRS, Definitions for cross-cutting concerns
• Core: AutoMapper, FluentValidation, Serilog, Caching, OperationResult
• Infra: EF Core + Postgres, UnitOfWork, Pagination