What’s an Aggregate Root?

In the context of the repository pattern, aggregate roots are the only objects your client code loads from the repository.

The repository encapsulates access to child objects – from a caller’s perspective it automatically loads them, either at the same time the root is loaded or when they’re actually needed (as with lazy loading).

For example, you might have an Order object which encapsulates operations on multiple LineItem objects. Your client code would never load the LineItem objects directly, just the Order that contains them, which would be the aggregate root for that part of your domain.

Related Posts:

  1. What is a wrapper class?
  2. Why is IoC / DI not common in Python?
  3. Why is IoC / DI not common in Python?
  4. What are the differences between Abstract Factory and Factory design patterns?
  5. Difference between static class and singleton pattern?
  6. What is the difference between Builder Design pattern and Factory Design pattern?
  7. On design patterns: When should I use the singleton?
  8. What is a MV* framework?
  9. What is dependency injection?
  10. What is Inversion of Control?
  11. Is there a simple, elegant way to define singletons? [duplicate]
  12. C++ Singleton design pattern
  13. What is the difference between MVC and MVVM?
  14. C++ Singleton design pattern
  15. What is copy-on-write?
  16. Does PHP supports MVP pattern?
  17. How to implement the factory method pattern in C++ correctly
  18. Factory Pattern. When to use factory methods?
  19. tar: add all files and directories in current directory INCLUDING .svn and so on
  20. Simplest/cleanest way to implement a singleton in JavaScript
  21. What is an anti-pattern?
  22. JavaScript pattern for multiple constructors
  23. Angular design pattern: MVC, MVVM or MV*?
  24. What are MVP and MVC and what is the difference?
  25. Flask-framework: MVC pattern
  26. Relational Database Design Patterns?

Leave a Comment