Skip to main content
Software Engineering

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.

Required fields*

3
  • Thank you very much for taking the time to read my question and reply. Indeed the code in my examples is not the "prettiest" since I am not quite familiar with C# or LINQ yet. Also encapsulating some logic in methods, like Find() in your example, is a good idea, since I can reuse it and it also embraces the DRY principle. FInally, I 've read that Domain Events are primarily used to propagate changes between different aggegates, but after reading this: shorturl.at/ivEU9 it seemed to me like suitable use of Domain Events as I wanted the changes in the aggregate to propagate from "botom to top". Commented Jul 10, 2021 at 4:03
  • To sum up, what I keep from your answer is that I should stick doing any "calculations" involving a chlild entity directly in the aggregate root's methods and use Domain Events mostly for cross-aggregare communication. Thank you once again. Commented Jul 10, 2021 at 4:03
  • Bubbling up events within an aggregate root is, in most of the cases, unnecessary complexity. Root has enough scope and knowledge to know what to do when children changes. One more drawback could be that eventual communication via events might end in race conditions. Something relatively easy to avoid with Observer pattern, which in my opinion is also unnecessary here. Commented Jul 11, 2021 at 9:57