Go-Native Durable Execution
dbos.dev
Go-Native Durable Execution
1–10 of 21 posts
Re: Go-Native Durable Execution
#2After spending way too much time debugging runtime problems with python based workflow tools, I’ve been implementing something very similar: DagGo.
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.
Re: Go-Native Durable Execution
#3Very timely for me! I've been looking into a go-based workflow engine. How does DagGo compare to go-workflows? https://cschleiden.github.io/go-workflows/
Re: Go-Native Durable Execution
#4Also check out https://www.restate.dev/. 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.
Re: Go-Native Durable Execution
#5Been 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
Re: Go-Native Durable Execution
#6Very timely for me! I've been looking into a go-based workflow engine. How does DagGo compare to go-workflows? https://cschleiden.github.io/go-workflows/
I landed up creating https://github.com/atmonostorm/derecho 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.
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.
Re: Go-Native Durable Execution
#7[dead]
Re: Go-Native Durable Execution
#8We love Dapr's durabletask-go. https://pkg.go.dev/github.com/dapr/durabletask-go
Re: Go-Native Durable Execution
#9Been 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 s…
> 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-...
Re: Go-Native Durable Execution
#10Been 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 s…
> 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-...
I was referring to this post