Integration event
An integration event is a published event exchanged across service boundaries to communicate an occurrence, an operation result, or data relevant to other services.
Clean Applications with Hexagonal Architecture
A published event contract representing an occurrence in a stable form suitable for consumers across system boundaries.
- How it is used
- Uses integration events to publish facts for consumers across bounded contexts and external systems.
- How deep it goes
- Develops contract design and transactional outbox recording, while leaving the relay implementation outside the complete application example.
- Examples
- Uses an article-publication event with an event ID, article ID, publication time, and creation time.
- What you can do after
- Builds an integration-event contract and records publication intent atomically through an outbox adapter.
Read how Clean Applications with Hexagonal Architecture explains integration event →
Microservices Patterns, Second Edition
An integration event is an event exchanged between services that communicates an operation result or transports data needed by another service.
- How it is used
- Coordinates choreography-based saga participants by transporting data and communicating operation results between services.
- How deep it goes
- Defines payload roles and contrasts domain events, but does not detail event schemas or delivery guarantees.
- Examples
- Uses OrderCreated carrying customerId and orderId, plus events for failed commands and query results.
- What you can do after
- Apply integration events to transport saga data and communicate command failures or query results.
Read how Microservices Patterns, Second Edition explains integration event →
Related concepts
- domain eventproduced by · A domain event is a record of a significant occurrence or change in a business domain that may prompt subsequent behavior or decisions.
- integration modepart of · An integration mode is a way for work or information to cross an architectural boundary, distinguished by waiting and responsibility for continuing work.
- orchestrationcontrasts with · Orchestration is the coordination and management of components, services, or tasks to carry out an operation or workflow.
- synchronous callcontrasts with · A synchronous call is an invocation in which the caller waits for the operation to complete or return a result before continuing.
- factused by · A fact is information or a statement describing an actual occurrence or state of reality.
- eventkind of · A software event is an occurrence, state change, or notification that a system can detect, record, communicate, or handle.
Questions about integration event
What is integration event?
An integration event is a published event exchanged across service boundaries to communicate an occurrence, an operation result, or data relevant to other services.
Which Manning books explain integration event?
Clean Applications with Hexagonal Architecture and Microservices Patterns, Second Edition.
What is the difference between integration event and orchestration?
An integration event is a published event exchanged across service boundaries to communicate an occurrence, an operation result, or data relevant to other services. Orchestration is the coordination and management of components, services, or tasks to carry out an operation or workflow.
What is integration event a kind of?
Integration event is a kind of event. A software event is an occurrence, state change, or notification that a system can detect, record, communicate, or handle.
What is integration event part of?
Integration event is part of integration mode. An integration mode is a way for work or information to cross an architectural boundary, distinguished by waiting and responsibility for continuing work.
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.

