What kind of saga have you worked with in practice?

In practice, the most common approach is saga choreography — where each service component independently reacts to events and makes decisions about the next step, without a central orchestrator. This approach is well-suited for distributed systems where minimizing coupling between services is important.

Example: During the order process, one service publishes an "Order Created" event, and other services (payment, warehouse, delivery) subscribe to these events and perform their actions, publishing new events.

There is also saga orchestration, where a central controller manages the sequence of steps and compensating transactions, which simplifies management but increases coupling.