[evancordell]

At the risk of making a classic "I have a few qualms with this app" blunder, I'm not super clear on what this has over other durable workflow solutions.

It seems to take the durable workflow idea and lock you into a specific language, operating system, and database, when other projects in the same space give you choice over those components.

[KraftyOne]

Co-founder here. Thanks for the questions! A couple advantages DBOS has:

1. It's a serverless platform. It manages application deployments, providing a simpler experience than trying to bolt a durable execution framework onto an app deployed on Kubernetes.

2. Transactional guarantees. DBOS does durable execution in the same transactions as your business logic, so it guarantees exactly-once execution for most operations while other workflow solutions are at-least-once. More details here: https://docs.dbos.dev/explanations/how-workflows-work

3. Database time travel, which greatly enhances observability/debugging/recovery. More details here: https://docs.dbos.dev/cloud-tutorials/timetravel-debugging