📝CQRS stands for Command Query Responsibility Segregation.
👉CQRS is about separating commands and queries into different classes or objects.
🧩CQS (Command Query Separation) is the foundation of CQRS.
🗂️Commands are responsible for writing data, while queries are responsible for reading data.
📚CQRS helps enforce the Single Responsibility Principle and improves code organization.
What is the difference between CQRS and CQS?
—CQRS builds on top of CQS by further separating commands and queries into different classes or objects.
Do I need separate databases for commands and queries?
—No, it's perfectly fine to use the same database table for both commands and queries.
Do I need event sourcing to implement CQRS?
—No, event sourcing is not required for implementing CQRS. It's all about logical separation of code flows.
Do I need a mediator to implement CQRS?
—No, a mediator is not required for implementing CQRS. Separate classes for commands and queries are sufficient.
What are the benefits of using CQRS?
—CQRS helps improve code organization, enforce the Single Responsibility Principle, and makes it easier to test and maintain your code.
00:00Demystifying CQRS and its misconceptions.
04:20Explaining CQS (Command Query Separation) as the foundation of CQRS.
08:46Introducing CQRS and its concept of separating commands and queries into different classes or objects.
11:50Taking CQRS further by using separate objects for each command, improving code organization and adherence to the Single Responsibility Principle.
13:17Clarifying that separate databases and event sourcing are not required for implementing CQRS.
