| Developer: | iMatix |
| Programming Language: | C++ |
| Platform: | Cross-platform |
| Genre: | Message queue, concurrency framework |
| License: | MPL-2.0[1] |
ZeroMQ (also spelled ØMQ, 0MQ or ZMQ) is an asynchronous messaging library, aimed at use in distributed or concurrent applications. It provides a message queue, but unlike message-oriented middleware, a ZeroMQ system can run without a dedicated message broker; the zero in the name is for zero broker.[2] The library's API is designed to resemble Berkeley sockets.
ZeroMQ is developed by a large community of contributors, founded by iMatix, which holds the domain name and trademarks. There are third-party bindings for many popular programming languages.
The ZeroMQ API provides sockets (a kind of generalization over the traditional IP and Unix domain sockets), each of which can represent a many-to-many connection between endpoints. Operating with a message-wise granularity, they require that a messaging pattern be used, and are particularly optimized for that kind of pattern.
The basic ZeroMQ patterns are:
Each pattern defines a particular network topology. Request-reply defines a so-called "service bus", publish-subscribe defines a "data distribution tree", and push-pull defines "parallelised pipeline". All the patterns are deliberately designed in such a way as to be infinitely scalable and thus usable on Internet scale.[3]
Any message through the socket is treated as an opaque blob of data. Delivery to a subscriber can be automatically filtered by the blob leading string. Available message transports include TCP, PGM (reliable multicast), inter-process communication (IPC) and inter-thread communication (ITC).
The ZeroMQ core library performs very well due to its internal threading model, and can outperform conventional TCP applications in terms of throughput by utilizing an automatic message batching technique.[4] [5]
ZeroMQ implements ZMTP, the ZeroMQ Message Transfer Protocol.[6] ZMTP defines rules for backward interoperability, extensible security mechanisms, command and message framing, connection metadata, and other transport-level functionality. A growing number of projects implement ZMTP directly as an alternative to using the full ZeroMQ implementations.[7]
iMatix CEO Pieter Hintjens registered the zeromq.org domain in May 2007 and started the ZeroMQ project together with Martin Sustrik, who was its architect and lead developer until December 2011.
On March 30, 2010, Hintjens announced that iMatix (the original designer of Advanced Message Queuing Protocol) would leave the AMQP workgroup and did not plan to support AMQP/1.0 in favor of the significantly simpler and faster ZeroMQ.[8] [9]
In 2011, CERN was investigating ways to unify middleware solutions used to operate CERN accelerators. The CERN study compared two open source implementations of CORBA, Ice, Thrift, ZeroMQ, YAMI4,[10] RTI, and Qpid (AMQP) and scored ZeroMQ highest, in part for its versatility, including its easy adaptability to the LynxOS.
At the start of 2012, two of the original developers forked ZeroMQ as Crossroads I/O.[11] [12] Martin Sustrik has started nanomsg,[13] a rewrite of the ZeroMQ core library.[14]
In August 2012, Dongmin Yu announced his pure Java conversion of ZeroMQ, JeroMQ.[15] This has inspired further full-native ports of ZeroMQ, such as NetMQ for C#[16] and zmq.rsfor Rust.[17]
In March 2013, Pieter Hintjens announced a new draft of the ZMTP wire-level protocol bringing extensible security mechanisms to ZeroMQ.[18] Martin Hurton implemented the CurveZMQ authentication and encryption mechanism[19] in the core library shortly afterwards.
In 2016, long-time ZeroMQ developer Garrett D'Amore forked Nanomsg to create project NNG (Nanomsg Next Generation).[20]
The ZeroMQ community mostly uses the Collective Code Construction Contract (C4)[21] as a development contract. C4 is inspired by Wikipedia processes and GitHub's fork + pull request model. It focuses on making it simpler for new contributors to participate and reducing dependency on older contributors.