Polaris Config asks for a key-value store in three regions holding configuration and sessions. Deliver the scope, a quorum size, a versioned API, the stored item, regional routing with quorum replication, a conflict strategy and replica repair.
How interviewers level this design
- Junior: replicates each key to every region and routes clients to the nearest one.
- Mid-level: explains R + W > N, versions writes and repairs replicas after a partition.
- Senior: chooses consistency per data type, handles clock drift with version vectors or hybrid clocks and plans region evacuation.
Polaris Config runs a key-value store in three regions for configuration and user sessions. Every region must read locally in milliseconds, and a write must survive the loss of a whole region. No single setting fits both kinds of data: a stale session is an inconvenience, a stale feature flag can break checkout.
You will work with quorums: with N replicas, a write acknowledged by W of them and a read that asks R of them overlap whenever R + W > N. You will define the API and table, route clients to their nearest region, choose a conflict strategy for writes made on both sides of a partition and repair replicas that missed writes while a region was away.
Use quorums for overlap, detect concurrent writes with versions and repair replicas after a partition.