Problem context and objectives
Lead systems engineer · Replica Compass
Design a globally replicated key-value service. Some keys are user preferences, while others represent uniqueness claims such as usernames.
The design must survive regions 5 and reads 1M/s. Every box must earn its place by satisfying a requirement or containing a failure.
How you win
- 1Trace one user action from request to durable outcome
- 2Connect every component to a stated requirement
- 3Explain the losing tradeoff, not only the chosen technology
Rules and pressure
- regions: 5
- reads: 1M/s
- Low-latency reads
- Explicit conflict policy
New words in this mission
Open a term for a plain-language explanation.latency+
The waiting time from starting an action until its result is available. Lower latency makes interactions feel more immediate.
consistency+
The promise about when different readers see the same state. Stronger promises simplify reasoning but can cost latency or availability.
Live architecture trace
Replica Compass: request to outcome
Regional client sends “request” to Global router. Consistency is a product invariant decision, not one universal database toggle.
Design a globally replicated key-value service. Some keys are user preferences, while others represent uniqueness claims such as usernames. Follow one real user action through the complete architecture; a component is useful only when you can explain the request, state, or failure it handles.