Busting some CQRS myths
Myth #1 – CQRS = Event Sourcing and vice versa
Event sourcing often fits well with CQRS, as it makes building and updating read stores over time a bit more straightforward in eventually consistent models. Additionally, the aggregates living in the command side for behavior-heavier systems and task-based UIs more obvious.
However, event sourcing is a completely orthogonal concept to CQRS . While they fit well together, doing CQRS does not require event sourcing, and doing event sourcing does not automatically mean we’re doing CQRS.
