Scaling Reads easy
Why is `SELECT * FROM Users` generally discouraged in high-performance applications compared to `SELECT name, email FROM Users`?
- A It breaks the database.
- B It is harder to read.
- C It sorts the data backwards.
- D It fetches unnecessary columns, wasting network bandwidth and memory.
Answer: D. It fetches unnecessary columns, wasting network bandwidth and memory.
Selecting all columns (`*`) might pull massive text fields (like 'biography' or 'logs') that you don't need, slowing down the transfer and parsing of data.
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'?
- 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?
- In a Primary-Replica architecture, which operation is typically ONLY allowed on the Primary node?