How mohamedroshdyp/chatapp-back works
Project type and purpose
• This is a full-stack .NET Core Chat Application. It exposes a REST/SignalR API (“Presentation/API/ChatApp.API”), implements business logic with a CQRS approach in the Application layer (“src/Core/ChatApp.Application”), defines core domain entities (“src/Core/ChatApp.Domain”), and handles data persistence via Entity Framework Core in the Persistence layer (“src/Infrastructure/ChatApp.Persistence”).
• Features include: user registration/login, profile/photo management, real-time messaging (SignalR hubs), message liking, admin role management, pagination, and JWT/token services.
File structure
• Top‐level solution groups by layer:
• Core
– Domain: Entities & base classes
– Application: CQRS commands/queries, DTOs, validators, mapping profiles, repositories interfaces, dependency‐injection
• Infrastructure
– Persistence: EF Core DbContext, Migrations, Seed data, Repository implementations, token service, photo manager
• Presentation (API)
– Controllers: Accounts, Messages, Likes, Admin
– SignalR: MessageHub, PresenceHub, PresenceTracker
– Program.cs & appsettings
• This layering enforces Clean/Onion architecture: Presentation → Application → Domain → Infrastructure.
• Look for “DependancyInjection” files in Application & Persistence—they register services.
Extract insights from README
• README only contains the title, so rely on file structure and naming conventions to infer the architecture and technologies (ASP.NET Core Web API, EF Core, SignalR, AutoMapper, MediatR-like CQRS).