eventual-consistency

A separate read store lets a query model match its screen or report instead of the write model. It can remove expensive joins and let read traffic scale independently.

The new boundary also creates a synchronization problem. Reads can be stale, projections must recover safely, and the system has to state what a user should expect after a command.