News for hackers. Stuff that matters.
Re:Dbos: Durable Workflow Orchestration with Go and PostgreSQL by plmpsu on Friday October 03, 2025 @03:08AM (#45459938)
Thanks for the reply.

So applications continuously poll the database for work? Have you done any benchmarking to evaluate the throughput of DBOS when running many workflows, activities, etc.?

Re:Dbos: Durable Workflow Orchestration with Go and PostgreSQL by qianli_cs on Friday October 03, 2025 @03:54AM (#45460242)
In DBOS, workflows can be invoked directly as normal function calls or enqueued. Direct calls don't require any polling. For queued workflows, each process runs a lightweight polling thread that checks for new work using `SELECT ... FOR UPDATE SKIP LOCKED` with exponential backoffs to prevent contentions, so many concurrent workers can poll efficiently. We recently wrote a blog post on durable workflows, queues, and optimizations: https://www.dbos.dev/blog/why-postgres-durable-execution

Throughput mainly comes down to database writes: executing a workflow = 2 writes (input + output), each step = 1 write. A single Postgres instance can typically handle thousands of writes per second, and a larger one can handle tens of thousands (or even more, depending on your workload size). If you need more capacity, you can shard your app across multiple Postgres servers.

Re:Dbos: Durable Workflow Orchestration with Go and PostgreSQL by odie5533 on Saturday October 04, 2025 @07:42AM (#45472600)
Even though I don't use DBOS, that blog post is gold.