RabbitMQ

Last updated
RabbitMQ
Developer(s) VMware
Stable release
3.13.2 / May 1, 2024;0 days ago (2024-05-01)
Repository github.com/rabbitmq
Written in Erlang
Operating system Cross-platform
Type AMQP, message-oriented middleware
License Mozilla Public License
Website www.rabbitmq.com

RabbitMQ is an open-source message-broker software (sometimes called message-oriented middleware) that originally implemented the Advanced Message Queuing Protocol (AMQP) and has since been extended with a plug-in architecture to support Streaming Text Oriented Messaging Protocol (STOMP), MQ Telemetry Transport (MQTT), and other protocols. [1]

Contents

Written in Erlang, the RabbitMQ server is built on the Open Telecom Platform framework for clustering and failover. Client libraries to interface with the broker are available for all major programming languages. The source code is released under the Mozilla Public License.

Since November 2020, there are commercial offerings available of RabbitMQ, for support and enterprise features: "VMware RabbitMQ OVA", "VMware RabbitMQ" and "VMware RabbitMQ for Kubernetes" (different feature levels) [2] Open-Source RabbitMQ is also packaged by Bitnami [3] and commercially for VMware's Tanzu Application Service.

History

Originally developed by Rabbit Technologies Ltd. which started as a joint venture between LShift and CohesiveFT in 2007, [4] RabbitMQ was acquired in April 2010 by SpringSource, a division of VMware. [5] The project became part of Pivotal Software in May 2013. [6] Which then got acquired back by VMWare in December 2019. [7]

The project consists of:

Examples

This section gives sample programs written in Python (using the pika package) for sending and receiving messages using a queue.

Sending

The following code fragment establishes a connection, makes sure the recipient queue exists, then sends a message and finally closes the connection.

#!/usr/bin/env python3importpikaconnection=pika.BlockingConnection(pika.ConnectionParameters(host="localhost"))channel=connection.channel()channel.queue_declare(queue="hello")channel.basic_publish(exchange="",routing_key="hello",body="Hello World!")print(" [x] Sent 'Hello World!'")connection.close()

Receiving

Similarly, the following program receives messages from the queue and prints them on the screen: (Note: This example does not acknowledge receipt of the message.)

#!/usr/bin/env python3importpikadefcallback(ch,method,properties,body):print(" [x] Received %r"%body)connection=pika.BlockingConnection(pika.ConnectionParameters(host="localhost"))channel=connection.channel()channel.queue_declare(queue="hello")print(" [*] Waiting for messages. To exit press Ctrl+C")channel.basic_consume(queue="hello",on_message_callback=callback)channel.start_consuming()

End-of-support schedule [8]

ReleaseReleasedCommunity SupportExtended Commercial SupportLatest
3.1322 Feb 2024Ends 01 Mar 2025Ends 01 Sep 20253.13.0

(22 Feb 2024)

3.1201 Jun 2023Ends 30 Jun 2024Ends 31 Dec 20243.12.13

(24 Aug 2023)

3.1126 Sep 2022Ended 31 Dec 2023Ends 31 Jul 20243.11.28

(24 Aug 2023)

3.103 May 2022Ended 31 Jul 2023Ended 31 Dec 20233.10.25

(18 Jun 2023)

3.923 Jul 2021Ended 31 Jan 2023Ended 31 Jul 20233.9.29
3.801 Oct 2019Ended 31 Jul 2022Ended 31 Jul 20223.8.35
3.728 Nov 2017Ended 30 Sep 2020Ended 30 Sep 20203.7.28
3.622 Dec 2015Ended 31 May 2018Ended 31 May 20183.6.16
3.511 Mar 2015Ended 31 Oct 2016Ended 31 Oct 20163.5.8
3.421 Oct 2014Ended 31 Oct 2015Ended 31 Oct 20153.4.4
3.302 Apr 2014Ended 31 Mar 2015Ended 31 Mar 20153.3.5
3.223 Oct 2013Ended 31 Oct 2014Ended 31 Oct 20143.2.4
3.11 May 2013Ended 30 Apr 2014Ended 30 Apr 20143.1.5
3.019 Nov 2012Ended 30 Nov 2013Ended 30 Nov 20133.0.4

See also

Related Research Articles

The Jakarta Messaging API is a Java application programming interface (API) for message-oriented middleware. It provides generic messaging models, able to handle the producer–consumer problem, that can be used to facilitate the sending and receiving of messages between software systems. Jakarta Messaging is a part of Jakarta EE and was originally defined by a specification developed at Sun Microsystems before being guided by the Java Community Process.

In computer science, message queues and mailboxes are software-engineering components typically used for inter-process communication (IPC), or for inter-thread communication within the same process. They use a queue for messaging – the passing of control or of content. Group communication systems provide similar kinds of functionality.

Message-oriented middleware (MOM) is software or hardware infrastructure supporting sending and receiving messages between distributed systems. MOM allows application modules to be distributed over heterogeneous platforms and reduces the complexity of developing applications that span multiple operating systems and network protocols. The middleware creates a distributed communications layer that insulates the application developer from the details of the various operating systems and network interfaces. APIs that extend across diverse platforms and networks are typically provided by MOM.

Microsoft Message Queuing (MSMQ) is a message queue implementation developed by Microsoft and deployed in its Windows Server operating systems since Windows NT 4 and Windows 95. Windows Server 2016 and Windows 10 also includes this component. In addition to its mainstream server platform support, MSMQ has been incorporated into Microsoft Embedded platforms since 1999 and the release of Windows CE 3.0.

IBM MQ is a family of message-oriented middleware products that IBM launched in December 1993. It was originally called MQSeries, and was renamed WebSphere MQ in 2002 to join the suite of WebSphere products. In April 2014, it was renamed IBM MQ. The products that are included in the MQ family are IBM MQ, IBM MQ Advanced, IBM MQ Appliance, IBM MQ for z/OS, and IBM MQ on IBM Cloud. IBM MQ also has containerised deployment options.

Mule is a lightweight enterprise service bus (ESB) and integration framework provided by MuleSoft. It has a Java-based platform and can also act as broker for interactions between other platforms such as .NET using web services or sockets.

The Advanced Message Queuing Protocol (AMQP) is an open standard application layer protocol for message-oriented middleware. The defining features of AMQP are message orientation, queuing, routing, reliability and security.

<span class="mw-page-title-main">Message broker</span> Computer program module

A message broker is an intermediary computer program module that translates a message from the formal messaging protocol of the sender to the formal messaging protocol of the receiver. Message brokers are elements in telecommunication or computer networks where software applications communicate by exchanging formally-defined messages. Message brokers are a building block of message-oriented middleware (MOM) but are typically not a replacement for traditional middleware like MOM and remote procedure call (RPC).

Simple Text Oriented Message Protocol (STOMP), formerly known as TTMP, is a simple text-based protocol, designed for working with message-oriented middleware (MOM). It provides an interoperable wire format that allows STOMP clients to talk with any message broker supporting the protocol.

Fault Tolerant Messaging in the context of computer systems and networks, refers to a design approach and set of techniques aimed at ensuring reliable and continuous communication between components or nodes even in the presence of errors or failures. This concept is especially critical in distributed systems, where components may be geographically dispersed and interconnected through networks, making them susceptible to various potential points of failure.

The broker pattern is an architectural pattern that can be used to structure distributed software systems with decoupled components that interact by remote procedure calls. A broker component is responsible for coordinating communication, such as forwarding requests, as well as transmitting results and exceptions.

A message queueing service is a message-oriented middleware or MOM deployed in a compute cloud using software as a service model. Service subscribers access queues and or topics to exchange data using point-to-point or publish and subscribe patterns.

Spring was a software company founded by Rod Johnson, who also created the Spring Framework, an open-source application framework for enterprise Java applications. VMware purchased Spring for $420 million in August 2009.

HornetQ is an open-source asynchronous messaging project from JBoss. It is an example of Message-oriented middleware. HornetQ is an open source project to build a multi-protocol, embeddable, very high performance, clustered, asynchronous messaging system. During much of its development, the HornetQ code base was developed under the name JBoss Messaging 2.0.

ZeroMQ 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. The library's API is designed to resemble Berkeley sockets.

<span class="mw-page-title-main">Apache ActiveMQ</span> Software message broker

Apache ActiveMQ is an open source message broker written in Java together with a full Java Message Service (JMS) client. It provides "Enterprise Features" which in this case means fostering the communication from more than one client or server. Supported clients include Java via JMS 1.1 as well as several other "cross language" clients. The communication is managed with features such as computer clustering and ability to use any database as a JMS persistence provider besides virtual memory, cache, and journal persistency.

MQTT is a lightweight, publish-subscribe, machine to machine network protocol for message queue/message queuing service. It is designed for connections with remote locations that have devices with resource constraints or limited network bandwidth, such as in the Internet of Things (IoT). It must run over a transport protocol that provides ordered, lossless, bi-directional connections—typically, TCP/IP, but also possibly over QUIC. It is an open OASIS standard and an ISO recommendation.

<span class="mw-page-title-main">Celery (software)</span> Distributed task queue

Celery is an open source asynchronous task queue or job queue which is based on distributed message passing. While it supports scheduling, its focus is on operations in real time.

MQTT is an ISO standard publish–subscribe-based messaging protocol. It works on top of the Internet protocol suite TCP/IP. It is designed for connections with remote locations where a "small code footprint" is required or the network bandwidth is limited. The publish-subscribe messaging pattern requires a message broker.

<span class="mw-page-title-main">Apache RocketMQ</span> Open-source stream processing platform

RocketMQ is a distributed messaging and streaming platform with low latency, high performance and reliability, trillion-level capacity and flexible scalability. It is the third generation distributed messaging middleware open sourced by Alibaba in 2012. On November 21, 2016, Alibaba donated RocketMQ to the Apache Software Foundation. Next year, on February 20, the Apache Software Foundation announced Apache RocketMQ as a Top-Level Project.

References

  1. ↑ Which protocols does RabbitMQ support?
  2. ↑ "VMware RabbitMQ" . Retrieved 5 May 2023.
  3. ↑ "RabbitMQ". bitnami.com. Retrieved 2023-05-08.
  4. ↑ "Launch of RabbitMQ Open Source Enterprise Messaging" (PDF). Press release. February 8, 2007. Retrieved October 23, 2013.
  5. ↑ "Rabbit Technologies announce acquisition by SpringSource". Press release. April 13, 2010. Archived from the original on April 18, 2010. Retrieved October 3, 2013.
  6. ↑ "Proudly part of Pivotal". Press release. May 14, 2010. Archived from the original on June 2, 2013. Retrieved October 3, 2013.
  7. ↑ "VMware Completes Acquisition of Pivotal". VMware News and Stories. Retrieved 2023-04-06.
  8. ↑ "RabbitMQ". endoflife.date. Retrieved 2023-04-14.

Further reading

This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.