In this chapter, we identified the domain model and agreed that the model represents some part of real life, which is targeted to solve some specific problem. We also discussed the importance of behavior and that it is an essential part of the model that is often overlooked and even ignored.
Along the way, we introduced the CQRS pattern. It separates commands as something to be done inside the model and that represent behavior, from queries that have the only purpose of retrieving state.
Then, we got more elements for the EventStorming modeling technique in order to model detail in more depth, moving toward something that we can start implementing in code. We recognized that these new elements match well with the CQRS paradigms.
Finally, we went through the modeling session of our sample domain and got more insight into how the core part of the system should work, so we...
