Mock Interviewer
Ask Coach
Tap a question to start, or type your own below.
Distributed Database System Design
Visual Problem Diagram
Scenario
A network partition splits US-East and EU-West—your "globally consistent" database either rejects writes or forks conflicting rows users never see reconciled. The interview compares Spanner/Paxos, Cassandra tunable consistency, and shard rebalancing honestly.
Design a distributed database that partitions data across nodes, replicates for fault tolerance, and serves queries with defined consistency guarantees. Compare SQL sharding vs leaderless wide-column models for the scenario given.
You should support CRUD, replication, failover, resharding, and consistency levels. Be ready to explain CAP tradeoffs and cross-shard limitations.
Constraints
SQL/KV CRUD, replication, secondary indexes, transactions per shard, admin resharding
99.99% availability, tunable latency vs consistency, horizontal scale, automatic failover
Petabytes, millions QPS aggregate, thousands of shards, multi-region
Stages ahead
Log in to start practicing
Preview the problem below. Sign in to start your timed session, save progress, and use the AI coach.
Want full access now? View Pro pricing