Magento 2 RabbitMQ Broker Magento 2 RabbitMQ Broker

RabbitMQ is an open-source message broker software written in Erlang. It enables applications, systems, and services to communicate with each other and exchange information.

RabbitMQ runs on many operating systems and cloud environments and provides developer tools for popular languages.

The software is lightweight and easy to deploy on-premises and in the cloud. It supports multiple messaging protocols. It is deployed in distributed and federated configurations for high-scale, high-availability requirements.

Magento 2 added asynchronous messaging capabilities with RabbitMQ. The advanced message queuing protocols allow web servers to respond to requests quickly. It helps to handle resource-intensive requests efficiently.

How it works

A publisher is a component that sends messages to an exchange. It knows which ‘exchange’ to publish and the message format. An exchange accepts messages from publishers and routes them to message queues.

A queue is a buffer that stores messages. A consumer receives the messages, and it knows which queue to consume. It maps the processors of the message to a specific queue.

Magento 2 RabbitMQ Diagram Magento 2 RabbitMQ Diagram


Magento 2 RabbitMQ Protocols Magento 2 RabbitMQ Protocols

Multi-protocol Support

RabbitMQ supports messaging protocols like AMQP, MQTT, HTTP, and STOMP.

Highly Available Queues Highly Available Queues

Highly Available Queues

RabbitMQ allows replicated queues and streams. It ensures that messages are safe with most cluster nodes online in the event of hardware failure.

RabbitMQ Management UI RabbitMQ Management UI

Management UI

RabbitMQ ships with an easy-to-use management UI. It allows us to monitor and control various aspects of the message broker.

RabbitMQ Plugin System RabbitMQ Plugin System

Plugin System

Shipped with many plugins to improve functionalities. Create and integrate new RabbitMQ plugins from the developers.

RabbitMQ Flexible Routing RabbitMQ Flexible Routing

Flexible Routing

RabbitMQ features built-in exchange types for the typical routing logic. For more complex routing, bind exchanges together or create an exchange type as a plugin.

RabbitMQ Reliability RabbitMQ Reliability


Get various features, including persistence, delivery acknowledgment, publisher confirms, and high availability.


There are several tasks performed within an ecommerce website’s architecture. As a customer places an order from the website, the tasks include -

  • Generating the order
  • Managing payments
  • Inventory management
  • Email and text notifications
  • Sending/Receiving order data to SAP/CRM/ERP systems
  • Sending data to analytics

The activities are performed in real-time. As more time is required to complete the order process, it may affect the business revenue.

RabbitMQ transfers most of these tasks into queues. It is then processed through asynchronous messaging, allowing web servers to respond quickly.

Yes, our team will help install the RabbitMQ service.

The RabbitMQ server is provided in the Auto Scaling plans. On-demand, we install the RabbitMQ server for any of our customers.

We set up the RabbitMQ server to handle receiving and sending messages. Once the RabbitMQ server is ready, developers configure it with Magento 2.

Add the RabbitMQ environment variables via the command line or append them to the env.php file:

  • Host
  • Port
  • User
  • Password
  • Virtualhost
  • Cafile
  • Keyfile

Configuring the message queue topology involves creating and modifying the following configuration files -

  • communication.xml – defines aspects of the message queue system that all communication types have in common.
  • queue_consumer.xml – defines the relationship between an existing queue section and its consumer
  • queue_topology.xml – defines the message routing rules and declares queues and exchanges.
  • queue_publisher.xml – defines the exchange where a topic is published.

Depending on the project’s needs, developers create and configure communication.xml and one or two files.

  • queue_publisher.xml file – to publish an existing queue by a third-party system.
  • queue_consumer.xml config file - to consume from an existing queue.

Messages are not posted directly in the queue. The user sends messages to the exchange. An exchange is responsible for routing the messages to the various queues.

It receives messages from the producer request and sends them by bindings and routing keys to message queues. A binding is an association between an exchange and a queue.