Entities and Aggregates: The Moment We 'Clicked' and Understood...
summary
The talk explains aggregates in Domain-Driven Design: what distinguishes an aggregate from an aggregate root and an entity, how large aggregates should be, how to return data spanning multiple aggregates, where business logic belongs (inside aggregates, value objects, or domain services), how aggregates relate to read/write models, and how to avoid method explosion. The presenters give their point of view and concrete examples, describing the moment their domain design clicked into a satisfactory approach.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 6:202015 problem and initial fix
- 11:39Entities vs aggregates today
- 19:47N+1 queries causes
- 27:57Key moment and example
- 33:18Anti-corruption layer and repos
- 37:52Folder structure and modules
- 40:41Summary
related talks
46mNot Just Aggregates: How to Design Complex Domain Algebra
50mDeveloping Microservices with Aggregates
35mTrivialization of DDD or Not?
59mDomain-Driven Design - Where Rubber Meets the Road
47mPHP: From Model to Commit - the Short History of an Aggregate
48mThe Aggregate is dead. Long live the Aggregate!
50mThe Aggregate is dead. Long live the Aggregate!
55mDomain-Driven Design: back to the roots