Decide: adopt a durable execution engine or keep the hand-built one #1997
Notifications
Due Date
No due date set.
Blocks
Reference: sam/archie#1997
Reference in new issue
Block a user
Runs must survive restarts and wait days for an answer, and a restart must never execute the same action twice; an action whose outcome can't be confirmed is marked unknown and the owner is asked. Evaluate adopting a durable execution engine (DBOS's Go SDK, Restate, Temporal) against the current engine on those requirements, the self-contained constraint, and what it would replace. The earlier spike #1097 is an input. This feeds the architecture document in sam/archie-product.
Done when: a decision is recorded with the evidence, and either an adoption issue or a reason to keep the current engine.
Spec: principle 8, R15, R31.
Decided in ARCHITECTURE.md section 2.2 (private sam/archie-product): Archie keeps its own durable engine, reshaped around step checkpoints in Postgres, with leases, durable timers and waits, and idempotency keys. DBOS, Temporal, Restate and LangGraph were rejected there with reasons. The spike input from #1097 is superseded by that decision.
Evaluation is in ARCHITECTURE.md section 2.2.1 (adopt an engine or keep ours). Recommendation: keep the engine and close its two gaps, filed as #2014 (a run is pinned to the workflow version it started with) and #2015 (a crash mid-action marks the action unknown). Both are dependencies of #1977. The decision itself is left to the maintainer.