resonate-saga-pattern-rust

Distributed transactions with compensating rollback actions in Rust pair ordered forward steps with reverse compensations using Result-based error propagation and match-based enum dispatch, ensuring multi-step workflows unwind safely during partial failures.

A saga resumes after a worker crash because each forward step creates a durable checkpoint, allowing the Rust durable workflow to recover state and continue processing or execute compensating actions from the last successful checkpoint.

Idempotent compensations for distributed transactions are needed when reverse rollback actions might retry due to timeouts or transient failures, preventing duplicate state changes when unwinding steps like payment captures or inventory reservations.

The best way to handle inventory reservation, payment capture, and shipment creation in a Rust saga is using manual catch-and-compensate control flow, orchestrating ordered durable forward steps and automatically reverting completed steps if a later step fails.

Yes, the Rust Resonate durable SDK supports configurable timeouts and retries for saga compensation operations, ensuring realistic order processing scenarios complete reliably or trigger idempotent compensating rollbacks.

Dispatch reverse compensations using enum-based match statements in Rust by mapping each forward step Result outcome to its corresponding rollback action, directing the saga to unwind specific completed operations via manual catch-and-compensate control flow.