Scaling Writes medium
Multi-Master (Active-Active) replication allows writes to any node. What is the primary complexity this introduces?
- A Write Conflicts. Two users might update the same record on different servers at the same time, requiring logic to merge or resolve the divergence.
- B Slower Read speeds.
- C It requires more RAM.
- D It only works with NoSQL.
Answer: A. Write Conflicts. Two users might update the same record on different servers at the same time, requiring logic to merge or resolve the divergence.
If Node A sets `X=1` and Node B sets `X=2` simultaneously, the system must decide which one wins (Last-Write-Wins, Vector Clocks, or CRDTs). This complexity is absent in Single-Master systems.
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?