How fpt-uni-team/focs-be---cafeteria-ordering-system works
Project type and purpose
• This is a .NET-based, API-driven food-ordering and coupon management system with a “clean/onion” architecture.
• It exposes REST endpoints (FOCS project), implements business logic in a separate Application layer, persists data via multiple context-specific infrastructure projects (Identity, Order), provides real-time updates via SignalR (FOCS.Realtime.Hub), and background/messaging-based notifications (FOCS.NotificationService).
File structure
• Top-level solution (“FOCS.sln”) with multiple projects:
• FOCS – ASP.NET Web API (Controllers, Middleware, Program.cs)
• FOCS.Application – DTOs, service interfaces & implementations, background services
• FOCS.Common – shared constants, enums, models, interfaces, helpers
• FOCS.Infrastructure.Identity – Identity DB context, repositories, migrations, user models
• FOCS.Order.Infrastucture – Order DB context, entity models, migrations
• FOCS.Realtime.Hub – SignalR hubs for cart & order events
• FOCS.NotificationService – a worker process consuming messages and sending push notifications
• Deployment artifacts: Dockerfile, docker-compose.yml, GitHub Actions workflow
Elements
– Clear component labels (e.g., “FOCS Web API”, “Order DbContext”, “SignalR CartHub”)
• Layers (e.g., blue for API, green for Application, orange for Infrastructure)