workflows

You orchestrate multi-step business processes with automatic rollback by implementing the saga pattern, which executes discrete compensatable steps and automatically reverses earlier completed operations if a later step fails, ensuring data consistency and atomicity across external side effects and database mutations.

The saga pattern is a sequence of discrete, compensatable steps used to manage complex operations involving multiple side effects. You need it when a business process, such as booking a room and charging a credit card, must either fully succeed or safely roll back all previous steps upon failure.

You ensure safe retries during payment processing and booking workflows by leveraging idempotency keys. This mechanism prevents duplicate side effects and database mutations when a multi-step process is automatically retried after a transient failure.

Yes, this saga orchestration approach supports emitting domain events by integrating directly with an event bus. As the workflow progresses through its defined steps and compensation logic, it emits relevant domain events to keep downstream systems synchronized.

The best way to handle atomicity across multiple external side effects is using a saga orchestration pattern. It defines specific compensation logic for each step, so if a step like sending a confirmation email fails, earlier actions like reserving a room are automatically undone.

You should not use a saga pattern for workflow orchestration if your operations lack reversible side effects or cannot define meaningful compensation logic. Without the ability to undo prior database mutations or external calls, automatic rollback cannot guarantee data consistency.