Scaling Reads easy
Your database is overwhelmed by too many 'Get User' requests, but the number of 'Update User' requests is low. What is the standard architectural fix?
- A Sharding the database.
- B Switching to NoSQL.
- C Adding Read Replicas and directing all GET requests to them.
- D Compressing the database.
Answer: C. Adding Read Replicas and directing all GET requests to them.
Since the bottleneck is reading, creating copies (Replicas) of the data allows you to spread the read load across multiple machines, while the Primary handles the writes.
One system design question a day, with spaced repetition so the ones you miss come back.
Get the appRelated questions
- In a caching system, what is a 'Cache Miss'?
- Why is `SELECT * FROM Users` generally discouraged in high-performance applications compared to `SELECT name, email FROM Users`?
- You have users all over the world downloading large images from your server in New York. Users in Australia complain it is slow. What solves this?
- What is the main downside of reading from a Read Replica instead of the Primary database?
- You have maximized the RAM on your single database server, but it's still too slow. You decide to add 10 more servers to share the load. What is this called?
- You have 5 Read Replicas. How does the application know which one to ask for data?