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."Guaranteed Messaging allows for us to transport messages between on-prem and the cloud without any loss of data."
"When we went to add another installation in our private cloud, it was easy. We received support from Solace and the install was seamless with no issues."
"One of the main reasons for using PubSub+ is that it is a proper event manager that can handle events in a reactive way."
"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 valuable feature of PubSub+ Event Broker is the speed of processing, publishing, and consumption."
"We like the seamless flexibility in protocol exchange offering without writing a code."
"The most valuable feature of PubSub+ Event Broker is the scaling integration. Prior to using the solution, it was done manually with a file, and it can be done instantly live."
"When it comes to granularity, you can literally do anything regarding how the filtering works."
"The product's reliability is the most valuable feature."
"We have been able to set up a messaging system that facilitates data integration between the software modules that we sell."
"Very sophisticated routing control and priority messaging capabilities"
"The message routing is the most valuable feature. It is effective and flexible."
"Simple and straightforward admin portals: Made it easy for users and worked out excellently for our requirements"
"The most valuable feature for me is that it is open source. The licensing costs are really low and they are transparent."
"The solution can scale."
"The most valuable feature is asynchronous calls, which are easy to configure."
"The section on observability pertains to understanding the functioning of an event crash. Instead of focusing on how the crash occurs, attention is given to the observable aspects, such as a memory pipeline where one person pushes messages and another reads them. However, this pipeline often encounters issues, such as the reader being unavailable, causing the system to become stuck and preventing the messages from moving forward. This can lead to the pipeline being permanently stalled."
"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."
"The deployment process is complex."
"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."
"I would like them to design topic and queue schemas, mapping them to the enterprise data structure."
"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."
"The licensing and the cost are the major pitfalls."
"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?"
"The debugging capabilities and testing flexibilities need to be improved."
"They should improve on the ability to scale your queues in a very simple and elegant way with the same power that they have would be great."
"If you're outside IP address range, the clustering no longer has all the features which is problematic."
"The support feature could benefit from some improvement in terms of accessibility and responsiveness."
"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 IP addresses."
"When you have complex tasks, RabbitMQ is hard to use."
"The fact that a single queue can't be distributed across multiple instances/nodes is a major disadvantage."
"If messages pile up until the space of the memory is full, then basically, the cluster goes down, and someone has to log in through the backend and purge all messages."
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 40 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 "Reliable queueing functionality and versatile tool that can be used with any programming languages ". 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, Apache Kafka, Anypoint MQ, ActiveMQ 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.