resonate-external-system-of-record-pattern-rust

To prevent duplicate side effects in durable Rust workflows, write to the external system of record first using idempotency keys and checkpointed ctx.run leaf calls, ensuring dependent operations execute only after durable commits succeed.

Keeping Resonate Rust workflows consistent with PostgreSQL requires inserting idempotent order rows using ON CONFLICT SQL patterns before triggering side effects, making the database the ground truth and preventing contradictory workflow states during retries.

Type-dispatched dependency injection in Rust registers dependencies like PgPool and Stripe clients in the ephemeral world, then retrieves them as Arc<T> inside durable functions, providing shared state access without breaking workflow determinism.

Yes, you can use TigerBeetle as a system of record for payment ledger transfers by applying deterministic ledger transfer IDs for idempotency, ensuring at-most-once external effects and deduplication when Resonate workflows retry.

You need idempotency keys for at-least-once execution in Rust workflows whenever durable functions interact with external durable stores like PostgreSQL or Stripe, preventing duplicate order creation, payment charges, or conflicting ledger outcomes during automatic retries.

Yes, this Rust pattern supports Stripe payment charging with external deduplication by enforcing system-of-record-first writes to PostgreSQL, then enqueuing checkpointed dependent side effects to Stripe only after the durable database commit succeeds.