We performed a comparison between PubSub+ Event Broker and VMware RabbitMQ based on real PeerSpot user reviews.
Find out in this report how the two Message Queue (MQ) Software solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."When it comes to granularity, you can literally do anything regarding how the filtering works."
"The way we can replicate information and send it to several subscribers is most valuable. It can be used for any kind of business where you've got multiple users who need information. Any company, such as LinkedIn, with a huge number of subscribers and any business, such as publishing, supermarket, airline, or shipping can use it."
"This solution reduces the latency to access changes in real-time and the effort required to onboard a new subscriber. It also reduces the maintenance of each of those interfaces because now the publisher and subscribers are decoupled. Event Broker handles all the communication and engagement. We can just push one update, then we don't have to know who is consuming it and what's happening to that publication downstream. It's all done by the broker, which is a huge benefit of using Event Broker."
"The event portal and the diversity of deployment options in a hybrid landscape are the most valuable features."
"One of the main reasons for using PubSub+ is that it is a proper event manager that can handle events in a reactive way."
"The valuable feature of PubSub+ Event Broker is the speed of processing, publishing, and consumption."
"As of now, the most valuable aspects are the topic-based subscription and the fanout exchange that we are using."
"The topic hierarchy is pretty flexible. Once you have the subject defined just about anybody who knows Java can come onboard. The APIs are all there."
"I like the high throughput of 20K messages/sec, and that it supports multiple protocols."
"The solution has really cool features to use. Its management console is excellent. You can utilize plugins to view the performance of the whole service on one network."
"We use VMware RabbitMQ to transfer information from one point to another."
"The solution can scale."
"The product's reliability is the most valuable feature."
"The most valuable feature for me is that it is open source. The licensing costs are really low and they are transparent."
"It is easy to use. The addition of more queues and more services can be managed very easily."
"The most valuable feature is asynchronous calls, which are easy to configure."
"A challenge we currently have is Solace's ability to integrate with single sign-on in our Active Directory and other single sign-on tools and platforms that any company would have. It's important for the platforms to work. Typically, they support only LDAP-based connectivity to our SQL Servers."
"We've pointed out some things with the DMR piece, the event mesh, in edge cases where we could see a problem. Something like 99 percent of users wouldn't ever see this problem, but it has to do with if you get multiple bad clients sending data over a WAN, for example. That could then impact other clients."
"For improvements, I would suggest increasing the max payload size to a limit of 100MB or more. The current max payload size is limited to 5MB."
"Some of the feature's gaps with some of the open-source vendors have been closed in a lot of ways. Being more agile and addressing those earlier could be an area for improvement."
"If you create one event in the past, you cannot resend it."
"The product should allow third-party agents to be installed. Currently, it is quite proprietary."
"We have requested to be able to get into the payload to do dynamic topic hierarchy building. A current workaround is using the message's header, where the business data can be put into this header and be used for a dynamic topic lookup. I want to see this in action when there are a couple of hundred cases live. E.g., how does it perform? From an administration perspective, is the ease of use there?"
"It could be cheaper. It could also have easier usage. It is a brilliant product, but it is quite complex to use."
"The fact that a single queue can't be distributed across multiple instances/nodes is a major disadvantage."
"We needed to configure additional plugins. While it was relatively easy to do this on-premises, it became more challenging in the cloud."
"There are some security concerns that have been raised with this product."
"If you're outside IP address range, the clustering no longer has all the features which is problematic."
"I’d like this dashboard to use web sockets, so it would actually be in real time. It would slightly increase debugging, etc."
"The next release should include some of the flexibility and features that Kafka offers."
"Their implementation is quite tricky. It's not that easy to implement RabbitMQ as a cluster."
"When you have complex tasks, RabbitMQ is hard to use."
PubSub+ Event Broker is ranked 6th in Message Queue (MQ) Software with 15 reviews while VMware RabbitMQ is ranked 5th in Message Queue (MQ) Software with 38 reviews. PubSub+ Event Broker is rated 8.6, while VMware RabbitMQ is rated 8.2. The top reviewer of PubSub+ Event Broker writes "Event life cycle management changes the way a designer or architect will design a topic and discover what is available". On the other hand, the top reviewer of VMware RabbitMQ writes "A cloud solution for asynchronous call with easy configuration". PubSub+ Event Broker is most compared with Apache Kafka, IBM MQ, ActiveMQ, Confluent and Amazon EventBridge, whereas VMware RabbitMQ is most compared with IBM MQ, ActiveMQ, Apache Kafka, Anypoint MQ and Amazon MQ. See our PubSub+ Event Broker vs. VMware RabbitMQ report.
See our list of best Message Queue (MQ) Software vendors.
We monitor all Message Queue (MQ) Software reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.