Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • 2nd seems too uncomvenient and cumbersome. Why that "event" trip to calculate something you can after each call to updateItemPrice? Commented Jul 11, 2021 at 9:35
  • You are right, "event" communication between the same aggregate is more complex than just doing any "calculation" I want inside the aggregate root's method that perform the intial change to child entity. It seemed convenient at first because the initial "change" was concering the child entity (the Item) so I wanted the "side effects" of this change to bubble up, from bottom to top. That's why domain events looked fitting in this case for me. Plus that I also read that this is a possible use for domain events here: shorturl.at/ivEU9 Commented Jul 11, 2021 at 23:07