Skip to main content

Infrastructure

Current Local Topology

ComponentLocal portRuntime
Gateway8080NGINX
Identity service8001FastAPI container
Customer service8002FastAPI container
Game service8003FastAPI container
Chat service8004FastAPI container
Staff console5173Node/Vite container

The local stack is orchestrated with Docker Compose. The gateway routes /identity/, /customer/, /game/, and /chat/ traffic to the respective backend containers.

Current Persistence

ServiceCurrent store
identity-servicePostgreSQL-oriented schema and Alembic migrations
customer-serviceSQLite under data/customer/
game-serviceSQLite under data/game/
chat-serviceSQLite under data/chat/

Target Production Platform

CapabilityPreferred platform
ContainersAWS ECS/Fargate or EKS
Service databasesRDS PostgreSQL per service
CacheElastiCache Redis
Key managementAWS KMS
Backups and retained exportsS3
ObservabilityCloudWatch, OpenTelemetry, and Prometheus-compatible metrics

Infrastructure Expectations

  • Per-service secrets and least-privilege access
  • TLS at the edge and encrypted storage
  • Blue/green or rolling deployment strategy
  • Health checks for authentication, WebSockets, and archive-expiry jobs
  • Daily backups plus restore drills
  • Separation between local evaluation topology and production infrastructure