Azure Service Bus vs RabbitMQ

Overview

RabbitMQ

Stacks21.8K

Followers18.9K

Votes558

GitHub Stars13.2K

Forks4.0K

Azure Service Bus

Stacks553

Followers536

Votes7

Azure Service Bus vs RabbitMQ: What are the differences?

Azure Service Bus and RabbitMQ are both popular message broker services that are widely used in the industry. While they offer similar functionality in terms of message queuing and reliable message delivery, there are several key differences between the two.

Transport Protocol: Azure Service Bus uses the AMQP (Advanced Message Queuing Protocol) 1.0, whereas RabbitMQ uses the AMQP 0.9.1 protocol. This difference in transport protocol affects the compatibility and interoperability with different client libraries and frameworks.
Hosting: Azure Service Bus is a cloud-based messaging service provided by Microsoft Azure, which means it is fully managed and hosted in the cloud. On the other hand, RabbitMQ is an open-source message broker that needs to be installed and managed on-premises or in a cloud environment.
Message Patterns: Azure Service Bus supports publish/subscribe, request/reply, and temporal decoupling of publishers and subscribers through features like topics and subscriptions. RabbitMQ, on the other hand, focuses primarily on the publish/subscribe pattern, simplifying the routing of messages to multiple subscribers.
Message Retention: Azure Service Bus has a built-in feature called "dead-lettering" that allows you to automatically move messages that couldn't be delivered to a separate queue for further analysis. RabbitMQ does not provide this feature out-of-the-box, although it can be implemented using custom code.
Scalability: Azure Service Bus is designed to handle high message throughput and can scale automatically based on the demand. It provides features like partitioning to distribute the load across multiple instances. RabbitMQ, on the other hand, requires manual configuration and management of clusters for scalability.
Administration: Azure Service Bus provides a graphical user interface (GUI) and a RESTful API through the Azure portal for administration and monitoring. RabbitMQ, being an open-source solution, provides a web-based management console and several command-line tools for administration.

In summary, Azure Service Bus is a cloud-based fully managed messaging service with support for various protocols and message patterns, while RabbitMQ is an open-source, on-premises message broker that offers flexibility and customization. The choice between the two depends on factors such as hosting preference, protocol compatibility, and specific messaging requirements.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on RabbitMQ, Azure Service Bus

viradiya

Apr 12, 2020

Needs adviceon

AngularJS

ASP.NET Core

MSSQL

We are going to develop a microservices-based application. It consists of AngularJS, ASP.NET Core, and MSSQL.

We have 3 types of microservices. Emailservice, Filemanagementservice, Filevalidationservice

I am a beginner in microservices. But I have read about RabbitMQ, but come to know that there are Redis and Kafka also in the market. So, I want to know which is best.

933k views933k

Comments

André

Technology Manager at GS1 Portugal - Codipor

Jul 30, 2020

Needs adviceon

.NET Core

Hello dear developers, our company is starting a new project for a new Web App, and we are currently designing the Architecture (we will be using .NET Core). We want to embark on something new, so we are thinking about migrating from a monolithic perspective to a microservices perspective. We wish to containerize those microservices and make them independent from each other. Is it the best way for microservices to communicate with each other via ESB, or is there a new way of doing this? Maybe complementing with an API Gateway? Can you recommend something else different than the two tools I provided?

We want something good for Cost/Benefit; performance should be high too (but not the primary constraint).

Thank you very much in advance :)

461k views461k

Comments

mediafinger

Feb 13, 2019

Reviewon

Kafka

RabbitMQ

The question for which Message Queue to use mentioned "availability, distributed, scalability, and monitoring". I don't think that this excludes many options already. I does not sound like you would take advantage of Kafka's strengths (replayability, based on an even sourcing architecture). You could pick one of the AMQP options.

I would recommend the RabbitMQ message broker, which not only implements the AMQP standard 0.9.1 (it can support 1.x or other protocols as well) but has also several very useful extensions built in. It ticks the boxes you mentioned and on top you will get a very flexible system, that allows you to build the architecture, pick the options and trade-offs that suite your case best.

For more information about RabbitMQ, please have a look at the linked markdown I assembled. The second half explains many configuration options. It also contains links to managed hosting and to libraries (though it is missing Python's - which should be Puka, I assume).

159k views159k

Comments

Detailed Comparison

RabbitMQ	Azure Service Bus
RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.	It is a cloud messaging system for connecting apps and devices across public and private clouds. You can depend on it when you need highly-reliable cloud messaging service between applications and services, even when one or more is offline.
Robust messaging for applications;Easy to use;Runs on all major operating systems;Supports a huge number of developer platforms;Open source and commercially supported	-
Statistics
GitHub Stars 13.2K	GitHub Stars -
GitHub Forks 4.0K	GitHub Forks -
Stacks 21.8K	Stacks 553
Followers 18.9K	Followers 536
Votes 558	Votes 7
Pros & Cons
Pros 235 It's fast and it works with good metrics/monitoring 80 Ease of configuration 60 I like the admin interface 52 Easy to set-up and start with 22 Durable Cons 9 Too complicated cluster/HA config and management 6 Needs Erlang runtime. Need ops good with Erlang runtime 5 Configuration must be done first, not by your code 4 Slow	Pros 4 Easy Integration with .Net 2 Cloud Native 1 Use while high messaging need Cons 1 Skills can only be used in Azure - vendor lock-in 1 Limited features in Basic tier 1 Observability of messages in the queue is lacking 1 Lacking in JMS support

What are some alternatives to RabbitMQ, Azure Service Bus?

Kafka

Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design.

Celery

Celery is an asynchronous task queue/job queue based on distributed message passing. It is focused on real-time operation, but supports scheduling as well.

Amazon SQS

Transmit any volume of data, at any level of throughput, without losing messages or requiring other services to be always available. With SQS, you can offload the administrative burden of operating and scaling a highly available messaging cluster, while paying a low price for only what you use.

NSQ

NSQ is a realtime distributed messaging platform designed to operate at scale, handling billions of messages per day. It promotes distributed and decentralized topologies without single points of failure, enabling fault tolerance and high availability coupled with a reliable message delivery guarantee. See features & guarantees.

ActiveMQ

Apache ActiveMQ is fast, supports many Cross Language Clients and Protocols, comes with easy to use Enterprise Integration Patterns and many advanced features while fully supporting JMS 1.1 and J2EE 1.4. Apache ActiveMQ is released under the Apache 2.0 License.

ZeroMQ

The 0MQ lightweight messaging kernel is a library which extends the standard socket interfaces with features traditionally provided by specialised messaging middleware products. 0MQ sockets provide an abstraction of asynchronous message queues, multiple messaging patterns, message filtering (subscriptions), seamless access to multiple transport protocols and more.

Apache NiFi

An easy to use, powerful, and reliable system to process and distribute data. It supports powerful and scalable directed graphs of data routing, transformation, and system mediation logic.

Gearman

Gearman allows you to do work in parallel, to load balance processing, and to call functions between languages. It can be used in a variety of applications, from high-availability web sites to the transport of database replication events.

Memphis

Highly scalable and effortless data streaming platform. Made to enable developers and data teams to collaborate and build real-time and streaming apps fast.

IronMQ

An easy-to-use highly available message queuing service. Built for distributed cloud applications with critical messaging needs. Provides on-demand message queuing with advanced features and cloud-optimized performance.

Related Comparisons

Azure Service Bus vs RabbitMQ: What are the differences?

Transport Protocol: Azure Service Bus uses the AMQP (Advanced Message Queuing Protocol) 1.0, whereas RabbitMQ uses the AMQP 0.9.1 protocol. This difference in transport protocol affects the compatibility and interoperability with different client libraries and frameworks.
Hosting: Azure Service Bus is a cloud-based messaging service provided by Microsoft Azure, which means it is fully managed and hosted in the cloud. On the other hand, RabbitMQ is an open-source message broker that needs to be installed and managed on-premises or in a cloud environment.
Message Patterns: Azure Service Bus supports publish/subscribe, request/reply, and temporal decoupling of publishers and subscribers through features like topics and subscriptions. RabbitMQ, on the other hand, focuses primarily on the publish/subscribe pattern, simplifying the routing of messages to multiple subscribers.
Message Retention: Azure Service Bus has a built-in feature called "dead-lettering" that allows you to automatically move messages that couldn't be delivered to a separate queue for further analysis. RabbitMQ does not provide this feature out-of-the-box, although it can be implemented using custom code.
Scalability: Azure Service Bus is designed to handle high message throughput and can scale automatically based on the demand. It provides features like partitioning to distribute the load across multiple instances. RabbitMQ, on the other hand, requires manual configuration and management of clusters for scalability.
Administration: Azure Service Bus provides a graphical user interface (GUI) and a RESTful API through the Azure portal for administration and monitoring. RabbitMQ, being an open-source solution, provides a web-based management console and several command-line tools for administration.

Azure Service Bus vs RabbitMQ

Overview