EMQ vs RabbitMQ

Overview

RabbitMQ

Stacks21.8K

Followers18.9K

Votes558

GitHub Stars13.2K

Forks4.0K

EMQX

Stacks34

Followers109

Votes6

GitHub Stars15.4K

Forks2.4K

EMQ vs RabbitMQ: What are the differences?

Introduction:

EMQ and RabbitMQ are both popular message-oriented middleware (MOM) systems used for handling distributed systems and data streaming. While they share some similarities, there are key differences that set them apart. Below are six key differences between EMQ and RabbitMQ.

Scalability: EMQ is designed with scalability in mind and can handle a high number of concurrent connections. It supports clustering and scales horizontally by adding more nodes to distribute the load. On the other hand, RabbitMQ lacks this horizontal scalability and struggles with handling large workloads or high message rates.
Protocol Support: EMQ supports various protocols such as MQTT, CoAP, LwM2M, and WebSocket, making it more versatile for IoT applications. RabbitMQ, on the other hand, primarily supports Advanced Message Queuing Protocol (AMQP) and supports fewer protocols overall.
Performance: EMQ is known for its high-performance capabilities and low message latency. It achieves this by utilizing a lightweight message storage engine and efficient message routing algorithms. RabbitMQ, while still performant, may not provide the same level of low latency and throughput as EMQ in highly demanding scenarios.
Ease of Use: RabbitMQ offers a more mature and user-friendly interface, making it easier to set up and configure. It has a wide range of developer tools and libraries available, along with a robust and well-documented API. EMQ, while powerful, has a steeper learning curve and may require more configuration and fine-tuning for optimal performance.
Open Source Community: RabbitMQ has a larger and more active open-source community compared to EMQ. This means that there is a wealth of community-generated resources, plugins, and third-party integrations available for RabbitMQ. EMQ, although open source, may have fewer community contributions and limited available resources.
Use Cases: EMQ is most suitable for scenarios involving IoT messaging, real-time data streaming, and handling massive concurrent connections. Its support for various protocols allows it to cater to diverse IoT device communication needs. RabbitMQ, on the other hand, is great for general-purpose messaging, task queues, and enterprise application integrations, making it more versatile for broader use cases.

In summary, EMQ and RabbitMQ differ in terms of scalability, protocol support, performance, ease of use, open-source community size, and preferred use cases. Understanding these differences will help in making an informed decision when choosing the right message broker for specific project 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, EMQX

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	EMQX
RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.	EMQX is a cloud-native, MQTT-based, IoT messaging platform designed for high reliability and massive scale. Licensed under the Apache Version 2.0, EMQX is 100% compliant with MQTT 5.0 and 3.x standard protocol specifications.
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	Scale to 100 million concurrent MQTT connections with a single EMQX 5.0 cluster./Licensed under the Apache Version 2.0, 100% compliant with MQTT 5.0 and 3.x standard protocol specifications for better scalability, security, and reliability./Move and process millions of MQTT messages per second in a single broker./Guarantee sub-millisecond latency in message delivery with the soft real-time runtime./Achieve high availability and horizontal scalability with a masterless distributed architecture./Easy to deploy on-premises and in public clouds with Kubernetes Operator and Terraform.
Statistics
GitHub Stars 13.2K	GitHub Stars 15.4K
GitHub Forks 4.0K	GitHub Forks 2.4K
Stacks 21.8K	Stacks 34
Followers 18.9K	Followers 109
Votes 558	Votes 6
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 3 QoS 2 2 Clusters 1 Plugins
Integrations
No integrations available	Linux Cassandra Kafka MongoDB

What are some alternatives to RabbitMQ, EMQX?

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

EMQ vs RabbitMQ: What are the differences?

Introduction:

Scalability: EMQ is designed with scalability in mind and can handle a high number of concurrent connections. It supports clustering and scales horizontally by adding more nodes to distribute the load. On the other hand, RabbitMQ lacks this horizontal scalability and struggles with handling large workloads or high message rates.
Protocol Support: EMQ supports various protocols such as MQTT, CoAP, LwM2M, and WebSocket, making it more versatile for IoT applications. RabbitMQ, on the other hand, primarily supports Advanced Message Queuing Protocol (AMQP) and supports fewer protocols overall.
Performance: EMQ is known for its high-performance capabilities and low message latency. It achieves this by utilizing a lightweight message storage engine and efficient message routing algorithms. RabbitMQ, while still performant, may not provide the same level of low latency and throughput as EMQ in highly demanding scenarios.
Ease of Use: RabbitMQ offers a more mature and user-friendly interface, making it easier to set up and configure. It has a wide range of developer tools and libraries available, along with a robust and well-documented API. EMQ, while powerful, has a steeper learning curve and may require more configuration and fine-tuning for optimal performance.
Open Source Community: RabbitMQ has a larger and more active open-source community compared to EMQ. This means that there is a wealth of community-generated resources, plugins, and third-party integrations available for RabbitMQ. EMQ, although open source, may have fewer community contributions and limited available resources.
Use Cases: EMQ is most suitable for scenarios involving IoT messaging, real-time data streaming, and handling massive concurrent connections. Its support for various protocols allows it to cater to diverse IoT device communication needs. RabbitMQ, on the other hand, is great for general-purpose messaging, task queues, and enterprise application integrations, making it more versatile for broader use cases.

EMQ vs RabbitMQ

Overview

EMQ vs RabbitMQ: What are the differences?