Durable execution without history replay

Snapshotting programs is also what https://github.com/pydantic/monty enables and aims for.

FWIW, I think we'll see a rise of AI-ready interpreters. In some sense, I like that it challenges traditional microservice architectures as an aside.

Durable execution looks a bit like a buzzword in general. If your state is defined in the execution graph then it's just an umbrella name for a group of pre-existing algorithms and patterns (e.g. exactly-once transactions in bookkeeping are centuries old). If your state is undefined then what are you resuming to? The snapshot just before the crash likely leads to the undefined state again, in which case you're durably automating the crash (or even worse, uncaught incorrect behavior).

dropping history replay would remove so much operational pain from durable workflows. how do you reconstruct in-flight state after a crash, snapshotting or something event sourced

Kind of reminds me of how redis forks itself to have a snapshot to persist as a backup.

Lamport & Chandy, right?

[dead]

[flagged]

[flagged]