liveBook · Manning

Integration event

As explained in 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.

An integration event communicates between services, transporting data or reporting an operation’s result. In a choreography-based saga, it can resemble a domain event but serves as a transport mechanism. section 10.1.2

Integration events can:

  • Carry request parameters or selected attributes of a corresponding domain event. section 10.1.2
  • Report command failures even when no state change occurs, or convey the result of a data-retrieval query. section 10.1.2
Figure 10.3 In a choreography-based saga, events transport data between participants. For example, the OrderCreated event transports the customerId parameter and the orderId - created by the Order Service - to the Customer Service.
events transport data

The OrderCreated example shows an event carrying customerId and orderId from the Order Service to the Customer Service. section 10.1.2

How Microservices Patterns, Second Edition covers it

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.
How it connects
Connects choreography-based sagas, domain events, publish-subscribe channels, service commands, and service queries.

Also explained in

Compare how 2 books explain integration event →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Microservices Patterns, Second Edition. The section links point to the parts of the book it draws on.