Inbound communication
The component consumes events from the external system and re-publishes them to the internal event stream to delegate processing to downstream components. The internal event contains the raw contents of the external event for auditing and a transformed version of the content for internal consumption. This interaction follows the Database-First variant of the Event Sourcing pattern and the external system represents the database that is emitting state change events. The component typically leverages the API Gateway pattern to create a RESTful service that can be registered with the external system's webhooks. Alternatively, when the cloud provider offers the external system, the component registers functions with the ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access