Scaling Writes easy
What does it mean to 'Shard' a database to improve write performance?
- A Splitting a single large database table across multiple distinct servers based on a key (e.g., User ID).
- B Compressing the database files.
- C Creating read-only copies of the database.
- D Moving the database to the cloud.
Answer: A. Splitting a single large database table across multiple distinct servers based on a key (e.g., User ID).
Sharding splits the dataset horizontally. Instead of one server handling 100% of writes, Server A handles User IDs 1-1000, and Server B handles 1001-2000, effectively doubling write capacity.
One system design question a day, with spaced repetition so the ones you miss come back.
Get the appRelated questions
- What does the 'Atomicity' property in a database transaction guarantee regarding writes?
- Your database is struggling with write traffic. You decide to 'Scale Up' (Vertical Scaling) by buying a bigger server. What is the eventual hard limit of this strategy?
- A developer sets up a 'Fire-and-Forget' write pattern (sending data without waiting for a database confirmation) to speed up the app. What is the major risk?
- Why is inserting 1,000 rows in a single 'Batch' query faster than executing 1,000 separate `INSERT` queries?
- In the Raft consensus algorithm, what mechanism prevents a 'Split Vote' (where no leader gets a majority) from stalling the cluster indefinitely?
- Your 'Logs' table has 10 billion rows and writes are getting slow. You barely access logs older than 1 year. What is the simplest strategy to improve performance?