Which description matches the Event SAGA pattern?

• A. Each API creates an event and sends it to the next one; No API is responsible for all
• B. If you have 3 APIs, one generates an event then sends it to another payment API. This will receive and generate a success and send it to delivery
• C. Every event is passed from API to API
• D. In SAGA one API is responsible for everything. One Experience API is responsible for all others and if there is a failure the main API will take the error

Answer: (A)

In an event-driven SAGA (choreography), each service performs its own local transaction and then emits an event to trigger the next service. No single API owns the entire workflow; the process unfolds through a chain of events, with each step responsible for its part and passing control along to the next. This decoupled flow enables loose coupling and eventual consistency.

The described option fits this pattern best because it states that each API creates an event and sends it to the next one, with no API responsible for all steps. The other descriptions point to centralized control or overly simplistic event passing, which don’t capture the distributed, event-driven nature of a SAGA.