←back to thread

Absurd Workflows: Durable Execution with Just Postgres

(lucumr.pocoo.org)
25 points ingve | 2 comments | 03 Nov 25 09:17 UTC | HN request time: 0.001s | source
Show context
oulipo2 ◴[03 Nov 25 09:39 UTC] No.45797356[source]▶
Other question: why reimplementing your framework, rather than using an existing agent framework like Claude + MCP, or OpenAI + tool calling? Is it because you're using your own LM models, or just because you wanted more control on retries, etc?
replies(1): >>45797387 #
the_mitsuhiko ◴[03 Nov 25 09:44 UTC] No.45797387[source]▶
There are not that many agent frameworks around at the moment. If you want to be provider independent you most likely either use pydantic AI or the vercel AI SDK would be my guess. Neither one have built-in solution for durable execution so you end up driving the loop yourself. So it's not that I don't use these SDKs, it's just that I need to drive the loop myself.
replies(2): >>45797439 #>>45803393 #
1. jedberg ◴[03 Nov 25 19:35 UTC] No.45803393[source]▶
> If you want to be provider independent you most likely either use pydantic AI ... Neither one have built-in solution for durable execution

PydanticAI has DBOS built in [0].

[0] https://ai.pydantic.dev/durable_execution/dbos/

replies(1): >>45804423 #
2. the_mitsuhiko ◴[03 Nov 25 21:05 UTC] No.45804423[source]▶
Oh interesting, maybe this makes for a better example then. If it has DBOS and Temporal it must be exposing some way to drive the loop. I'll investigate.