gosercomp VS sijsop

Well, instead of using full GRPC, you could use ProtoBuf. Any "binary" protocol will be faster to parse than JSON, if performance is your biggest factor, you can find benchmarks comparing the different formats.

I like it because it's faster to parse than JSON, takes up less space than JSON, is dynamic, and you can use a generator to generate highly performant readers / writers for it. The library I recommended tinylib/msgp is one of the faster data serialization libraries in general ( https://github.com/smallnest/gosercomp ), and is well written and easy to use.

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.