All challenges
Multiple ChoiceIntermediate 45s

CQRS read model

A CQRS system lets the read model lag behind writes. What must the UI/API account for?
Options
  1. 1Nothing needs to change. Reads against a CQRS read model are always consistent.
  2. 2Read-your-writes may fail, so clients need versioning, staleness tolerance, or token-based routing
  3. 3Writes must wait for the read model to catch up. That waiting defeats the purpose of CQRS.
  4. 4CQRS forbids asynchronous projection. The read model is rebuilt inside the write path.

Think you can answer under pressure?

Get matched and answer live questions in 3-minute 1v1 battles. Elo ranking, badge tiers and bragging rights on the line.

Play this in a 3-minute battle