Skip to content

Commit 5cad8e9

Browse files
CESARDELATORREmairaw
authored andcommitted
Minor update, clarification. (#9878)
* Minor update, clarification. * Update docs/standard/microservices-architecture/microservice-ddd-cqrs-patterns/eshoponcontainers-cqrs-ddd-microservice.md Co-Authored-By: CESARDELATORRE <[email protected]> * Update docs/standard/microservices-architecture/microservice-ddd-cqrs-patterns/eshoponcontainers-cqrs-ddd-microservice.md Co-Authored-By: CESARDELATORRE <[email protected]>
1 parent a283603 commit 5cad8e9

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

docs/standard/microservices-architecture/microservice-ddd-cqrs-patterns/eshoponcontainers-cqrs-ddd-microservice.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,9 @@ ms.date: 10/08/2018
99

1010
The design of the ordering microservice at the eShopOnContainers reference application is based on CQRS principles. However, it uses the simplest approach, which is just separating the queries from the commands and using the same database for both actions.
1111

12-
The essence of those patterns, and the important point here, is that queries are idempotent: no matter how many times you query a system, the state of that system will not change. You could even use a different “reads” data model than the transactional logic “writes” domain model, although the ordering microservices is using the same database. Hence this is a simplified CQRS approach.
12+
The essence of those patterns, and the important point here, is that queries are idempotent: no matter how many times you query a system, the state of that system won't change. In other words, queries are side-effect free.
13+
14+
Therefore, you could use a different “reads” data model than the transactional logic “writes” domain model, even though the ordering microservices are using the same database. Hence, this is a simplified CQRS approach.
1315

1416
On the other hand, commands, which trigger transactions and data updates, change state in the system. With commands, you need to be careful when dealing with complexity and ever-changing business rules. This is the where you want to apply DDD techniques to have a better modeled system.
1517

@@ -58,4 +60,4 @@ There is only one application architecture: the architecture of the system or en
5860

5961
>[!div class="step-by-step"]
6062
>[Previous](apply-simplified-microservice-cqrs-ddd-patterns.md)
61-
>[Next](cqrs-microservice-reads.md)
63+
>[Next](cqrs-microservice-reads.md)

0 commit comments

Comments
 (0)