How 9601dani/revista-ayd2-grupoa works
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.