How eospinam/pruebafinanzauto works
Project type and purpose
• This is a .NET solution implementing a clean-architecture (onion/hexagonal) backend API (“Finanzauto”).
• It exposes REST endpoints for authentication, and CRUD operations on Students, Teachers, Courses, Notes, and their relationships.
File structure
• Top-level solution file (PruebaFinanzauto.sln) groups four projects:
• PruebaFinanzauto.Api – the ASP.NET Core Web API (controllers, HTTP, launch settings)
• PruebaFinanzauto.Application – application layer (DTOs, interfaces, services, AutoMapper profiles)
• PruebaFinanzauto.Domain – domain layer (entities)
• PruebaFinanzauto.Infrastructure – infrastructure layer (EF Core DbContext, migrations, repository implementations)
• Controllers receive HTTP, call services in the Application layer via injected interfaces.
• Services orchestrate business logic, map between domain entities and DTOs, and call repository interfaces.
• Repository implementations in Infrastructure use Entity Framework Core to persist the Domain entities to a relational database.
README
• The README is minimal, so rely on the file structure and naming conventions for insights into architecture and tech stack.