Skip to content

Glossary

Short, plain definitions. Follow the links for the full notes.

accidental complexity

Complexity caused by design choices that no longer fit, as opposed to complexity inherent in the business. Remove it. See Chapter 11.

active record

An object that holds a data structure and knows how to load and save itself. It suits simple logic over complex data. See Chapter 5.

aggregate

A cluster of entities and value objects that guards its own consistency. It is changed only through its root’s commands and saved as one transaction. See Chapter 6.

aggregate root

The single entry-point entity of an aggregate. Inner objects are changed only through it. See Chapter 6.

anticorruption layer

A translation layer that a downstream context builds so that an upstream model doesn’t leak into its own. See Chapter 4.

big ball of mud

A codebase that grew without structure after many quick fixes and unexamined design decisions. See Chapter 11.

bounded context

An explicit boundary inside which one model and its language stay consistent. It is designed, not discovered, and it also marks a deployable unit and a single team’s ownership. See Chapter 3.

business domain

A company’s main area of activity: what customers pay it for. See Chapter 1.

command

A request to change state, run by an aggregate after it checks the rules. See Chapter 6.

conformist

An integration where the downstream side adopts the upstream model as it is. See Chapter 4.

context map

A diagram of all bounded contexts and the integration patterns between them. See Chapter 4.

core subdomain

Where the company competes: complex, frequently changing work that sets it apart. Build it in-house. See Chapter 1.

CQRS

Command-Query Responsibility Segregation: one strongly consistent model for changes, plus any number of rebuildable read models. See Chapter 8.

domain event

A past-tense message describing something significant that happened in the business. See Chapter 6.

domain expert

A person who knows how the business really works and is the source of the knowledge being modeled. See Chapter 1.

domain model

An object model that puts data and behavior together to handle complex business logic. See Chapter 6.

domain service

A stateless object for business logic that belongs to no single aggregate, often a calculation that reads several. See Chapter 6.

entity

An object identified by an ID rather than its values, whose state changes over time. See Chapter 6.

essential complexity

Complexity inherent in the business domain itself. Manage it with DDD tools rather than trying to remove it. See Chapter 11.

event sourcing

Storing every state change as an event and deriving state by replaying the events. See Chapter 7.

event store

An append-only database of events, with fetch-by-ID and append-with-expected-version. See Chapter 7.

EventStorming

A sticky-note workshop for mapping a business process as a timeline of domain events, then adding commands, policies, aggregates and contexts. See Chapter 12.

generic subdomain

A complex but already-solved problem that every company handles the same way. Buy or adopt it. See Chapter 1.

heuristic

A rule of thumb that is good enough to decide quickly without being guaranteed correct. See Chapter 10.

idempotent

Giving the same result however many times it is repeated. See Chapter 5.

layered architecture

Presentation, business logic and data access layers, each depending only on the layer below. See Chapter 8.

migration event

A single explicit event that starts an event stream for data migrated from a state-based system. See Chapter 11.

model

A purposeful simplification that keeps only what a specific problem needs. See Chapter 2.

open-host service

An integration where the upstream side exposes a consumer-friendly published language, separate from its internal model. See Chapter 4.

optimistic concurrency

Saving a change only if the data hasn’t changed since it was read, usually checked with a version number. See Chapter 6.

outbox

Saving new events in the same transaction as the state change, then having a relay publish them. Delivery is at least once. See Chapter 9.

partnership

An integration where two teams coordinate changes in both directions as they come up. See Chapter 4.

pivotal event

An EventStorming event that marks a change of phase in a process. It often hints at a bounded-context boundary. See Chapter 12.

policy (EventStorming)

An automation rule saying ‘when this event happens, run that command’. See Chapter 12.

ports & adapters

An architecture where the core defines interfaces (ports) and infrastructure implements them (adapters). Also called hexagonal, onion or clean architecture. See Chapter 8.

process manager

An explicitly started, stateful coordinator whose business logic decides each next step of a multi-step process. See Chapter 9.

projection

A state or read model derived from events or from the command model. See Chapter 7 and Chapter 8.

published language

The public, integration-focused model exposed by an open-host service. See Chapter 4.

read model (EventStorming)

The information an actor looks at before issuing a command. See Chapter 12.

saga

A process spanning several transactions that reacts to events with commands and compensates on failure. See Chapter 9.

separate ways

Choosing to duplicate a capability instead of integrating it. See Chapter 4.

shared kernel

A small piece of model that several contexts share and change together. See Chapter 4.

snapshot

A cached projection that lets you replay only the newer events, as an optimization. See Chapter 7.

subdomain

A smaller area of business activity: core, generic or supporting. It is discovered, not designed. See Chapter 1.

supporting subdomain

A simple, necessary activity with no competitive value. Build it cheaply or outsource it. See Chapter 1.

testing diamond

A testing strategy weighted toward integration tests. It suits active record. See Chapter 10.

testing pyramid

A testing strategy weighted toward unit tests. It suits domain models. See Chapter 10.

transaction script

One procedure per system operation, each running as an all-or-nothing transaction. See Chapter 5.

ubiquitous language

The shared business vocabulary used by everyone on the project, with one meaning per term inside a bounded context. See Chapter 2.

value object

An immutable object defined entirely by its values, with no ID. See Chapter 6.

Short, plain definitions. Follow the links for the full notes.

active record

An object that holds a data structure and knows how to load and save itself. It suits simple logic over complex data. See Chapter 5.

aggregate

A cluster of entities and value objects that guards its own consistency. It is changed only through its root’s commands and saved as one transaction. See Chapter 6.

aggregate root

The single entry-point entity of an aggregate. Inner objects are changed only through it. See Chapter 6.

anticorruption layer

A translation layer that a downstream context builds so that an upstream model doesn’t leak into its own. See Chapter 4.

bounded context

An explicit boundary inside which one model and its language stay consistent. It is designed, not discovered, and it also marks a deployable unit and a single team’s ownership. See Chapter 3.

business domain

A company’s main area of activity: what customers pay it for. See Chapter 1.

command

A request to change state, run by an aggregate after it checks the rules. See Chapter 6.

conformist

An integration where the downstream side adopts the upstream model as it is. See Chapter 4.

context map

A diagram of all bounded contexts and the integration patterns between them. See Chapter 4.

core subdomain

Where the company competes: complex, frequently changing work that sets it apart. Build it in-house. See Chapter 1.

CQRS

Command-Query Responsibility Segregation: one strongly consistent model for changes, plus any number of rebuildable read models. See Chapter 8.

domain event

A past-tense message describing something significant that happened in the business. See Chapter 6.

domain expert

A person who knows how the business really works and is the source of the knowledge being modeled. See Chapter 1.

domain model

An object model that puts data and behavior together to handle complex business logic. See Chapter 6.

domain service

A stateless object for business logic that belongs to no single aggregate, often a calculation that reads several. See Chapter 6.

entity

An object identified by an ID rather than its values, whose state changes over time. See Chapter 6.

event sourcing

Storing every state change as an event and deriving state by replaying the events. See Chapter 7.

event store

An append-only database of events, with fetch-by-ID and append-with-expected-version. See Chapter 7.

generic subdomain

A complex but already-solved problem that every company handles the same way. Buy or adopt it. See Chapter 1.

idempotent

Giving the same result however many times it is repeated. See Chapter 5.

layered architecture

Presentation, business logic and data access layers, each depending only on the layer below. See Chapter 8.

model

A purposeful simplification that keeps only what a specific problem needs. See Chapter 2.

open-host service

An integration where the upstream side exposes a consumer-friendly published language, separate from its internal model. See Chapter 4.

optimistic concurrency

Saving a change only if the data hasn’t changed since it was read, usually checked with a version number. See Chapter 6.

outbox

Saving new events in the same transaction as the state change, then having a relay publish them. Delivery is at least once. See Chapter 9.

partnership

An integration where two teams coordinate changes in both directions as they come up. See Chapter 4.

ports & adapters

An architecture where the core defines interfaces (ports) and infrastructure implements them (adapters). Also called hexagonal, onion or clean architecture. See Chapter 8.

process manager

An explicitly started, stateful coordinator whose business logic decides each next step of a multi-step process. See Chapter 9.

projection

A state or read model derived from events or from the command model. See Chapter 7 and Chapter 8.

published language

The public, integration-focused model exposed by an open-host service. See Chapter 4.

saga

A process spanning several transactions that reacts to events with commands and compensates on failure. See Chapter 9.

separate ways

Choosing to duplicate a capability instead of integrating it. See Chapter 4.

shared kernel

A small piece of model that several contexts share and change together. See Chapter 4.

snapshot

A cached projection that lets you replay only the newer events, as an optimization. See Chapter 7.

subdomain

A smaller area of business activity: core, generic or supporting. It is discovered, not designed. See Chapter 1.

supporting subdomain

A simple, necessary activity with no competitive value. Build it cheaply or outsource it. See Chapter 1.

transaction script

One procedure per system operation, each running as an all-or-nothing transaction. See Chapter 5.

ubiquitous language

The shared business vocabulary used by everyone on the project, with one meaning per term inside a bounded context. See Chapter 2.

value object

An immutable object defined entirely by its values, with no ID. See Chapter 6.