Saga Pattern - Choreography

Services publish and react to events without a central coordinator.

transactions

Detailed Description

Choreography works well when each service can react independently to domain events.

The challenge is understanding the full workflow because no single service owns the whole state machine.

OrderCreated
-> PaymentService charges
-> StockService reserves
Failure -> compensating events

Pros

Decentralized, resilient, low coupling

Cons

Harder to visualize and debug

Examples: Kafka choreography, EventBridge rules