How smart86029/deopeia works
Project type and purpose
• Deopeia is a .NET practice project built on a microservices architecture.
• It consists of a user-facing Vue3 Single-Page Application (SPA), a backend-for-frontend service (BFF), two domain services (Identity and Product), shared libraries, and hosting infrastructure.
File-structure analysis
• Top-level solution (Deopeia.slnx) aggregates all projects under src.
• src/AdminPortal/Web holds the Vue3 SPA.
• src/AdminPortal/Bff contains the .NET Core Web API acting as a BFF.
• src/Identity/Deopeia.Identity.Api and src/Product/Deopeia.Product.Api are two independent ASP.NET Core microservices.
• src/Common, src/Deopeia.ServiceDefaults, and src/Deopeia.AppHost implement shared frameworks, defaults, and hosting abstractions used by all services.
• Each microservice follows a layered pattern:
• API (Controllers, Endpoints)
• Application (Commands, Queries, Handlers)
• Domain (Entities, Repositories, Domain Events)
• Infrastructure (EF Core/Dapper configurations, migrations, repository implementations)
README insights
• Confirms a .NET microservices practice.
Detail
• Don’t over-abstract: show every service and database as its own component.
• Inter-service boundaries, shared-kernel modules, and external dependencies (object storage).