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

EMQX vs VMware Tanzu Data Solutions 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

EMQX
Ranking in Message Queue (MQ) Software
9th
Average Rating
8.6
Reviews Sentiment
5.6
Number of Reviews
5
Ranking in other categories
IoT Connectivity (1st)
VMware Tanzu Data Solutions
Ranking in Message Queue (MQ) Software
5th
Average Rating
8.0
Reviews Sentiment
7.0
Number of Reviews
85
Ranking in other categories
Database Development and Management (5th), Relational Databases Tools (14th), Data Warehouse (7th)
 

Mindshare comparison

As of May 2026, in the Message Queue (MQ) Software category, the mindshare of EMQX is 2.8%, up from 1.4% compared to the previous year. The mindshare of VMware Tanzu Data Solutions is 9.3%, up from 4.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Message Queue (MQ) Software Mindshare Distribution
ProductMindshare (%)
VMware Tanzu Data Solutions9.3%
EMQX2.8%
Other87.9%
Message Queue (MQ) Software
 

Featured Reviews

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.
Karthik Shivaram - PeerSpot reviewer
Sr. Manager at STI INFOTECH PVT LTD
Improved multi-cloud data management has simplified operations and supports seamless Kubernetes
From my perspective, the biggest challenge with VMware right now is the pricing. To be very honest, in many cases I find myself recommending alternative solutions instead of VMware. Even if those alternatives come with a bit more complexity, customers are often more willing to accept that than the current VMware pricing model. In the past, VMware used a socket-based licensing model, which was easier for customers to understand and budget for. Now the shift to a core-based licensing model has significantly increased costs for many environments, especially for organizations running modern high-core CPUs. One positive aspect of the new model is that VMware has bundled several components together. For example, earlier when deploying vSphere, customers also had to purchase vCenter separately for management. Now multiple components are packaged into a single SKU, which simplifies some aspects of procurement and deployment. While this consolidation has its benefits, the overall licensing and commercial costs remain very high. Pricing is not the only issue. I believe Broadcom also needs to reconsider its strategy in light of the current market conditions. The approach they are taking may be strategic from a business perspective, but from what I see in the field, it is leading to lost opportunities. Many customers who previously relied on VMware are now actively exploring alternative virtualization platforms. I’m not sure where this direction will ultimately lead, but based on my experience, it is already affecting adoption. Since you’ve been trying to reach me for some time—and we also had a discussion a couple of years ago—I hope this feedback helps Broadcom understand the current sentiment in the market and potentially make adjustments. Another important concern is the way features are bundled. In many cases, customers only need basic virtualization and high availability capabilities. However, the current packaging often includes additional features that they may not need. A good analogy is that if a customer only needs an entry-level car, we shouldn’t be forced to sell them a Rolls-Royce. VMware could benefit from adopting a more modular or à la carte licensing model, where customers can choose only the components they truly require. For example, if a customer only needs core virtualization functionality, they should be able to purchase just that. This would allow partners and solution providers to better align solutions with customer requirements and position VMware more competitively in the market. Another challenge I want to highlight is the pricing model based on U.S. dollars and the way multi-year licensing is handled. In many enterprise and government projects, customers prefer to commit to three-year or five-year licenses and pay the full amount upfront. However, in approximately 20% of the deals I work on, we lose opportunities because VMware only provides dollar-based pricing for the first year. When it comes to the following years, the contract requires renewals annually rather than allowing a fixed multi-year upfront payment. This approach is particularly problematic for government and public sector customers. Many of them are ready and willing to pay for three or five years in advance, but the current VMware model does not support that structure effectively. Because pricing is tied to the U.S. dollar and subject to yearly adjustments, VMware does not lock in pricing for the full term. From a customer’s perspective, this introduces uncertainty and makes procurement more complicated. Ideally, if a price is quoted—for example, $100 per year—it should remain consistent across a multi-year agreement. Customers would be comfortable committing to a five-year term if the price were fixed and predictable. Unfortunately, that flexibility is currently not available across VMware products, whether it is vSphere, VMware Tanzu solutions, or other offerings. For large enterprise environments, one-year commitments are usually not practical. Many enterprise customers prefer longer-term agreements for budgeting and procurement reasons. Even when they are willing to accept the higher cost associated with the core-based licensing model, the lack of a clear multi-year upfront option often becomes a deal-breaker.

Quotes from Members

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

Pros

"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."
"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 is a solid open-source project for making IoT devices connect anywhere in the world."
"RabbitMQ is perfect for publish and subscribe; it does an awesome job at fanout, perfect for CQRS, and messages are delivered to all subscribers with almost no additional latency."
"This product is fantastic."
"The product is not complex; I do not have to create stored procedures, functions, or views."
"Very fast for query processing."
"Append Only tables, data compression and bulk load and extraction using External Tables are very valuable features for us."
"Tanzu Greenplum's most valuable features include the integration of modern data science approaches across an MPP platform."
"The technical support is exquisite."
"This has improved our daily load process reducing the run time at least by three to four hours which made other departments within the organization to look for data from the Enterprise Data Warehouse."
 

Cons

"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."
"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."
"It doesn't have any GUI-based monitoring tools."
"We had multiple issues with stability. The product tends to be highly unstable when under heavy loads."
"Stability-wise, the consumer needs to configure with caution to make sure the queues never overflow; I have experienced data loss in scenarios in which consumer cases were configured incorrectly."
"More stability in terms of query result."
"Some integration with other platforms like design tools, and ETL development tools, that will enable some advanced functionality, like fully down processing, etc."
"The implementation of an upgrade takes a long time."
"The initial setup is somewhat complex and the out-of-the-box configuration requires optimization."
"The initial deployment was a little difficult."
 

Pricing and Cost Advice

Information not available
"Pricing is good compared to other products. It's fine."
"Tanzu Greenplum's pricing is really competitive and gives excellent value for money."
"We are using the open-source version of this solution."
"On a scale of one to five, with five being the most competitive pricing, I would rate this solution as a four."
"This is an open source solution."
"The solution's pricing is cost-effective as it does not involve significant expenses. Licensing is required only for the server, while clients do not need any licensing. Therefore, it proves to be a cost-efficient option."
"The pricing for RabbitMQ is reasonable. It is worth the cost."
"The pricing is okay."
report
Use our free recommendation engine to learn which Message Queue (MQ) Software solutions are best for your needs.
893,244 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Legal Firm
18%
Manufacturing Company
12%
Media Company
10%
Financial Services Firm
9%
Financial Services Firm
17%
Construction Company
9%
Outsourcing Company
8%
Manufacturing Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business30
Midsize Enterprise11
Large Enterprise49
 

Questions from the Community

Ask a question
Earn 20 points
How does IBM MQ compare with VMware RabbitMQ?
IBM MQ has a great reputation behind it, and this solution is very robust with great stability. It is easy to use, simple to configure and integrates well with our enterprise ecosystem and protocol...
What do you like most about VMware RabbitMQ?
RabbitMQ provides access to SDKs for development and the ability to raise and log tickets if we encounter issues. We can integrate RabbitMQ using various languages like Java or Python using the pro...
What needs improvement with VMware RabbitMQ?
Implementing a circuit breaker scenario using RabbitMQ is complicated. This complexity arises because manual intervention is required to manage worker details and handle operations based on worker ...
 

Also Known As

No data available
Greenplum, Pivotal Greenplum, VMware RabbitMQ, VMware Tanzu GemFire, VMware Postgres
 

Overview

 

Sample Customers

Information Not Available
General Electric, Conversant, China CITIC Bank, Aridhia, Purdue University
Find out what your peers are saying about EMQX vs. VMware Tanzu Data Solutions and other solutions. Updated: May 2026.
893,244 professionals have used our research since 2012.