How oettaqui/transcendence_42 works
Project type and purpose
• This is a full-stack, real-time multiplayer gaming platform (“ft_transcendence”) built on a microservices backend.
• Its purpose is to provide ping-pong gameplay, chat, tournaments, user management, and monitoring/logging in a containerized environment.
File structure
• Top-level ● backend ● front-end ● nginx ● infra ● docker-compose.yml ● Makefile
• backend/ contains five services (api-gateway, user, game, chat, tournament), each with its own Dockerfile, routes, controllers, models, and WebSocket or HTTP server entry point.
• front-end/ holds a TypeScript SPA powered by Vite.
• nginx/ contains reverse-proxy configuration.
• infra/ holds ELK Stack and Prometheus + Grafana definitions for logging and metrics.
Review README architecture section
• NGINX acts as a reverse proxy/load balancer.
• A SPA frontend communicates with an API Gateway on port 3000.
• The API Gateway routes to microservices: user (3001), chat (3005), game (3003/3006), tournament (3007).
• Each service uses SQLite (with shared volume auth_data for user/chat).
• Monitoring: ELK Stack for logs, Prometheus + Grafana for metrics.
• Blue for edge and API Gateway
• Green for microservices
• Orange for databases/volumes
• Gray for monitoring/logging
• Annotations for ports (3000, 3001, 3003/3006, 3005, 3007) and protocols (HTTP, HTTPS, WS)