Scaling Writes medium
In a CQRS architecture, how does the 'Write Model' typically communicate changes to the 'Read Model'?
- A They share the same database tables.
- B The Write Model publishes events (e.g., 'UserCreated') to a bus, and the Read Model subscribes to update its own optimized views.
- C The client updates both manually.
- D The Read Model polls the Write Model every second.
Answer: B. The Write Model publishes events (e.g., 'UserCreated') to a bus, and the Read Model subscribes to update its own optimized views.
CQRS decouples the sides. The Write side is optimized for command validation. The Read side is an eventually consistent projection (View) built by listening to the stream of changes.
One system design question a day, with spaced repetition so the ones you miss come back.
Get the appRelated questions
- What does the 'Atomicity' property in a database transaction guarantee regarding writes?
- Your database is struggling with write traffic. You decide to 'Scale Up' (Vertical Scaling) by buying a bigger server. What is the eventual hard limit of this strategy?
- A developer sets up a 'Fire-and-Forget' write pattern (sending data without waiting for a database confirmation) to speed up the app. What is the major risk?
- Why is inserting 1,000 rows in a single 'Batch' query faster than executing 1,000 separate `INSERT` queries?
- In the Raft consensus algorithm, what mechanism prevents a 'Split Vote' (where no leader gets a majority) from stalling the cluster indefinitely?
- Your 'Logs' table has 10 billion rows and writes are getting slow. You barely access logs older than 1 year. What is the simplest strategy to improve performance?