Aggregates and repository

- [Narrator] Our next artifact of…Domain Driven Design is aggregates.…Aggregate domain pattern is related to object life cycle…and defines ownership and boundaries.…When use of a table in your favorite restaurant online…using any app, you do need to worry about…the internal system and process that explains…to book your reservation such as searching…the available restaurants; then, the available tables…during the given date and time and so on and so forth.…

Therefore, you can say that reservation app…is an aggregate of several other objects…and works as a root for all the other objects…for our table reservation system.…The root should be an entity…that binds collection of objects together.…It is also called the aggregate root.…This root object does not pass any reference…to inside object to external worlds…and protects the changes of phone and internal objects.…

We need to understand why aggregates objects are required.…A domain money can contain large number of domain objects.…The bigger the application functionality and size,…