Durable Handlers And Journaling

A Restate durable handler charges a card by calling Stripe inside the handler body directly (a bare `await stripe.charge(...)`), not wrapped in a durable step. The process crashes after the charge but before the handler's next li…

Wrap every non-deterministic side effect (external HTTP call, random, time, UUID) in ctx.run(...) so its result is journaled. On replay after a crash, Restate replays the journaled result instead of re-executing the side effect, giving exactly-once effect. A bare call outside ctx.run re-executes on…

A handler validates input, finds it invalid, and throws a plain Error. Restate retries the handler indefinitely on the same bad input.

Throw a TerminalError for unrecoverable / business-logic failures (bad input, rejected payment) so Restate stops retrying and fails the invocation; throw / let propagate ordinary errors only for transient faults you want retried with backoff. A plain Error on permanently-bad input causes an infinit…

A handler does ctx.run that returns a 40 MB blob, then stores it again in state. The invocation journal balloons and replays slow down.

Keep journaled values small: store large payloads in object storage and journal only the reference (URL / key), not the bytes. The journal is replayed on every recovery, so large journaled values inflate memory and replay time. Pass blobs by reference between steps. [REQUIRES-VERIFICATION] for the …