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.
Compare publishing from participant domain logic with publishing from an incoming-event handler. section 10.1.2
