ØMQ

From Wikipedia, the free encyclopedia
ØMQ
Developer(s) iMatix Corporation
Stable release 3.2.4 / September 20, 2013 (2013-09-20)
Preview release 4.0.0 RC1 / September 20, 2013 (2013-09-20)
Written in C++
Platform Cross-platform
Type Message queue, concurrency framework
License LGPL with static linking exception
Website www.zeromq.org

ØMQ (also spelled ZeroMQ, 0MQ or ZMQ) is a high-performance asynchronous messaging library aimed at use in scalable distributed or concurrent applications. It provides a message queue, but unlike message-oriented middleware, a ØMQ system can run without a dedicated message broker. The library is designed to have a familiar socket-style API.

ØMQ is developed by a large community of contributors, founded by iMatix Corporation, which holds the domain name and trademarks. There are third-party bindings for many popular programming languages.

Technology

The ØMQ 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 ØMQ patterns are:

Request-reply
Connects a set of clients to a set of services. This is a remote procedure call and task distribution pattern.
Publish-subscribe
Connects a set of publishers to a set of subscribers. This is a data distribution pattern.
Push-pull (pipeline)
Connects nodes in a fan-out / fan-in pattern that can have multiple steps, and loops. This is a parallel task distribution and collection pattern.
Exclusive pair
Connects two sockets in an exclusive pair. (This is an advanced low-level pattern for specific use cases.)

Each pattern defines a particular network topology. Request-reply defines so-called "service bus", publish-subscribe defines "data distribution tree", 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.[1]

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 ØMQ 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.[2][3]

ØMQ implements ZMTP, the ZeroMQ Message Transfer Protocol.[4] 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 ØMQ implementations.[5]

History

iMatix CEO Pieter Hintjens registered the zeromq.org domain in May 2007 and started the ØMQ 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 (if it ever emerged) in favor of the significantly simpler and faster ØMQ.[6][7]

In 2011, CERN was investigating ways to unify middleware solutions used to operate CERN accelerators. The CERN study compared CORBA, Ice, Thrift, ØMQ, YAMI4,[8] RTI, and Qpid (AMQP) and scored ØMQ highest, in part for its versatility, including its easy adaptability to the LynxOS.[3]

At the start of 2012, two of the original developers forked ØMQ as Crossroads I/O.[9][10] Martin Sustrik has started nanomsg,[11] a reboot of the ØMQ core library.

In August 2012, Dongmin Yu announced his pure Java conversion of ØMQ, JeroMQ.[12] This has inspired further full-native ports of ØMQ, such as NetMQ for C#.[13]

In March 2013, Pieter Hintjens announced a new draft of the ZMTP wire-level protocol bringing extensible security mechanisms to ØMQ.[14] Martin Hurton implemented the CurveZMQ authentication and encryption mechanism[15] in the core library soon hereafter.

Development process

The ØMQ community mostly uses the Collective Code Construction Contract (C4)[16] 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.

See also

References

  1. ↑ Scalability Layer Hits the Internet Stack
  2. ↑ "How come ØMQ has higher throughput than TCP although it's built on top of TCP?". ZeroMQ FAQ. Retrieved 2013-06-08. 
  3. ↑ 3.0 3.1 "Middleware Trends And Market Leaders 2011". Retrieved 2013-06-08. 
  4. ↑ "ZeroMQ Message Transfer Protocol". Retrieved 2013-06-08. 
  5. ↑ "GitHub Search: ZMTP". Retrieved 2013-06-08. 
  6. ↑ "iMatix will end OpenAMQ support by 2011". openamq-dev maillist. Retrieved 14 July 2012. 
  7. ↑ "What is wrong with AMQP (and how to fix it)". iMatix Corporation. Retrieved 14 July 2012. 
  8. ↑ "Inspirel YAMI4". Retrieved 14 July 2012. 
  9. ↑ "ZeroMQ and Crossroads I/O: Forking over trademarks". LWN.net. Retrieved 14 July 2012. 
  10. ↑ "Crossroads I/O". Retrieved 14 July 2012. 
  11. ↑ "nanomsg". Retrieved 8 June 2013. 
  12. ↑ "jeromq - java pojo zeromq". zeromq-dev mailing list. Retrieved 23 May 2013. 
  13. ↑ "NetMQ". GitHub. Retrieved 23 May 2013. 
  14. ↑ "Securing ZeroMQ: draft ZMTP v3.0 Protocol". Hintjens.com. Retrieved 23 May 2013. 
  15. ↑ curvezmq.org
  16. ↑ "Collective Code Construction Contract (C4.1)". ZeroMQ RFCs. Retrieved 2013-05-23. 

External links

This article is issued from Wikipedia. The text is available under the Creative Commons Attribution/Share Alike; additional terms may apply for the media files.