Backend CQRS Patterns

Purpose

Separate read and write models so each can be optimized independently — write side for consistency and validation, read side for query performance and projection flexibility.

Agent Protocol

Trigger

Exact user phrases: "CQRS", "command query segregation", "separate read write", "command model", "query model", "read model", "write model", "materialized view", "command handler", "query handler", "command bus", "query bus".

Input Context

• Whether the system is greenfield or existing.
• Current data access pattern (CRUD, repository, ORM).
• Read-to-write ratio and query complexity.
• Consistency requirements (strong vs eventual).

Output Artifact

CQRS design as text. No file unless requested.