Rendered at 05:47:03 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
unsnap_biceps 4 hours ago [-]
I'm a little unclear on this. You say it's a replacement for Temporal, but the GitHub repo says it's a replacement for the temporal python client SDK?
Then in the description you say "This lets you run durable workflows, activities, signals, updates, retries, and recovery without needing any infrastructure except Postgres." but your diagram shows worker nodes outside of the Postgres server, so you do need infrastructure beyond the Postgres instance?
lmz 3 hours ago [-]
I think "without needing any infrastructure" is in contrast to Temporal, which has its own server in front of the storage.
lelandbatey 1 hours ago [-]
I asked the DBOS folks about this before; the idea is that there is no "coordination node", only the workers and the DB. See DBOS folks previously: https://news.ycombinator.com/item?id=45186494
KraftyOne 3 days ago [-]
Hi HN, I'm Peter, creator of DBOSify. Here to answer any questions you have!
raykyri 1 hours ago [-]
Hi! Do you have an example that includes a full agent workflow?
hatefulheart 3 hours ago [-]
You can add a dev dependency in your pyprojec.toml with uv, look it up.
Then in the description you say "This lets you run durable workflows, activities, signals, updates, retries, and recovery without needing any infrastructure except Postgres." but your diagram shows worker nodes outside of the Postgres server, so you do need infrastructure beyond the Postgres instance?