ZeroMQ: High-Performance Concurrency Framework
ZeroMQ is a versatile open-source messaging library supporting various messaging patterns and multiple transports. It excels in high-speed asynchronous I/O and is utilized by companies like Microsoft and Facebook.
Read original articleZeroMQ is an open-source messaging library offering sockets for transmitting atomic messages across various transports. It supports patterns like fan-out, pub-sub, and request-reply, making it suitable for clustered products with fast asynchronous I/O capabilities. ZeroMQ is versatile, running on multiple operating systems and offering language APIs. It enables universal connectivity in any language on any platform, with smart patterns like pub-sub and client-server. The library excels in high-speed asynchronous I/O engines and supports multiple transports including inproc, IPC, TCP, UDP, and WebSocket. ZeroMQ boasts a vibrant open-source community and provides a comprehensive guide with numerous examples in various languages. Notable companies like Microsoft, Samsung, and Facebook utilize ZeroMQ in their products.
Related
Some of Martin's rationale here:
https://250bpm.com/blog:23/index.html
ZeroMQ is still widely used and popular, but I am not sure if it is still actively developed.
I may have been doing it wrong, but i personally want to know when clients disconnect/reconnect/etc. the API seems to hide all that from you and your send or recv just block.
Did anybody compare throughput/latency for these approaches? Edit: ... for the basic zmq patterns PUB/SUB, REQ/REP, Client/Server