Aggregate root

As explained in Collaborative Software Design: How to facilitate domain modeling decisions

An aggregate root is the designated domain object through which modifications to an aggregate are managed.

How Collaborative Software Design: How to facilitate domain modeling decisions covers it

How deep it goes

Explains consistency boundaries, transactions, invariants, and a simplified implementation, while stopping short of a complete production design.

Examples

Demonstrates ScheduledMovieSeating for seat allocation and ScheduledMovie for ticket capacity and request-size constraints.

What it assumes

Assumes domain objects, business invariants, transactions, and EventStorm modeling; establishes aggregates through a concrete seating scenario.

What you can do after

Apply it by grouping related domain objects and routing invariant-sensitive modifications through one aggregate root.

How it connects

Connects aggregates with domain objects, business invariants, transactions, EventStorm, consistency boundaries, and bounded contexts.

liveBookmanning.com

Read Collaborative Software Design: How to facilitate domain modeling decisions on liveBook Get the book at manning.com

Also explained in

• 

  liveBookmanning.com
  Spring in Action, Sixth EditionThe designated domain object that serves as the entry point for access to the objects within an aggregate.
• 

  liveBookmanning.com
  Simple Object-Oriented Design: Create clean, maintainable applicationsAn aggregate root is the designated domain object through which an aggregate's members and consistency rules are accessed and modified.

Compare how 3 books explain aggregate root →

Related concepts

• domain-driven designused by · Domain-driven design is a software design approach that centers models, structure, and terminology on the concepts, behavior, and boundaries of a problem domain.
• Spring Data R2DBCcontrasts with · Spring Data R2DBC is a Spring Data project that provides repository-based persistence for relational databases through the Reactive Relational Database Connectivity API.
• invariantaddresses · An invariant is a property or condition that remains true across the valid states, operations, or specified transformations of a system or computation.
• consistencyaddresses · Consistency is the property of related data, behavior, outputs, or states agreeing with one another or conforming to defined rules across relevant instances or operations.
• subdocumenthas part · A subdocument is a document nested within another document and stored as part of the containing document.

This explainer was generated by Manning's knowledge graph from the text of Collaborative Software Design: How to facilitate domain modeling decisions. The section links point to the parts of the book it draws on.