Scaling Writes medium
Your traffic has huge spikes (10x load) every hour. Your database crashes during these spikes. How does a Message Queue help scaling writes?
- A It makes the database faster.
- B It acts as a buffer. The Queue accepts writes instantly during the spike, and a 'Worker' process drains the queue at a constant, safe speed that the database can handle.
- C It deletes excess messages.
- D It compresses the data.
Answer: B. It acts as a buffer. The Queue accepts writes instantly during the spike, and a 'Worker' process drains the queue at a constant, safe speed that the database can handle.
This pattern creates a 'shock absorber'. The peak load is stored temporarily in the queue (which is optimized for high write throughput), protecting the database from being overwhelmed.
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?