-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to create a more complex aggregate with more than one entity #24
Comments
Hi @Heucles! An aggregate:
I would recommend not to start with the entities, start with the intention. Little hint: Try first to not give your aggregate a name. (first catch intention, then give a name) If you want, you can even try to do an event storming (by @ziobrando) => https://techbeacon.com/introduction-event-storming-easy-way-achieve-domain-driven-design ;-) |
Can you put together a sample of what it would look like an aggregate with more than one entity, something like:
Car (root)
Customer (root)
I am having some trouble setting this up, since Customer events can have an effect over the Car aggregate. Can you point me into the right direction?
The text was updated successfully, but these errors were encountered: