3 ms·

Previous discussion on bitly blog / reddit with some comparisons to zmq: http://www.reddit.com/r/programming/comments/117dsj/nsq_realtime_distributed_message_pr

• matticakes 12y ago
  (project author) I appreciate all the work that Tyler has put into his series of blog posts on messaging systems (and NSQ bug reports!) but I think this particular article is one that misses the mark [1]. While raw performance is important, I think comparing the guarantees and related operational and development semantics are far more interesting and useful. These systems vary a great deal in the interfaces and functionality they expose to users building on top of them and operators dealing with them when they're deployed in production (and inevitably break!). This is ultimately what matters most. P.S. single node (localhost) performance is essentially useless. Most of these tools are designed to be deployed as the backbone of large distributed systems (NSQ in particular), so scalability and performance in that context is a better indication of real-world performance. [1] He's since posted this follow-up that outlines many of the same things http://www.bravenewgeek.com/benchmark-responsibly/ http://www.bravenewgeek.com/benchmark-responsibly/
• fpp 12y ago
  Best overview of available msg queues I know is http://queues.io/ http://queues.io/ - always a good starting point to find information.