ADR_014 Customer domain design decisions
Date: 10/31
accepted
This adr captures component design decisions in Customer domain.
We follow the same design process as we used before, which is, identifying top level pieces first.
Among actor/action, event storming, and workflow approaches. We chose event storming approach. Reasons
- There are limited number of actor within this domain
- There are many events can be identified easily identified.
We first started with brain storming all the possible events could happen in this domain, and then write out the commands that trigger those events, and at last identify the data aggregates that these commands will be operating upon. Then it became clear that customer domain can be further divided into Service, Aggregator, Surveyor and databases subcomponents.
This sub-component division did not reveal the workflow.