# 9601dani/revista-ayd2-grupoa architecture

> Architecture diagram of the GitHub repository 9601dani/revista-ayd2-grupoa, 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/9601dani/revista-ayd2-grupoa
- Repository: https://github.com/9601dani/revista-ayd2-grupoa

## Overview

##### Project Overview & Type
- This project is a full-stack microservices application. The backend is comprised of multiple Java-based microservices managed with Maven, and a gateway component that likely handles API routing and cross-cutting concerns. The front end is built as an Angular application, evident by the “app-frontend” folder with angular.json and TypeScript files.
- The README is minimal but confirms that this project is for a “Proyecto 1, Analisis y Dise;o de Sistemas 2,” suggesting that it is an academic or prototype project illustrating a multi-service architecture.

##### Main Architectural Components
- Frontend Client: Represent the Angular-based “app-frontend” component. Highlight that the frontend provides the user interface using Angular, SCSS, and routing components.
- API Gateway: Under “app-backend/gateway”, include this as a dedicated component that is likely the entry point for client requests, performing routing/security.
- Microservices: Illustrate the following individual services as separate components:
- ms-adds
- ms-email
- ms-magazine
- ms-upload
- ms-user
Each microservice is set up as an independent Maven project with its own application configuration (application.yaml) and test suites. They handle specific business functions and are deployed independently.
- Reporting Service: Also include the “report” service which is structured as an independent module.

##### Relationships and Interactions
- From the API Gateway, show that requests are forwarded to the appropriate microservice(s)—for example, ms-user for user management, ms-email for email notifications, etc.
- Optionally, if the services communicate with one another, illustrate inter-service communication channels.
- CI/CD pipeline (Jenkins) and connect it to both frontend and backend components to indicate that deployments and automated tests are triggered from source control changes.

##### Architectural Patterns & Technologies
- Microservices architectural pattern with service isolation, scalability, and modular development.
- The gateway indicates the use of API composition or edge service patterns, which centralize request processing.
- Mention common patterns like “separation of concerns” between frontend (Angular) and backend (Spring Boot likely) services.
- Use of Maven for dependency/build management and possibly Spring Boot for each microservice.

##### Final Touches
- Double-check that the separation between frontend and backend architecture is clearly depicted, along with the orchestration provided by the API gateway.

## Diagram (Mermaid)

```mermaid
flowchart TD
    %% Frontend Layer
    subgraph "Frontend"
        A("Angular Frontend (app-frontend)"):::frontend
    end

    %% Backend Layer
    subgraph "Backend Services"
        B("API Gateway (app-backend/gateway)"):::backend
        C("Microservice: ms-adds"):::backend
        D("Microservice: ms-email"):::backend
        E("Microservice: ms-magazine"):::backend
        F("Microservice: ms-upload"):::backend
        G("Microservice: ms-user"):::backend
        H("Reporting Service"):::backend
    end

    %% CI/CD Pipeline Component
    I("CI/CD Pipeline (Jenkins)"):::cicd

    %% Data Flow Connections
    A -->|"sendsRequest"| B
    B -->|"routesTo"| C
    B -->|"routesTo"| D
    B -->|"routesTo"| E
    B -->|"routesTo"| F
    B -->|"routesTo"| G
    B -->|"routesTo"| H

    %% CI/CD Integration to All Components
    I -->|"deploys"| A
    I -->|"deploys"| B
    I -->|"deploys"| C
    I -->|"deploys"| D
    I -->|"deploys"| E
    I -->|"deploys"| F
    I -->|"deploys"| G
    I -->|"deploys"| H

    %% Click Events for Component Mapping
    click A "https://github.com/9601dani/revista-ayd2-grupoa/tree/main/app-frontend/"
    click B "https://github.com/9601dani/revista-ayd2-grupoa/tree/main/app-backend/gateway/"
    click C "https://github.com/9601dani/revista-ayd2-grupoa/tree/main/app-backend/ms-adds/"
    click D "https://github.com/9601dani/revista-ayd2-grupoa/tree/main/app-backend/ms-email/"
    click E "https://github.com/9601dani/revista-ayd2-grupoa/tree/main/app-backend/ms-magazine/"
    click F "https://github.com/9601dani/revista-ayd2-grupoa/tree/main/app-backend/ms-upload/"
    click G "https://github.com/9601dani/revista-ayd2-grupoa/tree/main/app-backend/ms-user/"
    click H "https://github.com/9601dani/revista-ayd2-grupoa/tree/main/app-backend/report/"
    click I "https://github.com/9601dani/revista-ayd2-grupoa/tree/main/Jenkinsfile"

    %% Styles
    classDef frontend fill:#ADD8E6,stroke:#000,stroke-width:2px;
    classDef backend fill:#90EE90,stroke:#000,stroke-width:2px;
    classDef cicd fill:#FFA500,stroke:#000,stroke-width:2px;
```
