Scaling Writes easy
What does the 'Atomicity' property in a database transaction guarantee regarding writes?
- A If a transaction contains 5 writes, either ALL 5 succeed, or NONE of them happen (All-or-Nothing).
- B Writes happen instantly.
- C Writes are encrypted.
- D Writes are automatically backed up.
Answer: A. If a transaction contains 5 writes, either ALL 5 succeed, or NONE of them happen (All-or-Nothing).
Atomicity prevents partial data. If your system crashes halfway through a transaction, the database rolls back the half-finished changes to keep the data clean.
One system design question a day, with spaced repetition so the ones you miss come back.
Get the appRelated questions
- 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?
- When measuring how well your system handles writes, which metric is most important?