Decide: adopt a durable execution engine or keep the hand-built one #1997

Closed
opened 2026-11-14 14:42:49 +00:00 by sam · 2 comments
Owner

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.

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.
sam added the decisionhigh labels 2026-11-14 14:42:49 +00:00
sam added a new dependency 2026-11-14 14:43:00 +00:00
Author
Owner

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.

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.
sam closed this issue 2026-11-15 05:37:58 +00:00
Author
Owner

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.

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.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Reference: sam/archie#1997