How deabreu1105/ingenieria-soft works
Project type and purpose
• From the file tree and minimal README, this is a Docker‐based microservices demo/platform (“ingenieria-soft”) showcasing:
• Two custom microservices (ms‐alpha, ms‐beta)
• A relational database (db)
• A caching layer (redis)
• Service discovery (Consul)
• An edge/router (Traefik)
• A “whoami” test service
• A load-testing tool (vegeta)
• Each service has its own Dockerfile and docker-compose.yml, indicating isolated containers managed via Compose.
File structure
• Top-level orchestrators:
• consul/ (service discovery)
• traefik/ (edge router with dynamic certs)
• db/ (Postgres or MySQL, SQL init script)
• redis/ (cache store)
• ms-alpha/, ms-beta/ (core business services)
• whoami/ (echo/test service)
• vegeta/ (load testing harness)
• Each microservice folder: app.py entrypoint, requirements.txt, test suite → standard Python Flask/HTTP service.
• docker-compose files in each folder, plus central Compose via traefik or top-level Compose for full stack.
README for additional insights
• README is a placeholder, so rely on file conventions and folder names.
Details
• Docker Compose boundary
• Ports (e.g., Traefik: 80/443, services: 5000) if known
• Important environment variables or mount points (e.g., traefik cert paths, db init script)
• Version labels if relevant (e.g., Consul v1.x, Redis v6.x)