# jcfloresdroid/fisioterapiaback architecture

> Architecture diagram of the GitHub repository jcfloresdroid/fisioterapiaback, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2025-05-26). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/jcfloresdroid/fisioterapiaback
- Repository: https://github.com/jcfloresdroid/fisioterapiaback

## Overview

##### 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.

## Diagram (Mermaid)

```mermaid
flowchart TD
    %% External Tools
    subgraph "External/Tools"
        EFCLI["EF Core CLI"]:::external
        DockerTool["Docker"]:::external
        SwaggerUI["Swagger UI"]:::external
    end

    %% Presentation Layer
    subgraph "Presentation Layer"
        Controllers["Controllers"]:::presentation
        Filters["ApiExceptionFilterAttribute"]:::presentation
        Program["Program.cs"]:::presentation
        ConfigServ["ConfigureServices.cs"]:::presentation
        SwaggerAssets["Swagger UI Static Assets"]:::presentation
        Dockerfile["Dockerfile"]:::presentation
    end

    %% Application Layer
    subgraph "Application Layer"
        Features["CQRS Features"]:::application
        ValidatorApp["FluentValidation Rules"]:::application
    end

    %% Domain Layer
    subgraph "Domain Layer"
        Entities["Domain Entities"]:::domain
        Enums["Enums"]:::domain
        Exceptions["Exceptions"]:::domain
        Helpers["Helpers"]:::domain
    end

    %% Services Layer
    subgraph "Services Layer"
        Interfaces["Service Interfaces"]:::services
        Implementations["Service Implementations"]:::services
    end

    %% Infrastructure Layer
    subgraph "Infrastructure Layer"
        DIInfra["Infrastructure DI Config"]:::infrastructure
        DbContext["FisioContext (DbContext)"]:::infrastructure
        Migrations["Migrations"]:::infrastructure
    end

    %% Data Store
    DB["Relational Database"]:::database

    %% Connections
    EFCLI -->|runs migrations| Migrations
    DockerTool -->|containerizes| Controllers
    SwaggerUI -->|served by| Controllers

    %% Request flow
    Clients["HTTP Clients"]:::external -->|HTTP Request| Controllers
    Controllers -->|Invoke Commands/Queries| Features
    Features -->|Validates via| ValidatorApp
    ValidatorApp -->|Validation Passed| Features
    Features -->|Uses Entities| Entities
    Features -->|Calls Services| Interfaces
    Interfaces -->|Implemented by| Implementations
    Implementations -->|EF Core Calls| DbContext
    DbContext -->|Reads/Writes| DB

    %% DI Flow
    Controllers -->|Configured by| ConfigServ
    ConfigServ -->|Registers Services| Interfaces
    ConfigServ -->|Registers DbContext| DbContext

    %% Swagger Assets and Dockerfile
    Controllers -->|Serves| SwaggerAssets
    Controllers -->|Docker setup| Dockerfile

    %% Class Definitions
    classDef presentation fill:#cce5ff,stroke:#3399ff,stroke-width:1px;
    classDef application fill:#d4edda,stroke:#28a745,stroke-width:1px;
    classDef domain fill:#fff3cd,stroke:#ffcd39,stroke-width:1px;
    classDef infrastructure fill:#ffe5b4,stroke:#ff8c00,stroke-width:1px;
    classDef services fill:#e2d5f7,stroke:#6f42c1,stroke-width:1px;
    classDef external fill:#f0f0f0,stroke:#999999,stroke-width:1px;
    classDef database fill:#d1ecf1,stroke:#17a2b8,stroke-width:1px;

    %% Click Events - Presentation
    click Controllers "https://github.com/jcfloresdroid/fisioterapiaback/tree/main/Presentation/Controllers"
    click Filters "https://github.com/jcfloresdroid/fisioterapiaback/blob/main/Presentation/Filters/ApiExceptionFilterAttribute.cs"
    click Program "https://github.com/jcfloresdroid/fisioterapiaback/blob/main/Presentation/Program.cs"
    click ConfigServ "https://github.com/jcfloresdroid/fisioterapiaback/blob/main/Presentation/ConfigureServices.cs"
    click SwaggerAssets "https://github.com/jcfloresdroid/fisioterapiaback/tree/main/Presentation/wwwroot/swagger-ui"
    click Dockerfile "https://github.com/jcfloresdroid/fisioterapiaback/tree/main/Presentation/Dockerfile"

    %% Click Events - Application
    click Features "https://github.com/jcfloresdroid/fisioterapiaback/tree/main/Core/Features"
    click ValidatorApp "https://github.com/jcfloresdroid/fisioterapiaback/tree/main/Core/Validator"

    %% Click Events - Domain
    click Entities "https://github.com/jcfloresdroid/fisioterapiaback/tree/main/Core/Domain/Entities"
    click Enums "https://github.com/jcfloresdroid/fisioterapiaback/tree/main/Core/Domain/Enum"
    click Exceptions "https://github.com/jcfloresdroid/fisioterapiaback/tree/main/Core/Domain/Exceptions"
    click Helpers "https://github.com/jcfloresdroid/fisioterapiaback/tree/main/Core/Domain/Helpers"

    %% Click Events - Services
    click Interfaces "https://github.com/jcfloresdroid/fisioterapiaback/tree/main/Core/Services/Interfaz"
    click Implementations "https://github.com/jcfloresdroid/fisioterapiaback/tree/main/Core/Services/Implementacion"

    %% Click Events - Infrastructure
    click DIInfra "https://github.com/jcfloresdroid/fisioterapiaback/blob/main/Core/Infraestructure/ConfigureServices.cs"
    click DbContext "https://github.com/jcfloresdroid/fisioterapiaback/blob/main/Core/Infraestructure/Persistance/FisioContext.cs"
    click Migrations "https://github.com/jcfloresdroid/fisioterapiaback/tree/main/Core/Infraestructure/Persistance/Migrations"
```
