liveBook · Manning

Event publisher

As explained in Microservices Patterns, Second Edition

An event publisher is a component that emits integration events after a service operation or event handler has processed an input.

An event publisher emits events from a saga participant, allowing services to coordinate through publish/subscribe rather than direct calls. It can publish from domain logic after an operation or from a handler processing an incoming event. section 10.1.2

Create Order Saga

The Order Service and Customer Service publish events to separate channels; an OrderCreated event carries customerId and orderId to the Customer Service. section 10.1.2

Figure 10.4 Events can either be published by the saga participant’s domain logic or by the event handler for the incoming event.
events publishing design

Compare publishing from participant domain logic with publishing from an incoming-event handler. section 10.1.2

How Microservices Patterns, Second Edition covers it

How deep it goes
Identifies publishers as outbound adapters and locates publication in domain logic or event handlers, without detailing implementation mechanics.
Examples
Uses the Create Order Saga, where Order and Customer services publish events and OrderCreated transports customerId and orderId.
How it connects
Connects event publishers with event channels, event handlers, and choreography-based sagas.

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.