Event sourcing and Command Query Responsibility Segregation are frequently mentioned together. Although neither one necessarily implies the other, but they do complement each other.
In our CQRS explanation, we had observed the following diagram:
Events in a way act as synchronization of data on the write-side with the read-side. Once the data is synced with the read side, the read side stores the data in a fashion that makes it very fast to read (denomalized data?).
We could improvise our model by including Event Sourcing in the picture. On the write side, when a command is received, instead of persisting data in its own data model. The write side would generate events, append it to its event store and finally push it towards the read side.
The write side manages the event side, and pushes all the updates made on the write-side as events towards the read...