ergo VS sdk-java

Ergo Framework does - https://github.com/ergo-services/ergo

https://github.com/ergo-services/ergo for golang

I think you should clarify what exactly you need. If you need something like TCP/UDP socket acceptor pool you may want to try Ergo Framework with ready to use design patterns https://github.com/ergo-services/ergo . Example for TCP https://github.com/ergo-services/examples/tree/master/gentcp, for UDP https://github.com/ergo-services/examples/tree/master/genudp

In case if you want to feel a flavour of Erlang in Golang - https://github.com/ergo-services/ergo

Besides, something like this already exists, I don’t see the point, but hey to each there own… https://github.com/ergo-services/ergo

Thanks for sharing. Looks good as a first attempt in the long way to production state. You may also want to take a look another approach of actor based implementation https://github.com/ergo-services/ergo

It looked very different than all the other frameworks I have seen. https://github.com/ergo-services/ergo/blob/master/examples/http/app.go

If you love the Erlang way you may want to try ergo framework https://github.com/ergo-services/ergo

How does this compare against Temporal/Cadence/Conductor? Does hatchet also support durable execution?

https://temporal.io/

Flawless sounds a lot like https://temporal.io/ .

I'm wondering if it has the same scalability concerns - sticking everything in Postgres is fine at small-ish scale, but what happens when you outgrow Postgres, either because you have higher availability requirements (can't handle primary DB restarts) or because of the sheer volume of the workload?

Temporal is a scalable and reliable runtime for durable Workflow Executions. It enables you to develop as if failures don't even exist. I started exploring it over the Christmas holiday and using it for a recently open-sourced project.

I have my eyes on https://temporal.io/ for similar purposes.

Check out temporal.io open source project for a much cleaner solution using Durable Execution abstraction.

Interesting to see Netflix featured both on StackStorm & https://temporal.io/ frontpages.

Our stack at Escape is written in multiple languages because each team has specific needs. We use TypeScript for its vibrant ecosystem, Python for cybersecurity research and Go for performance-sensitive tasks. To orchestrate cross-language task orchestration, we first developed a simple request-response protocol over HTTP, but it wasn't sustainable as the Escape codebase grew rapidly. We evaluated several technologies to replace our homegrown protocol, and two emerged as the most promising options: Connect and Temporal. The title gives it away, but the reason is far from obvious

I've put a lot of time into Airflow and feel similarly that it's a huge pain and a risk to rely on it. I've replaced it with Temporal (https://temporal.io/) and while I don't have the breadth of experience with the frameworks you listed, I do think Temporal is a great replacement for Airflow.

Just to confirm my understanding; would you consider at least part of your product offering to be similar to temporal.io [1]? Your examples are reminiscent of theirs.

[1] https://temporal.io/