Integration Event Block
An integration event is a message published across a system or bounded-context boundary.
When To Use It
Use an Integration Event block when one generated service, bounded context, or external system needs to notify another that something happened. A domain event may stay inside one context; an integration event is deliberately published outside it.
Required Data
- Name: past-tense phrase stable enough for other systems, such as Invoice Issued.
- Publisher: context or system that publishes the event.
- Subscribers: contexts or systems expected to consume it.
- Contract payload: fields included in the public message.
- Publishing trigger: domain event, policy, schedule, or external signal that causes publication.
Recommended Data
- Schema version: contract version used by subscribers.
- Delivery semantics: at least once, exactly once where supported, or best effort.
- Retry and dead-letter policy: failure handling for consumers.
- Privacy review: fields that must not leave the context.
- Compatibility notes: how payload changes will be rolled out.
Examples
- Invoice Issued from Billing to Accounting.
- Shipment Dispatched from Fulfilment to Customer Notifications.
- Customer Risk Rating Changed from Risk to Lending.
- Subscription Cancelled from Billing to Entitlements.