CQRS is (not?) that simple

When I was trying to learn what the heck is CQRS, I found it very difficult. Authors of blog posts, and others in their explanations, are constantly mixing CQRS with different buzzwords. This makes things not easy for understanding. Oh well, at least for me.

What really is CQRS?

You can describe the entire idea of CQRS in just a single sentence.

CQRS is separate model between write and read.

In this blog post, we will talk about pure CQRS. No event sourcing, no message patterns, no eventual consistency anymore. All these buzzwords make things complex. Despite that, my goal is to keep CQRS sweet and simple.

Let’s go deeper!

Traditional approach