How trycatchlearn/datingapp-dotnet8angular18 works
Project type and purpose
• This is a full-stack web application—a social/dating platform—built with an Angular 17 front end and a .NET 8.0 back end.
• Core features include user registration/login (JWT auth), member browsing, photo uploads (Cloudinary), real-time messaging (SignalR), likes, admin photo approval, pagination, and role-based access control.
File structure
• Top-level directories:
• API – ASP.NET Core Web API project, organized by layers (Controllers, DTOs, Data, Entities, Services, SignalR, Middleware, Extensions, Helpers, Interfaces).
• client – Angular SPA with modules for components (_services, _guards, _interceptors, _models, _resolvers, feature folders).
• docker-compose.yml – defines multi-container setup (API, database).
• Data access: EF Core DataContext, Repositories (LikesRepository, MessageRepository, PhotoRepository, UserRepository), UnitOfWork.
• Business logic: Services (TokenService, PhotoService), AutoMapper profiles.
• API surface: Controllers (Account, Users, Likes, Messages, Admin) expose REST endpoints.
• Real-time layer: SignalR hubs (MessageHub, PresenceHub).
• Client bootstraps via index.html, main.ts, app.routes.ts, and uses Bootstrap for styling.
README for additional insights
• Confirms the tech stack (.NET 8.0, Angular 17/18, Bootstrap 5).
• Mentions newer/older versions for reference—implies the architecture is stable across versions.
a. Main components:
• Angular SPA (Browser)
• ASP.NET Core API
• EF Core / SQL Database
• SignalR Hub (inside API)
• Cloudinary (external photo storage)
• Authentication/Authorization (JWT token service)
• Docker Compose orchestration
b. Relationships and interactions:
– Browser ↔ API: REST calls (HTTP/HTTPS) for CRUD operations, JWT in Authorization header.
– Browser ↔ API: WebSocket connection to SignalR for real-time chat/presence.
– API → Database: EF Core issues SQL queries to read/write Entities.
– API → Cloudinary: PhotoService uploads/downloads images.
– API Middleware pipeline: ExceptionHandling → Logging → Authentication/Authorization → Routing → Controllers.
c. Architectural patterns/design principles:
– Layered Architecture: Controllers → Services → Repositories → DataContext
– Repository & Unit of Work patterns for data access
– DTO mapping via AutoMapper for separation between domain and API models
– Middleware pipeline in ASP.NET Core for cross-cutting concerns
– SPA pattern in Angular with Services/Guards/Interceptors for auth and error handling
– Real-time communication via SignalR hubs
d. Key technologies/frameworks/libraries:
– Back end: ASP.NET Core 8.0, EF Core, AutoMapper, SignalR, Cloudinary SDK, JWT Bearer Auth
– Front end: Angular 17, RxJS, Angular Router, Bootstrap 5, Angular Guards/Interceptors
– DevOps: Docker, Docker Compose, SQL Server container