What's an Aggregate Root?

design-patterns repository-pattern ddd-repositories aggregateroot
Dinah picture Dinah · Dec 24, 2009 · Viewed 120.8k times · Source

I'm trying to get my head around how to properly use the repository pattern. The central concept of an Aggregate Root keeps coming up. When searching both the web and Stack Overflow for help with what an aggregate root is, I keep finding discussions about them and dead links to pages that are supposed to contain base definitions.

In the context of the repository pattern, what is an aggregate root?

Answer

Jeff Sternal picture Jeff Sternal · Dec 24, 2009

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 questions

Difference between a Factory, Provider and a Service?

What is the difference between the terms Factory, Provider and Service? Just getting into NHibernate and its Repository pattern (POCO classes, etc).

Read More
Repository Design Pattern with Dapper

This is maybe more a question for code review rather than stack overflow. I am using Dapper for a MicroORM to retrieve and Save Data to SQL Server 2014. I have got DTO classes in a DTO Proj that represent the …

Read More
NOT using repository pattern, use the ORM as is (EF)

I always used Repository pattern but for my latest project I wanted to see if I could perfect the use of it and my implementation of “Unit Of Work”. The more I started digging I started asking myself the question: "…

Read More