# jobs2306/pruebacompuslands architecture

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

- Interactive diagram: https://gitdiagram.com/jobs2306/pruebacompuslands
- Repository: https://github.com/jobs2306/pruebacompuslands

## Overview

##### Main Components
- API Layer (Controllers): Representing endpoints for authentication (AuthController), client management (ClientesController), order management (PedidoController), order–product relationships (PedidoProductosController), and product management (ProductoController).
- Service Layer: Contains business logic implemented in the Service folder with corresponding interfaces in Service/Interface. This layer processes requests coming from the controllers.
- Data Access Layer: Built around Entity Framework Core. Include the ApplicationDbContext (in the Data folder), the Models (clientes, productos, pedidos, pedidoProductos), and migrations for the database schema.
- External Dependencies:
- MySQL Database: As defined in appsettings.json and docker-compose.
- Authentication Component: Note the JWT-based authentication mechanism, which validates login credentials and assigns roles.
- Deployment/Containerization: Include Docker configuration aspects such as the Dockerfile and docker-compose.yml which illustrate how the application and the MySQL DB are containerized.

##### Relationships and Interactions
- The API layer (Controllers) receives HTTP requests and then passes these to the Service Layer after validating authentication tokens.
- The Service Layer encapsulates core business logic and communicates with the Data Access Layer (EF Core DB context) to perform CRUD operations.
- The Data Access Layer interacts with the MySQL database, as configured through connection strings.
- The JWT authentication process provides security, interacting with the API endpoints to issue and validate tokens.
- Docker orchestrates containerized deployment, ensuring the API service and the MySQL database work together in different containers (as specified in docker-compose).

##### Architectural Patterns and Design Principles
- Layered (n-tier) Architecture: Separation between Controllers (presentation), Services (business logic), and Data Access (persistence).
- Dependency Injection: Evident through the use of service interfaces and implementations, allowing for modularity and easier testing.
- Containerization: With Docker for deployment, promoting consistency across environments.
- RESTful API practices: Clearly defined endpoints that handle CRUD operations.

##### Relevant Technologies and Frameworks
- ASP.NET Core for the web framework.
- Entity Framework Core for the ORM.
- MySQL as the database system.
- JWT for authentication and authorization.
- Docker and docker-compose for containerization and deployment.

##### Putting It All Together
- Them to the API layer (Controllers) with HTTP requests.
- Finally, illustrate the connection between the Data Access layer and the MySQL database (within its Docker container), highlighting the network communication.
- Additionally, include a side view or annotation for Docker, indicating that both the API and MySQL are deployed in their own containers as orchestrated by docker-compose.

## Diagram (Mermaid)

```mermaid
graph TB
    %% External Client
    Clients("Clients / Postman"):::external

    %% API Layer (Controllers)
    subgraph "API Layer (Controllers)"
        AuthController("AuthController"):::api
        ClientesController("ClientesController"):::api
        PedidoController("PedidoController"):::api
        PedidoProductosController("PedidoProductosController"):::api
        ProductoController("ProductoController"):::api
    end

    %% Service Layer
    subgraph "Service Layer"
        IClientesService("IClientesService"):::service
        IPedidoService("IPedidoService"):::service
        IPedidoProductoService("IPedidoProductoService"):::service
        IProductoService("IProductoService"):::service

        ClienteService("ClienteService"):::service
        PedidoService("PedidoService"):::service
        PedidoProductoService("PedidoProductoService"):::service
        ProductoService("ProductoService"):::service
    end

    %% Data Access Layer
    subgraph "Data Access Layer"
        ApplicationDbContext("ApplicationDbContext"):::data
        ClientesModel("Clientes Model"):::data
        ProductosModel("Productos Model"):::data
        PedidosModel("Pedidos Model"):::data
        PedidoProductosModel("PedidoProductos Model"):::data
        Migrations("Migrations"):::data
    end

    %% Deployment/Containerization
    subgraph "Deployment/Containerization"
        Dockerfile("Dockerfile"):::docker
        DockerCompose("docker-compose.yml"):::docker
        AppSettings("appsettings.json/appsettings.Development.json"):::docker
        MySQLDB("MySQL Database"):::docker
    end

    %% JWT Authentication Component (represented via AuthController)
    JWT("JWT Authentication"):::api

    %% Connections
    Clients -->|"HTTP_Request"| AuthController

    %% JWT token issuance for authentication (side connection)
    JWT ---|"issues_token"| AuthController

    %% From Controllers to corresponding Service implementations
    ClientesController -->|"calls"| ClienteService
    PedidoController -->|"calls"| PedidoService
    PedidoProductosController -->|"calls"| PedidoProductoService
    ProductoController -->|"calls"| ProductoService

    %% Service Interfaces implementation mapping
    IClientesService -->|"implements"| ClienteService
    IPedidoService -->|"implements"| PedidoService
    IPedidoProductoService -->|"implements"| PedidoProductoService
    IProductoService -->|"implements"| ProductoService

    %% Service implementations call the Data Access Layer
    ClienteService -->|"uses"| ApplicationDbContext
    PedidoService -->|"uses"| ApplicationDbContext
    PedidoProductoService -->|"uses"| ApplicationDbContext
    ProductoService -->|"uses"| ApplicationDbContext

    %% Data Access interacts with Models
    ApplicationDbContext -->|"manages"| ClientesModel
    ApplicationDbContext -->|"manages"| ProductosModel
    ApplicationDbContext -->|"manages"| PedidosModel
    ApplicationDbContext -->|"manages"| PedidoProductosModel

    %% Data Access to MySQL Database
    ApplicationDbContext -->|"CRUD"| MySQLDB

    %% Deployment connections (Docker Compose orchestrates containers)
    DockerCompose ---|"orchestrates"| Dockerfile
    DockerCompose ---|"orchestrates"| MySQLDB

    %% Click Events for API Layer (Controllers)
    click AuthController "https://github.com/jobs2306/pruebacompuslands/blob/main/PruebaApp/Controller/AuthController.cs"
    click ClientesController "https://github.com/jobs2306/pruebacompuslands/blob/main/PruebaApp/Controller/ClientesController.cs"
    click PedidoController "https://github.com/jobs2306/pruebacompuslands/blob/main/PruebaApp/Controller/PedidoController.cs"
    click PedidoProductosController "https://github.com/jobs2306/pruebacompuslands/blob/main/PruebaApp/Controller/PedidoProductosController.cs"
    click ProductoController "https://github.com/jobs2306/pruebacompuslands/blob/main/PruebaApp/Controller/ProductoController.cs"

    %% Click Events for Service Interfaces
    click IClientesService "https://github.com/jobs2306/pruebacompuslands/blob/main/PruebaApp/Service/Interface/IClientesService.cs"
    click IPedidoService "https://github.com/jobs2306/pruebacompuslands/blob/main/PruebaApp/Service/Interface/IPedidoService.cs"
    click IPedidoProductoService "https://github.com/jobs2306/pruebacompuslands/blob/main/PruebaApp/Service/Interface/IPedidoProductoService.cs"
    click IProductoService "https://github.com/jobs2306/pruebacompuslands/blob/main/PruebaApp/Service/Interface/IProductoService.cs"

    %% Click Events for Service Implementations (assumed file names)
    click ClienteService "https://github.com/jobs2306/pruebacompuslands/blob/main/PruebaApp/Service/ClienteService.cs"
    click PedidoService "https://github.com/jobs2306/pruebacompuslands/blob/main/PruebaApp/Service/PedidoService.cs"
    click PedidoProductoService "https://github.com/jobs2306/pruebacompuslands/blob/main/PruebaApp/Service/PedidoProductoService.cs"
    click ProductoService "https://github.com/jobs2306/pruebacompuslands/blob/main/PruebaApp/Service/ProductoService.cs"

    %% Click Events for Data Access Layer
    click ApplicationDbContext "https://github.com/jobs2306/pruebacompuslands/blob/main/PruebaApp/Data/ApplicationDbContext.cs"
    click ClientesModel "https://github.com/jobs2306/pruebacompuslands/blob/main/PruebaApp/Models/Clientes.cs"
    click ProductosModel "https://github.com/jobs2306/pruebacompuslands/blob/main/PruebaApp/Models/Productos.cs"
    click PedidosModel "https://github.com/jobs2306/pruebacompuslands/blob/main/PruebaApp/Models/Pedidos.cs"
    click PedidoProductosModel "https://github.com/jobs2306/pruebacompuslands/blob/main/PruebaApp/Models/PedidoProductos.cs"
    click Migrations "https://github.com/jobs2306/pruebacompuslands/tree/main/PruebaApp/Migrations"

    %% Click Events for Deployment/Containerization
    click Dockerfile "https://github.com/jobs2306/pruebacompuslands/tree/main/PruebaApp/Dockerfile"
    click DockerCompose "https://github.com/jobs2306/pruebacompuslands/blob/main/PruebaApp/docker-compose.yml"
    click AppSettings "https://github.com/jobs2306/pruebacompuslands/blob/main/PruebaApp/appsettings.json"
    
    %% Styles
    classDef external fill:#e0e0e0,stroke:#333,stroke-width:2px;
    classDef api fill:#ffeb99,stroke:#333,stroke-width:2px;
    classDef service fill:#d5f5e3,stroke:#333,stroke-width:2px;
    classDef data fill:#d6eaf8,stroke:#333,stroke-width:2px;
    classDef docker fill:#fadbd8,stroke:#333,stroke-width:2px;
```
