Is CQRS Complicated? No, it's simple!

💥 Join this channel to get access to source code, demos, and slides!

📚 Book Recommendations

Domain-Driven Design

Patterns of Enterprise Application Architecture

Refactoring: Improving the Design of Existing Code

Monolith to Microservices: Evolutionary Patterns to Transform Your Monolith

RESTful Web Clients: Enabling Reuse Through Hypermedia

[mebsuta]

Simplicity is the key to understanding any concept. You have provided a very simple explanation that sits well with my understanding. Thank you.

[santosfelipe]

I just needed the basic concept and this is exactly what I wanted

[mwatkins]

i dont understnad what the point of using CQRS would be if not to implement an event driven application/microservices. Why would I want a class for a query instead of just running the query and returning the object model that they are querying for?

[zoran]

Hi, and thank you for your video! Can you give a more detailed example of using CQRS with Entity Framework? I think that is a good alternative to the Repository+Unit Of Work pattern, which I honestly often use.

[yulinxp]

Even the name CQRS itself is complicated enough.

[leehaisen]

It kinda seems to work similar to GraphQL in a way in terms of mutations and queries right ?