In MIPC, what is a primary benefit of applying CQRS alongside event sourcing?

• A. CQRS is unrelated to event sourcing in MIPC.
• B. Event sourcing stores state as a sequence of events; CQRS separates reads from writes to optimize read-heavy paths.
• C. Event sourcing stores only the current state; CQRS merges reads and writes for simplicity.
• D. In MIPC, event sourcing eliminates the need for persistent storage.

Answer: (B)

The main idea is that CQRS leverages the event-driven foundation to make reads and writes operate on different models. In event sourcing, the system’s state is stored as a sequence of events, and every change is captured as an event. CQRS then uses a separate read model that’s optimized specifically for queries, built from those events (often as projections). Writes continue to emit events, while reads pull from a tailored, often denormalized, data structure that can be tuned for fast access, caching, and complex queries. This separation lets read-heavy paths scale and perform better without impacting the write path, and it also makes it easy to replay events to rebuild or update read models as requirements evolve. The other statements don’t reflect this dynamic: they either imply no relation between CQRS and event sourcing, claim you only store the current state, or suggest event sourcing removes the need for persistent storage.