How hawerforerouniandes/electivamicroservicios works
Project type and purpose
• This is a microservices‐based backend example (“fotoalpes-microservices-examples”) split into three domain services: usuarios, productos, and ordenes.
• Each service exposes REST endpoints for CRUD operations on its resource and maintains its own database.
• Services communicate asynchronously via a messaging queue to propagate updates and maintain eventual consistency.
• An API Gateway sits in front of the trio to route incoming HTTP calls.
File structure
• Top‐level README.md describes all services and the asynchronous communication pattern.
• The usuarios directory contains:
• Dockerfile (to containerize the service)
• app.py (Flask or similar HTTP server)
• models.py (ORM definitions)
• instance/database.db (local SQLite store)
• requirements.txt (Python dependencies)
• __pycache__ (compiled bytecode)
• By analogy, productos and ordenes directories (not shown) follow the same layout.
• No frontend code or monolith—purely backend microservices.
README for additional insights
• Lists each domain’s operations (create, list, consult, modify).
• Specifies that each service keeps a copy of other services’ schemas in its DB and updates it via message bus.
• Mentions “API Gateway” but no implementation details inside this repo.
Elements
• Clear, human‐readable labels for every component (API Gateway, Service A, DB A, Message Broker, etc.).
Capturing essential details
• That each service has its own Docker container, code, and database.
• Which events trigger which updates (e.g., “usuarios publishes user.updated → ordenes updates its user copy”).