How juanjosell/microservice-app-example works
Main Components
• Users API (Java / Spring Boot): Provides user profile information and basic user queries.
• Auth API (Go): Manages authorization and generates JWT tokens for secure communication.
• TODOs API (NodeJS): Provides CRUD operations for TODO items; also logs 'create' and 'delete' operations.
• Log Message Processor (Python): Acts as a consumer that reads from a Redis queue and processes log messages.
• Frontend (Vue JS): The user interface that communicates with the backend services via APIs.
• Supporting Services: Include any configuration/deployment tools visible in the project such as the Azure Pipelines configuration (azure-pipelines.yml) and integration with Redis (used by TODOS API and Log Message Processor).
Relationships and Interactions
• Frontend communicates with the Auth API, Users API, and TODOs API via RESTful calls.
• Auth API provides JWT tokens that secure access to other APIs.
• TODOs API interacts with a Redis queue to log specific operations (CRUD events).
• Log Message Processor consumes messages from the Redis queue and outputs log details.
Architectural Patterns and Components
• Microservices Architecture: Highlight the separation of concerns as each service is a standalone component that can be built, deployed, and scaled independently.
• API Gateway or Frontend as API Consumer: While not explicitly mentioned, the Frontend plays the role of aggregating data from the different backend services.
• JWT for Authentication: Emphasize the role of Auth API in token generation and validation as part of secure communication.
Relevant Technologies and Frameworks
• Users API: Spring Boot, Java.
• Auth API: Go.
• TODOs API: NodeJS, Express (if applicable), Redis integration.
• Log Message Processor: Python (using standard libraries or message queue packages).
• Frontend: Vue.js, webpack configuration (note the build and config directories).
• Additional DevOps tools: Azure Pipelines for CI/CD integration.