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; what you should do; what you can do but be aware of trade-offs.

We'll also have a look at different implementation possibilities in .net.

Let's get back to the basics and see which CQRS is the real one.