No more typing reviews! Try our Samantha, our new voice AI agent.

CloudAMQP vs EMQX comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

CloudAMQP
Ranking in Message Queue (MQ) Software
10th
Average Rating
9.4
Number of Reviews
3
Ranking in other categories
No ranking in other categories
EMQX
Ranking in Message Queue (MQ) Software
4th
Average Rating
8.8
Reviews Sentiment
5.7
Number of Reviews
10
Ranking in other categories
IoT Connectivity (1st)
 

Featured Reviews

HemantKumar7 - PeerSpot reviewer
Senior Site Reliability Engineer at a tech vendor with 501-1,000 employees
Reliable queues have handled heavy microservice traffic and prevent data loss in daily operations
The best features CloudAMQP offers include its ability to handle load efficiently. Without it, if there is a lack of requests coming from multiple consumers, it stores the data in the queue, and the lag will clear after consumption from the consumer side, ensuring no messages drop from CloudAMQP. Additionally, it can run tasks in the background so that it does not block any user requests. CloudAMQP is able to handle the load, and if I want to scale, I can scale the RabbitMQ nodes without any downtime. CloudAMQP has impacted our organization positively because it can handle a huge amount of data. I can have multiple RabbitMQ queues inside CloudAMQP and, as per my plan, purchase multiple queues that offer different capabilities. For example, the Tough Tiger plan allows sending a maximum of ten million messages per month with simultaneous connections of one hundred connections per queue, ensuring no traffic loss. For heavy environments, I can opt for Big Bunny queues, where I can handle one lakh messages per second if there is a huge amount of traffic. Additionally, I have a dedicated RabbitMQ broker as per my requirement, and according to my needs in CloudAMQP, there are different queue plans which I can select accordingly.
AP
Senior Software Engineer
Connected millions of iot devices and manage real time pub sub control and flexible access rules
When going with the open-source EMQX version, there are limitations provided. For example, the webhooks use case cannot be scaled to as large a scale compared to the enterprise edition of EMQX. The open-source version helps a great deal with work in the company. The way this resource helps nurture the IoT device paradigm is greatly helpful for developers working newly on this system because the onboarding part of EMQX is very easy and developer-friendly. Someone who wants to dive into it can easily implement and make the system robust based on the technologies it provides. EMQX provides API connections for applications. HTTP calls can be made to EMQX to get updates from the client. Those connections should be made asynchronously. The webhook part handles this well, but when it comes to the API part, when the load and payload of the MQTT topics and messages are very heavy, sometimes unknown errors occur, and logs and errors must be found. When a specific log session is created for that client, the readability of those logs is not good. The platform itself does not need improvement, but when it comes to developer-friendly implementations of EMQX, there are some pain points that need attention. The visibility of logs, error logs, and information logs inside the built-in monitoring needs work because developers, when they implement code or any kind of specific tools, need proper control over the system. Without that control, there is no point in implementing anything at all. The monitoring part needs work. When it comes to the flow chart of how different clients are connected with different devices, there is a feature inside EMQX called Flow. When that Flow is in place, clients (devices) should be controllable from that Flow itself. These are the most important improvements that need to be addressed.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"CloudAMQP has positively impacted my organization as I have built an automation for scaling, which has helped the organization benefit from workload distribution and faster processes."
"After using CloudAMQP, our efficiency has increased, and the data which is transferring from the fuel station has become easier and faster to communicate with our front-end application."
"Since using CloudAMQP, my organization has seen a very significant return on investment because there is no data loss, and I can recover the system timely."
"The best features EMQX offers are that it is highly scalable and cheaper than other brokers, plus we can use our own back-end services integrated to it for authentication and authorization."
"EMQX helped me complete my project perfectly because when I compared it to other platforms, EMQX truly fits my needs and my project, allowing me to explain my output more clearly to my lecturer, and ultimately I received a good grade, so it has been very helpful."
"The best features EMQX offers in my experience are that it can send messages for a large number of customers with a very high message-per-second rate while consuming low resources."
"The outcomes from using EMQX are very cost-saving for us because we previously used the MQTT Mosquitto broker, and when I compare Mosquitto with EMQX, EMQX is far better than Mosquitto and other protocols."
"EMQX remains live and matured, allowing us to scale it, and we continue using EMQX without requiring to switch to any other offerings as it still works best and is resilient."
"EMQX will boost your product sampling rate and transmission so that you can achieve a large amount of data without any loss while transmitting through the internet."
"EMQX has positively impacted my organization in many ways, particularly by making our main agenda of getting stock details and connecting users to our real-time protocol much easier."
"EMQX is a solid open-source project for making IoT devices connect anywhere in the world."
 

Cons

"CloudAMQP can be improved in a few ways, such as lowering the pricing at scale and keeping the pricing structure simpler."
"CloudAMQP can be improved, as sometimes while upgrading, for instance, if I am running a Big Bunny cluster and want to upgrade to Happy Hour, there is a lag or slowness while upgrading from one queue to another."
"CloudAMQP can be improved as the pricing is a bit high, and if that could be reduced, it would be a great tool."
"I think EMQX can be improved by providing a uniform UI and login feature that we can use in the dashboard."
"On EMQX improvement side, I saw certain frameworks such as NanoMQTT and others claiming to be much more performant than EMQX, so maybe the newer version of EMQX can look into those aspects for potential improvements, but I do not have insight on the latest version of EMQX to know whether it has already addressed this or not."
"To improve EMQX, I think it should reduce costs, save time when sending messages, and improve reliability."
"If you want to improve further, the SSL certificate and TLS certificate have overhead in serverless EMQX."
"EMQX is a good MQTT broker but the historian is simple."
"The visibility of logs, error logs, and information logs inside the built-in monitoring needs work because developers, when they implement code or any kind of specific tools, need proper control over the system."
report
Use our free recommendation engine to learn which Message Queue (MQ) Software solutions are best for your needs.
902,988 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Construction Company
53%
Outsourcing Company
8%
Comms Service Provider
8%
Transportation Company
5%
Media Company
20%
Legal Firm
15%
Manufacturing Company
11%
Outsourcing Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
No data available
 

Questions from the Community

What needs improvement with CloudAMQP?
CloudAMQP can be improved, as sometimes while upgrading, for instance, if I am running a Big Bunny cluster and want to upgrade to Happy Hour, there is a lag or slowness while upgrading from one que...
What is your primary use case for CloudAMQP?
Our main use case for CloudAMQP is that we are using it for RabbitMQ operations as a message broker, with CloudAMQP managing RabbitMQ. Apart from that, we use it for microservice communication. In ...
What advice do you have for others considering CloudAMQP?
My advice for others looking into using CloudAMQP is that if you are choosing any message broker, you can go directly to CloudAMQP. However, before making a choice, at least check their plans accor...
What is your experience regarding pricing and costs for EMQX?
My experience with EMQX regarding pricing, setup cost, and licensing shows that it is affordable.
What needs improvement with EMQX?
I think EMQX can be improved, but to be honest, I don't have anything I'd like to see added or changed. In terms of needed improvements, I don't have anything else to add, even small ones or nice-t...
What is your primary use case for EMQX?
My main use case for EMQX is a stable and scalable IoT message queue. I use EMQX in one of my projects specifically with ESP32 and Argon and Boron embedded chips, and I program them to send and rec...
 

Comparisons

No data available
 

Overview

Find out what your peers are saying about IBM, Apache, Amazon Web Services (AWS) and others in Message Queue (MQ) Software. Updated: June 2026.
902,988 professionals have used our research since 2012.