Try our new research platform with insights from 80,000+ expert users

PubSub+ Platform vs TIBCO Rendezvous 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

PubSub+ Platform
Ranking in Message Oriented Middleware (MOM)
2nd
Average Rating
8.6
Reviews Sentiment
7.1
Number of Reviews
17
Ranking in other categories
Message Queue (MQ) Software (8th), Event Monitoring (12th), Streaming Analytics (11th)
TIBCO Rendezvous
Ranking in Message Oriented Middleware (MOM)
6th
Average Rating
8.0
Number of Reviews
2
Ranking in other categories
Business Activity Monitoring (3rd)
 

Mindshare comparison

As of July 2025, in the Message Oriented Middleware (MOM) category, the mindshare of PubSub+ Platform is 15.5%, down from 17.3% compared to the previous year. The mindshare of TIBCO Rendezvous is 6.8%, up from 3.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Message Oriented Middleware (MOM)
 

Featured Reviews

BhanuChidigam - PeerSpot reviewer
Performs well, high availability, and helpful support
We use approximately four people for the maintenance of the solution. My advice to others is this solution has high throughput and is used for many stock exchanges. For business critical use cases, such as processing financial transactions at a quick speed, I would recommend this solution. I rate PubSub+ Event Broker an eight out of ten.
MP
Good communication, stable, and responsive support
TIBCO Rendezvous has some difficulties to be deployed in a cloud environment. We use it typically in a bare-metal infrastructure. We can use a cluster of the nodes of the other companies. For example, we cannot deploy in the cloud infrastructure, but the companies cannot deploy TIBCO Rendezvous in a cloud environment without issues. It is very easy to start the TIBCO Rendezvous in the DMO infrastructure. The first time we deployed TIBCO Rendezvous, we used it to support individual transaction integration between the distributed and mainframe applications. We spent approximately five days deploying TIBCO Rendezvous in the companies in their application. It's very fast to implement and to use.

Quotes from Members

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

Pros

"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."
"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."
"We've built a lot of products into it and it's been quite easy to feed market data onto the systems and put entitlements and controls around that. That was a big win for us when we were consolidating our platforms down. Trying to have one event bus, one messaging bus, for the whole globe, and consolidate everything over time, has been key for us. We've been able to do that through one API, even if it's across the different languages."
"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."
"When it comes to granularity, you can literally do anything regarding how the filtering works."
"Guaranteed Messaging allows for us to transport messages between on-prem and the cloud without any loss of data."
"The valuable feature of PubSub+ Event Broker is the speed of processing, publishing, and consumption."
"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."
 

Cons

"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 product should allow third-party agents to be installed. Currently, it is quite proprietary."
"The ease of management could be approved. The GUI is very good, but to configure and manage these devices programmatically in the software version is not easy. For example, if I would like to spin up a new software broker, then I could in theory use the API, but it would require a considerable amount of development effort to do so. There should be a tool, or something that Solace supports, that we could use for this, e.g., a platform like Terraform where we could use infrastructure as code to configure our source appliances."
"It could be cheaper. It could also have easier usage. It is a brilliant product, but it is quite complex to use."
"The solution could be improved by enhancing the message pooling size for persistent messages to handle both small and large messages effectively."
"The deployment process is complex."
"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?"
"I would like them to design topic and queue schemas, mapping them to the enterprise data structure."
"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."
 

Pricing and Cost Advice

"Having a free version of the solution was a big, important part of our decision to go with it. This was the big driver for us to evaluate Solace. We started using it as the free version. When we felt comfortable with the free version, that is when we bought the enterprise version."
"The price of PubSub+ Event Broker is reasonable for the capability it offers. However, when compared to others solutions on the market it is expensive."
"There are different tiers where you can choose what would work for you. As a customer, you need to know roughly how many messages a month you will use."
"I would rate the product's pricing a ten out of ten."
"The price of the solution is expensive."
"It could be cheaper. Its licensing is on a yearly basis."
"The pricing and licensing were very transparent and well-communicated by our account manager."
"Having a free version is critical for our technology operations use case. This is primarily because our technology operations team is a cost center in our company. They are not profit drivers and having a free version for installation will probably meet our needs. Even for production, it'll support up to a 100,000 messages per second. I don't think in technology operations that we have that many events and alerts from our detection tools. Even if I have 20 or 30 event detection products out there, they're only going to publish the things which are critical or warnings. I don't think we'll ever reach a 100,000 messages per second."
"There is a license needed to use this solution."
report
Use our free recommendation engine to learn which Message Oriented Middleware (MOM) solutions are best for your needs.
861,390 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
33%
Computer Software Company
11%
Manufacturing Company
8%
Retailer
8%
Financial Services Firm
60%
Computer Software Company
13%
Energy/Utilities Company
4%
University
3%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

What needs improvement with PubSub+ Event Broker?
Regarding improving the PubSub+ Platform, I'm not sure about the pricing aspect, but I heard that it is quite expensive compared to Kafka. That's the only concern I can mention; otherwise, it was a...
What is your primary use case for PubSub+ Event Broker?
My typical use case for the PubSub+ Platform is as an event-driven solution for communication between two components.
What advice do you have for others considering PubSub+ Event Broker?
I have experience working with Kafka, PubSub+ Platform, and IBM MQ, all three of them. We are customers, meaning my company uses Solace. We use it and customize it based on our needs. Based on my e...
Ask a question
Earn 20 points
 

Comparisons

 

Also Known As

PubSub+ Event Broker, PubSub+ Event Portal
Rendezvous
 

Overview

 

Sample Customers

FxPro, TP ICAP, Barclays, Airtel, American Express, Cobalt, Legal & General, LSE Group, Akuna Capital, Azure Information Technology, Brand.net, Canadian Securities Exchange, Core Transport Technologies, Crédit Agricole, Fluent Trade Technologies, Harris Corporation, Korea Exchange, Live E!, Mercuria Energy, Myspace, NYSE Technologies, Pico, RBC Capital Markets, Standard Chartered Bank, Unibet 
Agilent Technologies, Vodafone Hutchison Australia
Find out what your peers are saying about PubSub+ Platform vs. TIBCO Rendezvous and other solutions. Updated: July 2025.
861,390 professionals have used our research since 2012.