Scaling Writes easy
Can a standard Load Balancer distribute `INSERT/UPDATE` requests to any server in a Primary-Replica cluster?
- A Yes, all servers are equal.
- B Yes, if the servers are in the same zone.
- C No, databases don't use load balancers.
- D No, the Load Balancer must be configured to send Writes specifically to the Primary node, while Reads can go to Replicas.
Answer: D. No, the Load Balancer must be configured to send Writes specifically to the Primary node, while Reads can go to Replicas.
Sending a write to a Read Replica will result in an error (since it is read-only). The routing logic must distinguish between Read and Write traffic.
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?