We performed a comparison between PubSub+ Event Broker and TIBCO Rendezvous based on real PeerSpot user reviews.
Find out in this report how the two Message Oriented Middleware (MOM) solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The valuable feature of PubSub+ Event Broker is the speed of processing, publishing, and consumption."
"In my assessment of Solace against other products — as I was responsible for evaluating various products and bringing the right tool into companies in the past — I worked with multiple platforms like RabbitMQ, Confluent, Kafka, and various other tools in the market. But I found the event mesh capability to be a very interesting as well as fulfilling capability, towards what we want to achieve from a digital-integration-strategy point of view... It's distributed, yet it is intelligently connected. It can also span and I can plug and play any number of brokers into the event mesh, so it's a great deal. That's a differentiator."
"We like the seamless flexibility in protocol exchange offering without writing a code."
"When it comes to granularity, you can literally do anything regarding how the filtering works."
"Going from something where we had outages and capacity issues constantly to a system that was able to scale with the massive market data and messaging spikes that happened during the initial stages of the COVID crisis in March, we were able to scale with 40 plus percent growth in our platform over the course of days."
"The most useful features has been the WAN optimization and probably the HybridEdge, which requires some third-party adapters or plugins. The idea that we can position Solace as a protocol-agnostic message transport fabric is key to our company having all manners of asynchronous messaging protocols from MQ, Kafka, JMS, etc. I really like the WAN optimization: Send once over a WAN, then distribute locally as many times as there are subscribers."
"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."
"TIBCO Rendezvous has a strategy to communicate in the network between the DMO of the product. They provide strategy through secure communication. They use the UDP protocol, but It's not a resilient protocol. They put another protocol to create a type of guarantee. It has a high level of communication between the DMO. This is the best capability the solution has."
"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."
"The product should allow third-party agents to be installed. Currently, it is quite proprietary."
"It could be cheaper. It could also have easier usage. It is a brilliant product, but it is quite complex to use."
"If you create one event in the past, you cannot resend it."
"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?"
"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."
"One of the areas of improvement would be if we could tell the story a bit better about what an event mesh does or why an event mesh is foundational to a large enterprise that has a wide diversity of applications that are homegrown and a small number off the shelf."
"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."
"TIBCO Rendezvous is currently restricted in a cloud environment and it would be more useful in a hybrid cloud setup. It does not work correctly in a cloud environment alone. This is something they can improve in the future."
Earn 20 points
PubSub+ Event Broker is ranked 2nd in Message Oriented Middleware (MOM) with 15 reviews while TIBCO Rendezvous is ranked 6th in Message Oriented Middleware (MOM). PubSub+ Event Broker is rated 8.6, while TIBCO Rendezvous is rated 8.0. 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 TIBCO Rendezvous writes "Good communication, stable, and responsive support". PubSub+ Event Broker is most compared with Apache Kafka, IBM MQ, ActiveMQ, VMware Tanzu Data Services and Real-Time Innovations DDS, whereas TIBCO Rendezvous is most compared with TIBCO FTL and IBM MQ. See our PubSub+ Event Broker vs. TIBCO Rendezvous report.
See our list of best Message Oriented Middleware (MOM) vendors.
We monitor all Message Oriented Middleware (MOM) 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.