nng VS distributed-process-tests

I just published the other day some bindings to the NNG message passing library (https://nng.nanomsg.org/). You can do request/reply, publish/subcribe and other communication patterns. It's trivial to serialize (with Binary for example) any data structure and pass it around the network:

I put together quickly a binding to the NNG! library, it's simply a fork of the existing binding to Nanomsg! updated to work with NNG using the "compatible API". For basic usage seems to work pretty well:

I’m considering using msgpack + nng or msgpack + zmq

I've found NNG to be high quality, also has less restrictive license. https://nng.nanomsg.org/

for communication between a Discord bot and other applications on the same machine I have used ZeroMQ - relatively easy to use, very portable but still flexible enough. (I've heard though that ZeroMQ has been somewhat superseded by nng nowadays)

I agree with this, but would add NNg as a good messaging library. It’s the successor to the spiritual successor of ZeroMQ.

you can also look into https://github.com/nanomsg/nng

I just pushed a stack.yaml file that lets distributed-process compile with lts-20.19. It's here: https://github.com/haskell-distributed/distributed-process/blob/master/stack-ghc-9.2.7.yaml