ergo VS sijsop

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

There's a ton of options. You can look at https://github.com/thejerf/sijsop , perhaps more just because it's a very simple example of what you're asking for than necessarily because it's the perfect choice for everything, though I do use it in real code.

Moreover, because Ergo imports Erlang wholesale, it precludes things where you can send messages over the network and keep their types. Here's one simple example from a library of mine but there are numerous other options, gRPC, protocol buffers, etc. (I link this not because it is amazing code, but just because I have it on hand and personally know where it is. Also, note that as a demo program it demonstrates both typed and untyped receive; the "right" side does an untyped receive on purpose.) It is not necessary to lose types in general to go over a network.

The most efficient option is to send the type separately. I wrote and use sijsop for this, if you want something off-the-shelf.

You might consider https://github.com/thejerf/sijsop , then. About as fast to get going as a network protocol can be.

Personally I tend to use my JSON protocol library for slamming down a quick protocol, and probably use a unix socket if I'm on UNIX or a 127.0.0.1-bound network service if not.