ORIGINAL SYSTEM DESIGN QUESTION
Multi-region account failover
Keep account reads/writes available across two regions with a defined recovery policy.
Original exercise · advanced. Editorial role relevance does not imply a company has asked this question.
Requirements and constraints
- 20,000 reads/second; 2,000 writes/second; five TB dataset.
- Choose and justify RPO/RTO; split-brain writes must be addressed.
- State assumptions and justify security, cost, operational ownership and data retention.
Pressure round
Connectivity between regions fails while both regions can reach clients.
Build and explain the design
Requirements & scope
Who uses it? What must it do? What is explicitly out of scope? State latency, durability and privacy goals.
Self-review guidance
Define the actors, required operations and out-of-scope behavior. Explicit requirement: Choose and justify RPO/RTO; split-brain writes must be addressed.
Capacity estimates
State assumptions, peak requests/second, data volume and retention. Show your arithmetic and units.
Self-review guidance
Use this workload: 20,000 reads/second; 2,000 writes/second; five TB dataset. Convert rates and payload sizes into peak compute/storage assumptions; show units, headroom and what remains unmeasured.
APIs & data model
Describe endpoints/events, entity keys, indexes, authorization, and idempotency.
Self-review guidance
Define write ownership, replication positions and failover epochs.
Architecture & data flow
Describe components and request/event paths. Use plain text arrows to sketch your design; explain each responsibility.
Self-review guidance
Model leader placement, replicated logs and recovery procedures.
Failures & observability
What happens on overload, duplicate events, partial failures or lost dependencies? Discuss monitoring and recovery.
Self-review guidance
Pressure-test: Connectivity between regions fails while both regions can reach clients. Describe bounded recovery, deduplication, observability and a user-visible failure state.
Tradeoffs & alternatives
Compare two plausible approaches. State the costs, consistency model and what would make you change the design.
Self-review guidance
Compare write availability with consistency and operator-controlled failover.
Design guidance describes assumptions and tradeoffs; no architecture has been simulated or benchmarked.
Practice this question
Save your work privately, explain decisions and return to your revision queue.
Open practice workspaceBrowse the question library →