Been eager for something that wasn’t temporal (egregious overhead and annoying multiple services), but they do write this like Temporal… doesn’t exist. They use a lot of the same pioneered techniques (like “our own context type”) that they do.

go-workflows has always been the good alternative, but I’m sure dbos is a bit better supported. Dbos always had some weird gaps (I don’t remember why exactly, I just remember saying “oh well I can’t use this then” more than once), but maybe they’ll close them with the go sdk

▲

hmaxdml 4 hours ago | parent | next [-]

Thanks for the comment (author here). I wanted this post to focus on the Golang specific implementation, not dwell on the durable execution ecosystem at large.

With respect to context, I don't know that anyone invented "having their own context". Go interface are extendable and pretty much every major framework I know of implement their own context.

Would love to learn more about the gaps that offset you. We're constantly improving here ;)

	▲	dangoodmanUT 3 hours ago \| parent [-]
		Thanks, I didn't mean it as criticism, I guess my 5am brain thought the way it was worded almost came off as like "look at our unique idea" which was a pretty common pattern.

▲

akahn 5 hours ago | parent | prev | next [-]

> but they do write this like Temporal… doesn’t exist

See "DBOS vs. other systems" on the github repository page[1]

1: https://github.com/dbos-inc/dbos-transact-golang?tab=readme-...

	▲	dangoodmanUT 5 hours ago \| parent [-]
		I was referring to this post

▲

pphysch 4 hours ago | parent | prev [-]

We bounced off dbos when we found they charge $$$ for their CRUD web GUI ("DBOS conductor"), which they also "strongly recommend" for production use, for good reason.

▲

hmaxdml 4 hours ago | parent [-]

Conductor is about enterprise features like automatic workflow recovery, alerting, or RBAC. The GUI is a nice to have -- but all your workflow data are in Postgres. You can access it very easily.

	▲	pphysch 2 hours ago \| parent [-]
		The offering would be enticing if some Web GUI features were behind a paywall. Separate "production" from "enterprise". Right now the messaging is "you shouldn't use DBOS for production unless you are a paying customer", which is odd considering durable execution itself is a production-level concept. So we rolled our own in a few hundred lines of Python.