Designing a Passively Safe API

Re:Designing a Passively Safe API by awildfivreld on Saturday January 31, 2026 @05:10AM (#46835203)

If anyone here wants to do this but don't want to implement all of this yourselves, this "field" is called Durable Execution. Frameworks such as Temporal, Restate and DBOS do a lot of the heavy lifting to get the idempotency, exactly once and recovery to a known state logic here.

[ Parent | on HN ]

Re:Designing a Passively Safe API by fernandopj on Saturday January 31, 2026 @10:22AM (#46837425)

Second this. It's only been a few months since I started deploying Temporal at work, and there's no way that I would try implementing all this in-house.

[ Parent | on HN ]

Re:Designing a Passively Safe API by fsociety on Saturday January 31, 2026 @01:31PM (#46839259)

Yes but one subtle point. Exactly once processing is not possible in these frameworks, they assume execution is idempotent which means at least once.

Now, any system I’ve seen designed around exactly once is complete garbage.

[ Parent | on HN ]

Re:Designing a Passively Safe API by jedberg on Monday February 02, 2026 @12:47AM (#46852846)

> Exactly once processing is not possible in these frameworks

Not entirely true, DBOS can guarantee exactly once execution if your API calls are idempotent.

[ Parent | on HN ]