Scaling Reads easy
The CQRS (Command Query Responsibility Segregation) pattern suggests what core principle?
- A Using only one database for everything.
- B Separating the models/systems used for Reading data from the models/systems used for Writing data.
- C Always using caching.
- D Writing SQL in uppercase.
Answer: B. Separating the models/systems used for Reading data from the models/systems used for Writing data.
Reads and Writes often have different performance requirements. CQRS splits them, allowing you to optimize the Read side (e.g., fast lookups) differently from the Write side (e.g., complex logic).
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?