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

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.0
Number of Reviews
20
Ranking in other categories
Message Queue (MQ) Software (9th), Event Monitoring (11th), Streaming Analytics (15th)
TIBCO Rendezvous
Ranking in Message Oriented Middleware (MOM)
4th
Average Rating
8.0
Number of Reviews
3
Ranking in other categories
Business Activity Monitoring (3rd)
 

Mindshare comparison

As of August 2026, in the Message Oriented Middleware (MOM) category, the mindshare of PubSub+ Platform is 12.8%, down from 16.1% compared to the previous year. The mindshare of TIBCO Rendezvous is 7.4%, up from 7.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Message Oriented Middleware (MOM) Mindshare Distribution
ProductMindshare (%)
PubSub+ Platform12.8%
TIBCO Rendezvous7.4%
Other79.8%
Message Oriented Middleware (MOM)
 

Featured Reviews

Deepankar Bbhowmick - PeerSpot reviewer
Integration Architect at a tech services company with 11-50 employees
Messaging design has become visual and reliable and now supports fast microservice communication
The unique functions I appreciate about PubSub+ Platform are that it allows me to design my solution in a graphical manner, which is not available in many other products, and the design can also be pushed to the actual infrastructure layer, making it quite advantageous. Mesh technology is useful in scenarios where different geographies have to be connected, although such situations are not commonly found. It is beneficial but not a super-used feature of PubSub+ Platform. The event replay function is quite mature in PubSub+ Platform, allowing me to replay messages that are days in the past, which is a good feature. The main benefits PubSub+ Platform provides for the end-user include building a robust and scalable system with very low network latency, which improves the customer experience, whether using mobile phones or applications. This type of messaging framework is extremely important, and Solace is a very good product in that space. Nowadays, most applications are built using microservices technology, with small microservices interchanging messages via PubSub+ Platform. Without it, realizing a scalable system would not be possible; for example, one cannot have Netflix or similar services that require quick data transit and a good user experience, ensuring that data cannot be lost in transit. The analytics part of PubSub+ Platform is quite useful as it can connect with many analytical software tools, mainly for analysis of system logs, such as Splunk, DataDog, or Prometheus. It has the flexibility to connect with any of these and supports OpenTelemetry, which is not available in many other products, making traceability very easy. I can see how a message travels from a source system to the target system, end-to-end, along with what happens to that message along the path, making the analytics quite good.
reviewer2817747 - PeerSpot reviewer
Tibco Consultant at a tech vendor with 10,001+ employees
Messaging has supported complex integrations while DevOps automation improves uptime
TIBCO Rendezvous is a great tool but has some advantages and disadvantages. It runs on TCP and has a specific port on each server. However, the messages are not guaranteed messages. Messages that float on TIBCO Rendezvous are not persistent, which means we can lose the message. That is the disadvantage of TIBCO Rendezvous. If there is a disadvantage with TIBCO Rendezvous, people prefer to use TIBCO EMS because businesses do not want to lose their messages. The best features in Rendezvous require that when we need to install the TIBCO environment, the dependency of Rendezvous itself is required after the Java installation. There is too much dependency of TIBCO Rendezvous for the TIBCO environment to run. On each server, we need TIBCO Rendezvous messaging to communicate with different servers, both within the servers and outside the server. TIBCO Rendezvous is a good messaging service, but there is a feature of losing messages. We cannot guarantee that a message will reach the client because there is no client send receipt and acknowledgment receipt protocol that works in TIBCO Rendezvous. With TIBCO EMS, we have client send and acknowledgment responses. TIBCO Rendezvous is very good to use within the TIBCO servers. If businesses need to use it, they always prefer to use TIBCO EMS outside the servers, as TIBCO EMS is the best. The response time of Rendezvous is good, but I have one disadvantage only for Rendezvous. We can lose the messages over TIBCO Rendezvous. That is not good for businesses. They are not ready to lose messages.

Quotes from Members

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

Pros

"Because we use it as a message broker, it makes information flow very seamless."
"One of the main reasons for using PubSub+ is that it is a proper event manager that can handle events in a reactive way."
"Some valuable features include reconnecting topics, placing queues, and direct connections to MongoDB. The platform provides a dashboard to monitor the status of messages, such as how many have been processed or delivered, which is helpful for tracking performance."
"If we talk about Solace, you see the value-add layer; I can say that Solace is a basic Kafka, but on top of that Kafka layer, they have added their own layer that is really good, as this is where it adds value and why we went for it."
"As of now, the most valuable aspects are the topic-based subscription and the fanout exchange that we are using."
"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."
"It is a product that is more like a switch or router, where you install it, then it keeps on working."
"Guaranteed Messaging allows for us to transport messages between on-prem and the cloud without any loss of data."
"Kubernetes is the platform where we deploy pods containing YAML files, and we deploy Python or Java JAR files and run them without requiring the operating system, allowing us to run applications flawlessly."
"You should read the documentation really well; they have made some improvements over the years during the past 20 years, and it's a hundred times better than what it was back in 1996/1997."
"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."
"TIBCO Rendezvous has about 600 days of time without any problems in the system and the infrastructure we have is very stable to support infrastructure."
 

Cons

"If you create one event in the past, you cannot resend it."
"The solution could be improved by enhancing the message pooling size for persistent messages to handle both small and large messages effectively."
"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."
"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."
"Potential areas for improvement in PubSub+ Platform are its authentication mechanisms, which could be slightly better."
"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."
"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."
"The point-to-point connection issue with the mailbox needs to improve."
"TIBCO Rendezvous is a good messaging service, but there is a feature of losing messages; we cannot guarantee that a message will reach the client because there is no client send receipt and acknowledgment receipt protocol that works in TIBCO Rendezvous."
"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

"It could be cheaper. Its licensing is on a yearly basis."
"The licensing is dependent on the volume that is flowing. If you go for their support services, it will cost some more money, but I think it is worth it, especially if you are just starting your journey."
"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."
"The price of the solution is expensive."
"We have been really happy with the product licensing rates. It has been free for us, up to a 100,000 transactions per second, and all we have to do is pay for support. Making their product available and accessible to us has not been a problem at all."
"We are looking for something that will add value and fit for purpose. Freeware is good if you want to try something quickly without putting in much money. However, as far as our decision is concerned, I don't think it helps. At the end of the day, if we are convinced that a capability is required, we will ask for the funding. Then, when the funding is available, we will go for an enterprise solution only."
"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."
"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."
"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.
909,679 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
17%
Manufacturing Company
11%
Construction Company
7%
Comms Service Provider
6%
Financial Services Firm
48%
Computer Software Company
6%
Manufacturing Company
6%
Comms Service Provider
5%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business6
Midsize Enterprise1
Large Enterprise15
No data available
 

Questions from the Community

What is your experience regarding pricing and costs for PubSub+ Event Broker?
Pricing-wise for PubSub+ Platform, I find it a little expensive, so I would rate it at six.
What needs improvement with PubSub+ Event Broker?
Potential areas for improvement in PubSub+ Platform are its authentication mechanisms, which could be slightly better. While simple authentication using basic methods is easy, moving to more robust...
What is your primary use case for PubSub+ Event Broker?
PubSub+ Platform is primarily used for guaranteed delivery of messages from across systems, for microservice-based development, and for high-speed data consumption purposes. Guaranteed transmission...
What is your experience regarding pricing and costs for TIBCO Rendezvous?
TIBCO has quite high prices as compared to other messaging services. However, the business still relies on TIBCO.
What needs improvement with TIBCO Rendezvous?
TIBCO Rendezvous is a great tool but has some advantages and disadvantages. It runs on TCP and has a specific port on each server. However, the messages are not guaranteed messages. Messages that f...
What is your primary use case for TIBCO Rendezvous?
We are dealing with both TIBCO and Tomcat. Tomcat is the backend server which is used at the back end of TIBCO 5.x. TIBCO is a product-based company that creates products for businesses such as pha...
 

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: August 2026.
909,679 professionals have used our research since 2012.