How jcfloresdroid/fisioterapiaback works
Project type and purpose
• This is a single‐solution, layered ASP.NET Core Web API (“fisiolabs_backend”) intended to manage clinical data (patients, appointments, diagnostics, reports).
• It follows a Clean/Onion Architecture style with a “Core” domain/application layer, an “Infrastructure” layer (EF Core), a “Services” layer, and a “Presentation” layer (ASP.NET Core controllers + swagger + static assets).
File structure
• Top‐level projects:
• Core – holds Domain entities, enums, exceptions, DA-Cqrs “Features” (commands/queries), EF Core DbContext/migrations, helper classes.
• Infraestructure (under Core) – ConfigureServices registrations, FisioContext (EF Core), Migrations.
• Services – interface definitions (IAuthService, IUtilPdf, validators) and implementations.
• Validator – FluentValidation rules for commands/queries.
• Presentation – ASP.NET Core Web API project (Controllers, Filters, Program.cs, swagger, static wwwroot assets, Dockerfile).
• Supporting files: global DI configuration (ConfigureServices.cs), appsettings.json, launchSettings, Dockerfile.
README
• Mentions EF Core migrations and database update commands, confirming use of EF Core Code-First.
• No frontend client—presentation layer is purely the Web API plus static swagger UI and image resources.
a. Main components
1. Presentation Layer (API):
• Controllers (e.g., CitaController, UsuarioController)
• Filters (ApiExceptionFilterAttribute)
• Program.cs + ConfigureServices registrations
2. Application Layer (Core/Features + Validators):
• CQRS “Features” subfolders: commands & queries for each bounded context (Pacientes, Citas, Diagnostico, etc.)
• FluentValidation rules in Validator project
3. Domain Layer (Core/Domain):
• Entities (Paciente, Cita, Diagnostico, etc.)
• Enums, Exceptions, Helpers
4. Services Layer (Core/Services):
• Service Interfaces (IAuthService, IUtilPdf, validators)
• Implementations (AuthService, UtilPdf, Validator implementations)
5. Infrastructure Layer (Core/Infraestructure/Persistance):
• EF Core DbContext (FisioContext)
• Migrations
6. Data Store
• Relational database (SQL Server or chosen provider)
7. External/Tools
• EF Core CLI, Docker (Dockerfile in Presentation), Swagger UI
b. Relationships and interactions
• HTTP requests → Presentation.Controllers
• Controller invokes Application Layer by resolving & invoking command/query handlers (via MediatR-style or direct calls)
• Validators execute before command handlers
• Command/query handlers in Application layer manipulate Domain entities & call Services for cross‐cutting concerns (auth, PDF, date utils)
• Services may read/write via Infrastructure’s FisioContext
• Infrastructure layer persists/retrieves Entities to/from the Database
• Errors bubble up to Presentation.Filters for consistent API responses
c. Architectural patterns & principles
• Layered/Clean Architecture: clear separation of concerns, dependencies point inwards (Presentation → Application → Domain).
• CQRS pattern in Application layer: separate “command” and “query” models.
• Dependency Injection across layers (ConfigureServices registers all I* interfaces).
• Validator abstraction using FluentValidation pattern.
• EF Core Code-First for persistence.
d. Relevant technologies
• ASP.NET Core Web API
• Entity Framework Core
• FluentValidation
• Dependency Injection (Microsoft.Extensions.DependencyInjection)
• Docker (containerization)
• Swagger UI (OpenAPI)
Essential elements
• Layer’s responsibility.
• Assemblies/projects (Core.csproj, Presentation.csproj, Services project, Validator project).
• EF Core migrations folder under Infrastructure.
• Dockerfile and swagger-ui static assets under Presentation.