Also check out <a href="https://www.restate.dev/" rel="nofollow">https://www.restate.dev/</a>. We chose this internally after evaluating it against temporal, hatchet, and dbos. The docs are pretty good and development locally and deployment to k8s was simple.
A thing to note is that Restate is not open-source (BSL) while dbos (core, anyway) and temporal are. (Haven't heard of hatchet before.)<p>On the other hand, durable execution in dbos is implemented in libraries so you have different features for different languages (the Go one doesn't support SQLite as a backend for example while the Python one does), whereas Temporal and Restate are not embedded like this.
We love Dapr's durabletask-go. <a href="https://pkg.go.dev/github.com/dapr/durabletask-go" rel="nofollow">https://pkg.go.dev/github.com/dapr/durabletask-go</a>
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.<p>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
> but they do write this like Temporal… doesn’t exist<p>See "DBOS vs. other systems" on the github repository page[1]<p>1: <a href="https://github.com/dbos-inc/dbos-transact-golang?tab=readme-ov-file#dbos-vs-other-systems" rel="nofollow">https://github.com/dbos-inc/dbos-transact-golang?tab=readme-...</a>
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.
After spending way too much time debugging runtime problems with python based workflow tools, I’ve been implementing something very similar: DagGo.<p>DagGo is a type based workflow tool with observably written in Go. Jobs are compile time safe. I’m planning to bring it to feature parity with tools like Dagster over the next few months.<p><a href="https://github.com/swetjen/daggo" rel="nofollow">https://github.com/swetjen/daggo</a>
Very timely for me! I've been looking into a go-based workflow engine. How does DagGo compare to go-workflows? <a href="https://cschleiden.github.io/go-workflows/" rel="nofollow">https://cschleiden.github.io/go-workflows/</a>
I landed up creating <a href="https://github.com/atmonostorm/derecho" rel="nofollow">https://github.com/atmonostorm/derecho</a> to answer the question of "in-process temporal.io". Works pretty well, with some unique features (error-controlled retry behavior) that temporal can't do.<p>I've used it pretty heavily in production, ~30m workflows of various types from various projects through it at this point. No capacity to support it as OSS though, and my internal persistence backend isn't easily extricable from monorepo, but it's just an interface with conformance tests.
[dead]