Continuing our design journey
In Chapter 4, Domain Analysis and Modeling, we discussed eventstorming as a lightweight method to clarify business flows. As a reminder, this is the output produced from our eventstorming session:
Figure 7.1 – Recap of the eventstorming session
As mentioned previously, we are making use of the CQRS architecture pattern to create the solution. For a detailed explanation on why this is a sound method to employ, you can revisit the When to use CQRS section in Chapter 3, Understanding the Domain, where we’ve already covered this. In the preceding diagram, the green stickies represent read/query models. These query models are required when validating a command (for example, a list of valid product identifiers when processing the ValidateProduct command) or if the information is simply required to be presented to the user (for example, a list of LCs created by an applicant). Let’s look at what it means to apply CQRS...
