Scaling Writes easy
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?
- A Add more indexes.
- B Archive (move) old data to 'Cold Storage' (e.g., S3 or a separate table) and delete it from the main active table.
- C Buy a larger hard drive.
- D Use a faster internet connection.
Answer: B. Archive (move) old data to 'Cold Storage' (e.g., S3 or a separate table) and delete it from the main active table.
Small tables are fast tables. Keeping the 'Active Set' small by pruning old, unused data keeps indexes small and RAM cache efficient.
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?
- When measuring how well your system handles writes, which metric is most important?