The entire stack — API and database — runs in a single region (us-east). Users in Europe and Asia hit it across the ocean, paying hundreds of milliseconds per request, and a regional outage takes the whole product down. Make it multi-region.
Multi-region deployment runs the stack in two or more geographic regions, with geo-routing sending each user to the nearest one. This cuts latency for a global audience and survives a regional outage. Databases replicate across regions to keep data available everywhere. The trade-off is cross-region replication cost and conflict resolution under concurrent writes.
Evaluation criteria and weights will be revealed after you submit your solution. This ensures a fair assessment of your design skills.
Draw your architecture diagram, explain your design decisions, and get AI-powered feedback.
For the best experience, design challenges on a desktop or tablet — drawing the architecture on a phone is hard.