golem-atomic-block-ts

To make TypeScript side effects replay-safe across crashes, you can group external operations into atomic blocks so that recovery after a failure re-executes the entire block from the start rather than leaving partially completed state.

Durable execution ensures external side effects like HTTP or network I/O operations survive crashes. You need it when grouping multiple observable operations so they replay together from the beginning during recovery.

You group multiple HTTP calls by wrapping them in an atomic block using a TypeScript Golem agent, ensuring that all observable side effects replay together from the start if a crash occurs before completion.

Idempotency keys prevent duplicate side effects during crash recovery by allowing oplog replication and replay behavior to enforce exactly-once style interactions, ensuring external systems do not process the same operation twice.

Yes, Golem supports custom persistence levels for oplog entries, allowing you to define how entries are interpreted and explicitly handle live execution versus replay scenarios in advanced authoring situations.

A limitation of using atomic blocks is that you must explicitly handle live versus replay execution when using custom persistence levels, and complex retry policies may require careful oplog coordination to avoid unexpected replay behavior.