Scaling Writes easy
Why are NoSQL databases (like Cassandra or DynamoDB) often chosen for write-heavy workloads over traditional SQL databases?
- A They use SQL, which is popular.
- B They are designed from the ground up for easy horizontal scaling (Sharding) and often relax strict consistency (ACID) constraints to speed up writes.
- C They are older and more stable.
- D They use less RAM.
Answer: B. They are designed from the ground up for easy horizontal scaling (Sharding) and often relax strict consistency (ACID) constraints to speed up writes.
Traditional SQL databases scale up (Vertical). NoSQL databases scale out (Horizontal). By relaxing constraints like Joins and strict transactions, NoSQL can ingest writes across hundreds of nodes efficiently.
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?