Scaling Reads easy
Normalization optimizes for data integrity and reduced redundancy. What does 'Denormalization' optimize for?
- A Write speed.
- B Disk space.
- C Security.
- D Read speed (by avoiding Joins).
Answer: D. Read speed (by avoiding Joins).
Denormalization involves duplicating data (e.g., storing `author_name` inside the `Book` table) so you don't have to JOIN the `Authors` table every time you read a Book.
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?