DBOS

“they don't have SDKs for the languages we use at work”

“which are similar to Erlang processes but with persistent disk storage”

“I personally think DB based OS or more accurately data-centric OS is the way to go”

“Systems like these (durable execution) fit well with agents or LLM driven on demand workflows.”

“DBOS is price-gated as well, and pricing is based on usage whereas River's is not.”

“Same thesis: durable and reliable workflows are hard to manage -- it just doesn't have to be as hard as Temporal makes it be”

“DBOS is much less complexity compared to Temporal. That's the benefit.”

“Making the workflow engine of DBOS depend on the paid component (Conductor) for scaling and recovery makes it a no-go.”

“There's a reason why there is a dedicated team building DBOS, every day.”

“executor elasticity appears to be locked behind license purchase”

“it has made a world of difference building Durable Queues and Long Running, Durable Workflows in Python”

“Much easier to integrate and not nearly as heavyweight for you/your customers.”

“I think we need to keep pushing for best in class open source orchestrtion”

“The beauty of the DBOS solution is that it works great for tiny apps and massive apps”

“It turns your app into its own durable executor using your database for coordination.”

“Right now the messaging is "you shouldn't use DBOS for production unless you are a paying customer"”

“the Go one doesn't support SQLite as a backend for example while the Python one does”

“I'm super excited about the debug workflow we recently enabled when we launched both a skill and MCP server.”

“If you want truly private durable execution, you should check out DBOS.”

“DBOS can guarantee exactly once execution if your API calls are idempotent.”

“do a lot of the heavy lifting to get the idempotency, exactly once and recovery”

“especially if you use a library like DBOS, which only adds a database write”

“DE workflow gives you the same guarantees with far less complexity.”

“It slides right into our existing Postgres usage and has a simple Go SDK.”

“it's much easier to integrate than Temporal and it Just Uses Postgres(tm)”

“DBOS uses in process coordination with a pure language library, which makes it far more performant with a lot less hardware.”

“DBOS is tied to Postgres, right? That wouldn't scale anywhere near where we need either.”

“All the functionality of Temporal without any of the infrastructure.”

“DBOS workflows are fast enough to use interactively for critical tasks like this.”

“form factor matters! Building this as a library was technically tricky, but unlocks a lot of use cases”

“having a good story for workflow evolution is going to be essential for adoption”

“I had to back out when I figured that the observability isn't self hostable yet”

“The Java version looks pretty danged cool paging through the some of the code.”

“I love the product and what you are doing -- it's definitely needed and valuable.”

“It's awesome, looking forward to seeing what that self hostable observability would look like.”

“It’s not clear what part of the functionality is specific to Postgres, and why.”

“You can view your workflows and queues, search/filter them by any number of criteria”

“shame that due to annotation-based API it's gonna be a pain to use in Clojure”

“It has everything you need (queues, crons, easy to understand pure Python).”

“FWIW DBOS is already in production at multiple Fortune 500 companies.”