Scaling Reads easy
If you decide to 'Vertically Scale' (Scale Up) your database to handle more reads, what are you doing?
- A Upgrading the existing server with more RAM and a faster CPU.
- B Adding more servers to form a cluster.
- C Splitting the database into smaller pieces.
- D Optimizing the SQL queries.
Answer: A. Upgrading the existing server with more RAM and a faster CPU.
Vertical scaling means making the single node bigger (stronger hardware). Horizontal scaling means adding more nodes (distributed system).
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?