CQRS is one of those patterns/architectures/designs that is easily misunderstood. The basic idea of "separate your reads from your writes" is simple. But it's too simple, it allows for too many misconceptions: the use of separate data stores, caching, eventsourcing, eventual consistency...

Let's take a step back and start from the essence of CQRS.

In this session we'll follow my own path of misunderstanding, confusion and frustration with CQRS. You'll see where I made mistakes and how it started to make sense.

Stop your confusion about CQRS and start taking advantage of it. By the way it doesn't matter whether your using n-tier, clean architecture, hexagonal, microservices or monolith. Any design or architecture can benefit from CQRS.