How maheshkumarsingh/meetyourmatch works
Project Type & Purpose
• This is a full-stack dating web application (“MeetYourMatch”) combining an Angular 18 single-page frontend with an ASP.NET Core 8 Web API backend.
• It offers user registration/login, role-based access, photo uploads (via Cloudinary), real-time chat/presence (SignalR), and persistent data storage (SQL via EF Core).
High-Level File Structure Analysis
• Top level:
• API/ – ASP.NET Core Web API project
• README.md, MeetYourMatch.sln – solution and documentation
• API/Controllers – HTTP endpoints (Account, Users, Messages, Likes, Admin, Fallback)
• API/ServiceContracts & Services – service interfaces and implementations (Repository, UnitOfWork, TokenService, PhotoService)
• API/Data – DbContext, migrations, seed data (EF Core with SQL scripts & JSON seed)
• API/Entities & DTOs – domain models (AppUser, AppRole, Message, Photo, Like, Group/Connection) and data transfer objects
• API/SignalR – real-time hubs (MessageHub, PresenceHub) and trackers
• API/Helpers & Extensions – AutoMapper profiles, pagination, JWT/Identity extensions, middleware (global error handling)
• API/wwwroot – Angular build output (static SPA) hosted by .NET
• Configuration: appsettings.json, launchSettings, Azure Web Deploy profiles
README Insights
• Confirms Angular frontend and .NET backend separation with outputPath directed to API/wwwroot
• Highlights tech stack: Angular CLI, RxJS, Bootstrap/ngx-bootstrap, SignalR; ASP.NET Core Identity, JWT, EF Core, AutoMapper, Cloudinary, Azure App Service.
• Deployment on Azure (Linux/Windows), CI/CD via GitHub Actions (.github/workflows).
1. Angular 18 Frontend (Client SPA)
2. ASP.NET Core 8 Web API
– Controllers (REST endpoints)
– Business/Domain Layer (Services & UnitOfWork)
– Data Access Layer (Repositories & EF Core DbContext)
– SignalR Hubs (MessageHub, PresenceHub)
– Middleware (Exception, Authentication)
3. SQL Database (Azure SQL / Local SQL Server)
4. Cloudinary (Photo storage)
5. External Identity (JWT token issuing via IdentityService)
6. CI/CD Pipeline (GitHub Actions → Azure App Service)
• Browser → (HTTPS requests) → Angular SPA assets (served from API/wwwroot)
• Angular → (REST/HTTP + JWT in headers) → API Controllers → Services → Repositories → SQL DB
• Angular ↔ (SignalR over WebSockets) ↔ MessageHub & PresenceHub → PresenceTracker & Group management → Broadcast to connected clients
• API → Cloudinary SDK/API calls for photo upload/download
• GitHub Actions → Azure App Service (deploy Angular build & .NET API)
c. Architectural Patterns & Design Principles:
• Layered (Presentation → API → Services → Repositories → Database)
• Repository + Unit of Work for data persistence
• DTOs + AutoMapper for data shaping between layers
• Middleware for cross-cutting concerns (error handling, logging, JWT validation)
• Real-time pub/sub via SignalR hubs
• Dependency Injection throughout ASP.NET Core
d. Key Technologies & Frameworks:
• Frontend: Angular 18, RxJS, ngx-bootstrap, ngx-toastr, ng-gallery, Bootstrap 5, Font Awesome
• Backend: ASP.NET Core 8, EF Core 8, ASP.NET Core Identity, JWT, AutoMapper, SignalR
• Storage: Azure SQL (or local SQL), Cloudinary (image hosting)
• Infrastructure: Azure App Service, GitHub Actions CI/CD