Which description matches the Command/Orchestration SAGA pattern?

• A. 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
• B. Each API creates an event and sends it to the next one; No API is responsible for all
• C. Every event is passed from API to API
• D. In SAGA one API is responsible for everything

Answer: (A)

SAGA orchestration relies on a central coordinator that drives the entire long-running transaction by issuing explicit commands to each participating service. The orchestrator defines the sequence, invokes a local transaction in one service, waits for its result, and then instructs the next service to proceed, handling compensations if something goes wrong.

The described flow fits this pattern because there’s a central control flow: one API initiates and directs the subsequent steps two more services must perform, moving the process toward delivery. This centralized coordination contrasts with plain event-driven choreography, where services emit and react to events with no single orchestrator directing the sequence. The idea of one API handling everything is inconsistent with a distributed saga, which involves coordinated work across multiple services.