Scaling Writes easy
A user clicks 'Generate Report'. This operation requires a heavy database write that takes 10 seconds. To keep the website responsive, what is the best architectural pattern?
- A Use a faster CPU.
- B Place the request in a Message Queue and have a background worker process the write asynchronously.
- C Increase the browser timeout.
- D Run the write on the user's computer.
Answer: B. Place the request in a Message Queue and have a background worker process the write asynchronously.
Decoupling the user action from the heavy write ensures the UI responds instantly ('202 Accepted'). The heavy lifting happens in the background without blocking the web server.
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?