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*

5
  • 4
    "I guess the answer is that this is a much more complex concept than I first thought it was." This is very true. Commented Feb 16, 2011 at 22:35
  • for your situation, you might create a proxy for the aggregate root object that selectively retrieves and caches data only when it is requested Commented Jun 3, 2011 at 15:55
  • My suggestion is to implement lazy load in the root aggregate associations. So you can retrieve a list of roots without loading too many objects. Commented Feb 19, 2015 at 16:35
  • 5
    almost 6 years later, still a good question. After reading the chapter in the red book, I'd say: don't make your aggregates too big. It's tempting to pick some top-level concept from your domain and declare it the Root to Rule Them All but DDD advocates smaller aggregates. And mitigates inefficiencies like the ones you describe above. Commented Nov 20, 2016 at 21:35
  • Your aggregates should be as small as possible while being natural and effective to the domain (a challenge!). Furthermore, it is perfectly fine and desirable for your repos to have highly specific methods. Commented Mar 18, 2017 at 16:35