Multi-Region Active-Active Architecture for a Gaming Backend
Overview
What this challenge is about.
Read the current architecture (single-region: ECS + RDS Aurora + Redis + S3) and traffic mix (around 60 percent APAC, 25 percent NA, 15 percent EU). Design a 3-region active-active architecture on AWS (Tokyo, Frankfurt, N. Virginia) covering: per-region stateless API, Aurora Global Database for player data, multi-region S3 + CloudFront for assets, latency-based DNS routing. Tackle the hard problems: (1) global leaderboard with eventual consistency + per-region top-100 strict, (2) cross-region matchmaking (where do players from 2 regions meet), (3) session affinity. Prototype the cross-region replication on a sample workload (1M synthetic players). Deliver architecture diagrams, Terraform for one of the new regions, the prototype + benchmark, and a 10-page migration plan.
The Brief
What you'll do, and what you'll demonstrate.
Design a 3-region active-active gaming backend that cuts cross-Pacific p95 below 80ms while solving leaderboard, matchmaking, and session-affinity correctly.
Earning criteria — what you'll demonstrate
- Design an active-active multi-region architecture on a major cloud
- Choose consistency models per data type (player profile, leaderboard, sessions)
- Solve cross-region matchmaking as a real distributed-systems problem
- Plan a multi-quarter migration without breaking the live game
Program Fit
Where this fits in your program.
Sharpens the same skills your degree expects you to demonstrate.
Skills
Skills you'll demonstrate.
Each one shows up on your verified credential.
Careers
Roles this prepares you for.
Real titles. Real skill bridges. Pick the one closest to your trajectory.
Career mappings coming soon.