AWS Resource Diagram

Edit this diagram in Lucidchart.

Upcoming Changes

• Migrate RDS to Aurora Serverless tutorial
• Update MySQL version from 8.x to latest version

Backend services

The canonical backend lives in backend/: uv-workspace microservices under projects/ plus shared libraries under libs/. Each service has an ARCHITECTURE.md (what it does, how it’s built, where code lives) alongside its run-it README. Shared libraries are summarized in backend/libs/README.md.

The root-level directories UserService/, RestaurantService/, BetService/, WebSocketService/, DevPanel-V2/, OutcomeGen/ are pre-monorepo legacy and are not maintained. Use the backend/projects/ versions below.

HTTP APIs (FastAPI + Mangum → Lambda)

• user_service — users, profiles, user-side reservations (port 8000)
• restaurant_service — venues, menus, reservation pools (port 8001)
• bet_service — core betting engine: live/finished bets, outcomes, promos, trivia (port 8002)
• partner_dashboard_service — partner dashboard API (port 8003)
• event_service — analytics event tracking (Amplitude + Kinesis Firehose)
• websocket — realtime messaging (API Gateway WebSocket)

Async workers

• game_tracker — live game-state tracking (active)
• bet_resolver — bet settlement + payouts (active)
• bet_tracker — legacy; replaced by game_tracker + bet_resolver

Scheduled / event Lambdas

• bet_auditor — closes imbalanced promo bets (EventBridge, ~2 min)
• outcome_generator — generates bettable outcomes per game
• cognito_service — Cognito auth extension
• customer_io_service — SMS via SNS

Tools

• agent_service — Maître AI agent (two-Lambda API + SQS runner)
• dev_panel — Streamlit admin dashboard (port 8501)