How pixelweb-co/apienviosmicroservices works
Main Architectural Components
• API Gateway: Represented by gateway_api (with its nginx.conf), this component will route incoming requests to the proper microservices.
• Microservices: There are several services including:
• accounts_api (handles account-related operations)
• ofertas_api (manages offer-related functionality, which leverages RabbitMQ messaging in its services)
• solicitudes_api (manages request/solicitud operations)
• socket_service (handles real-time operations with socket communications, uses redis and RabbitMQ)
• calificar_service (a Java-based service for "calificar", possibly handling ratings or evaluations)
• micro_service_template (a template for quickly spinning up new services)
• update_service (manages update checks for the system)
• cluster_service_monitor (likely monitors the health or status of the clustered microservices)
• Auxiliary Components:
• A testing component (e.g., testing/socketConnect.html) possibly used for system testing and integration tests.
• Configuration files (such as .env files, Dockerfiles, docker-compose.yml) that assist with deployment and environment configuration.
Out Component Relationships and Data Flow
• For each microservice, represent them as independent components (possibly within their own Docker containers as indicated by their Dockerfiles and a shared docker-compose file).
• Integration of the calificar_service (Java application) with the rest of the system, likely communicating with other services via REST endpoints or even messaging if required.
• Cluster_service_monitor as a monitoring component that observes the health and performance of these services.