In this chapter, we identified what is the domain model and agreed that the model is representing some part of the real life, which is targeted to solve some specific problem. We also discussed the importance of behavior and that it is the essential part of the model, which 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 represent behavior, from queries that have the only purpose of retrieving state.

Then, we got more elements for the EventStorming modeling technique, to be able to model in more in-depth detail, towards something that we can start implementing in code. We recognized that those new elements match well with the CQRS paradigms.

Finally, we went through the modeling session of our sample domain and got more insight on how the core part of the system should work, so we are now prepared to convert this knowledge to code. That is what we will be doing in the next chapter.