Domain event
A domain event is a record of a significant occurrence or change in a business domain that may prompt subsequent behavior or decisions.
Collaborative Software Design: How to facilitate domain modeling decisions
A domain event is a record of a significant occurrence in a business domain that may be relevant to subsequent behavior or decisions.
- How it is used
- Maps business conversations and scenarios onto a shared timeline during EventStorming and requirements discussions.
- How deep it goes
- Defines past-tense, stakeholder-relevant events and gives a facilitated capture-to-timeline procedure, while deferring technical concerns.
- Examples
- Uses cinema ticket purchase, payment, and seat reservation, contrasted with database loss and DDOS attack.
- What you can do after
- Practice/perform it by capturing stakeholder-relevant past events and merging them into a scenario timeline.
Clean Applications with Hexagonal Architecture
An immutable representation of a significant occurrence expressed in the language of the business domain.
- How it is used
- Separates a primary domain state change from independently attached secondary reactions in a hexagonal application.
- How deep it goes
- Works through event generation, publication, listeners, transaction timing, and boundary contracts, while limiting aggregate-list ordering guarantees to one in-process sequence.
- Examples
- Uses article publication, subscriber notifications, publication statistics, analytics, and aggregate event-draining tests.
- What you can do after
- Apply domain events by recording them in an aggregate, publishing after persistence, and routing reactions through listeners.
Read how Clean Applications with Hexagonal Architecture explains domain event →
Microservices Patterns, Second Edition
An event representing a business-significant state change of a domain entity or aggregate.
- How it is used
- Uses domain events to coordinate business changes and supply data for CQRS views.
- How deep it goes
- Defines domain events, distinguishes integration events, and details provider event fields and handler responsibilities.
- Examples
- Uses order creation, customer credit reservation, and an order history view to illustrate events and their data.
- What you can do after
- Evaluate whether saga events represent domain changes and design provider event data for a CQRS view.
Read how Microservices Patterns, Second Edition explains domain event →
Build High Value Software Systems
A record of a significant occurrence in a business domain that other parts of a system can respond to.
- How it is used
- Use domain events to communicate between bounded contexts and feed a reporting projection.
- How deep it goes
- Defines an event through a Java record and traces its use in a projection, without detailing the full implementation.
- Examples
- Models ReservationPlaced with reservation details and uses it to support cross-center inventory visibility.
- What you can do after
- Understand how to model a reservation event and use it to update a reporting projection.
Read how Build High Value Software Systems explains domain event →
Also covered in
What to know first
- aggregateA domain-driven design aggregate is a cluster of related domain objects treated as a unit for consistency and state changes, typically accessed through a designated root.
- use caseA use case is a goal-oriented interaction or application scenario that describes how a system is expected to support an actor or practical objective.
Related concepts
- integration eventproduces · An integration event is a published event exchanged across service boundaries to communicate an occurrence, an operation result, or data relevant to other services.
- aggregateproduced by · A domain-driven design aggregate is a cluster of related domain objects treated as a unit for consistency and state changes, typically accessed through a designated root.
- application layerused by · A software layer that coordinates application operations and use cases above the domain layer.
- backlog refinement meetinguses · Backlog refinement is a collaborative activity for clarifying, detailing, estimating, splitting, and ordering items in a product backlog.
- decorator design patterncontrasts with · The decorator design pattern adds behavior or responsibilities to an object by wrapping it in another object that preserves its interface.
- domain serviceproduced by · A domain service is a stateless component that encapsulates business logic not naturally belonging to a single entity or value object.
Questions about domain event
What is domain event?
A domain event is a record of a significant occurrence or change in a business domain that may prompt subsequent behavior or decisions.
Which Manning books explain domain event?
Collaborative Software Design: How to facilitate domain modeling decisions, Clean Applications with Hexagonal Architecture, Microservices Patterns, Second Edition and Build High Value Software Systems.
What should I know before learning domain event?
Manning books that teach domain event usually introduce aggregate and use case first.
What is the difference between domain event and decorator design pattern?
A domain event is a record of a significant occurrence or change in a business domain that may prompt subsequent behavior or decisions. The decorator design pattern adds behavior or responsibilities to an object by wrapping it in another object that preserves its interface.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.



