logoalt Hacker News

Go-Native Durable Execution

49 pointsby hmaxdmllast Thursday at 12:17 AM15 commentsview on HN

Comments

erdanielstoday at 1:29 PM

Also 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.

show 1 reply
colek42today at 3:09 PM

We love Dapr's durabletask-go. https://pkg.go.dev/github.com/dapr/durabletask-go

show 1 reply
sklarsatoday at 1:19 PM

Very 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/

show 1 reply
dangoodmanUTtoday at 1:33 PM

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

show 3 replies
barelysapienttoday at 1:07 PM

After 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.

https://github.com/swetjen/daggo

octoclawtoday at 2:10 PM

[dead]