nng VS nsq

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

Interesting. What are you thoughts on NSQ?

https://github.com/nsqio/nsq

Was looking at it earlier today, but haven't ever tried it out.

(G)NATS can do millions of messages per second and is the right tool for the job (either that or NSQ). Redis isn't even the fastest Redis protocol implementation, KeyDB significantly outperforms it.

Bit.ly's NSQ is also an excellent message queue option.

Queue consumers are interesting because there are many solutions for them, from using Redis and persisting the data in a data store - but for fast and scalable the approach I would take is something like SQS (as I advocate AWS even free tier) or NSQ for managing your own distributed producers and consumers.

distrubition server engine ( for example websocket server multi ws gateway and worker pool,nsq.io realtime message queue and so on)