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

PubSub+ Platform vs TIBCO Rendezvous comparison

Why PeerSpot?
 

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
6.9
Number of Reviews
20
Ranking in other categories
Message Queue (MQ) Software (10th), Event Monitoring (13th), Streaming Analytics (14th)
TIBCO Rendezvous
Ranking in Message Oriented Middleware (MOM)
5th
Average Rating
8.0
Number of Reviews
3
Ranking in other categories
Business Activity Monitoring (3rd)
 

Mindshare comparison

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

Featured Reviews

Parth Mehta - PeerSpot reviewer
Senior Software Engineer at Luxoft
Event platform has transformed real-time trading data processing and accelerates client onboarding
There is one important thing about how Solace Platform can be improved, and the pain points are part of that. In my seven months of experience, I understand that it should have a better Standard Edition. It has two editions, Standard and Enterprise, and in production they should offer better free services in the Standard Edition at least, so it can help smaller organizations onboard and then move to the Enterprise Edition. I expect them to increase the availability of free editions and more services, so they can get better coverage from different clients, starting from smaller ones. Compared to Kafka, message replay was not available, but they are going to announce it very soon with a better approach for replaying failure cases, which Kafka supports very well. They have this issue right now. Solace Platform is generally evolving day to day, from a single broker to event mesh, which I mentioned, but it still has a limitation that has to be improved. I also expect more insightful observability integrations, such as OpenTelemetry-enabled distributed tracing. I can see they are working on this, but it does not look better right now, and they need to work more in that area. They should also have their own dedicated portal where I can configure everything and monitor everything per my customization. That is what I expect. There are other areas Solace Platform should focus on next. In seven months, I would say it has a lot to offer us, but I have a lot of Kafka experience from before I moved over in the last seven months. I think they need to improve pricing transparency, because their pricing is not publicly available. They should clarify their pricing. They also have the problem of being a single vendor commercial platform, which should not be the case. They should have more long-term event storage and retention capability, which I found to be the biggest gap since we are leveraging a real-time distribution broker. It is not durable right now compared to Kafka, which has indefinite event processing commit logs. It does not have that much compared to its rival Kafka. As I mentioned, they should support more of an open-source ecosystem instead of being tied to their own localized products, which Kafka does very well, so they can gain more popularity. In stream processing, it also lacks a native, first-class stream processing layer equivalent to Kafka Streams. They are not strong in stream analytics, so they have to improve in that area as well. Beyond what we already discussed, Solace Platform needs good long-term event support, since if something fails, it needs better long-term availability for replay. I would also request that they improve their version release timeline. They have to fix some smaller issues that we already raised from our side, such as not having indefinite commit logs or replay of failed events. That is why I introduced Kafka, where I can put all of this, and they should support more here. They should also support more AI offerings. I can see they provide Google ADK support in development and LangGraph, but they should support Claude or other more efficient LLMs. As I mentioned, they have a single vendor commercial platform, and the vendor lock-in perception has to be removed compared to their open-source rival Kafka. This is what I can see. Anyway, they are maturing, so I would say they can definitely improve day to day.
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

"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."
"As of now, the most valuable aspects are the topic-based subscription and the fanout exchange that we are using."
"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."
"The best features of PubSub+ Platform include being highly scalable, allowing us to handle billions and billions of events, and configuring and managing PubSub+ Platform is straightforward and simple while being highly reliable."
"When it comes to granularity, you can literally do anything regarding how the filtering works."
"The event portal and the diversity of deployment options in a hybrid landscape are the most valuable features."
"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."
"Solace Platform is particularly engineered for ultra-low latency and high-throughput data processing with inbuilt high availability and disaster recovery, which is quite a bit better in our use case compared to Kafka."
"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."
"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."
"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."
"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."
 

Cons

"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?"
"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."
"We have struggled in a sort of perpetual PoC mode internally."
"Additional in-line information about certain things on PubSub+ Platform could be more beneficial for new users who are just starting to use this technology."
"If you create one event in the past, you cannot resend it."
"I heard that it is quite expensive compared to Kafka."
"The point-to-point connection issue with the mailbox needs to improve."
"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."
"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."
 

Pricing and Cost Advice

"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."
"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 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."
"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."
"The price of the solution is expensive."
"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."
"I would rate the product's pricing a ten out of ten."
"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."
"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.
922,921 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
13%
Manufacturing Company
11%
Outsourcing Company
10%
Construction Company
8%
Financial Services Firm
46%
Computer Software Company
7%
Construction Company
6%
Manufacturing Company
6%
 

Company Size

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

Questions from the Community

What is your experience regarding pricing and costs for PubSub+ Event Broker?
The pricing and setup cost of PubSub+ Platform is very seamless and reliable for medium and large-scale enterprises. For small-sized enterprises, it may be a higher cost, or they may be looking for...
What needs improvement with PubSub+ Event Broker?
PubSub+ Platform could improve by simplifying some advanced configurations and providing better visualization for event flow. Some advanced configurations in PubSub+ Platform could be made simpler ...
What is your primary use case for PubSub+ Event Broker?
PubSub+ Platform's main use case in our company is real-time data streaming using applications and API integrations. We are working on an IoT-based application, and our company handles most of ...
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: November 2026.
922,921 professionals have used our research since 2012.