How beeziniss/ekofycapstone works
Project type and purpose
• This is an ASP .NET Core RESTful API (“EkofyApp.Api”) following a classic layered (hexagonal) architecture.
• Purpose: expose business operations over HTTP, orchestrate domain logic (in the Domain layer), map/use cases and validation (in the Application layer), delegate persistence and external integrations (in the Infrastructure layer), and handle cross-cutting concerns (filters, configuration).
File structure
• Top-level solution contains four projects:
• EkofyApp.Api – the ASP .NET Core Web API project (controllers, HTTP filters, environment loader, appsettings).
• EkofyApp.Application – service interfaces, UnitOfWork abstraction, AutoMapper profiles, DbContext abstractions, and MongoDB settings.
• EkofyApp.Domain – core entities, enums, exceptions, and utility classes.
• EkofyApp.Infrastructure – concrete implementations of repositories/unit‐of‐work, third-party services (Cloudinary), and DI bootstrap.
• Key files:
• DatabaseContext/EkofyDbContext.cs – EF Core or MongoDB context.
• ThirdPartyServices/CloudinaryService – image storage integration.
• DependencyInjection.cs – wiring up Application + Infrastructure into the DI container.
• Filters/BaseExceptionFilter.cs – global exception handling pipeline.