Now you know the basic rules for Aggregate Design.

The best way to learn about Aggregates is by seeing code. So let's consider the scenario of a web application where users can make wishes to be granted if something happens to them, similar to a will. For example, I would like to send an email to my wife explaining what to do with my GitHub account if I die in a horrible accident, or maybe I want to send an email telling her how much I loved her. The way to check that I'm still alive is to answer emails the platform sends to me. (If you want to know more about this application, you can visit our GitHub account. So we have users and their wishes. Let's consider only one use case: "As a User, I want to make a Wish." How could we model this? Using good practices when designing Aggregates, let's try to push for small Aggregates. In this case, that means using two different Aggregates of one Entity each, User and Wish. For the relationship between them...