CQRS (Command Query Responsibility Segregation)

When to use

• The user wants to represent each state-changing intent as a command object dispatched to a dedicated handler.
• The user wants distinct models for changing state and for reading data because one shared model has become awkward for both.
• The user wants read models tailored to each view, bypassing the write model to return exactly what a screen needs.

When NOT to use

• Do not adopt event sourcing or eventual consistency just because you are separating reads from writes.
• Do not split reads and writes for a plain CRUD screen where one model serves both sides comfortably.

Core guidance