Skip to main content
TIBCO Rendezvous

TIBCO Rendezvous


What is TIBCO Rendezvous?

TIBCO's Rendezvous is message oriented middleware.

Read more
Recent Reviews

TIBCO oldie...

7 out of 10
February 15, 2018
TIBCO Rendezvous is TIBCO's version of ESB. Rendezvous was TIBCO's innovation by its founder Vivek Ranadivé. TIBCO Rendezvous is a …
Continue reading
Read all reviews


Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards

Return to navigation


View all pricing

What is TIBCO Rendezvous?

TIBCO's Rendezvous is message oriented middleware.

Entry-level set up fee?

  • No setup fee


  • Free Trial
  • Free/Freemium Version
  • Premium Consulting / Integration Services

Would you like us to let the vendor know that you want pricing?

2 people also want pricing

Alternatives Pricing

What is TIBCO Messaging?

TIBCO offers high-performance messaging technology, and gives customers flexibility and unique choice between Commercial and Open-source messaging solutions. TIBCO Messaging is a comprehensive messaging portfolio available to meet a wide variety of use cases and deployment models.

What is AWS IoT Core?

AWS IoT Core is a managed cloud service that lets connected devices interact with cloud applications and other devices. It includes the Device Gateway and the Message Broker, which connect and process messages between IoT devices and the cloud. AWS IoT Core connects AWS and Amazon services like…

Return to navigation

Product Demos

Tibco BW Training video | Tibco Business Events (BE) online course demo

Return to navigation

Product Details

What is TIBCO Rendezvous?

TIBCO Rendezvous Technical Details

Operating SystemsUnspecified
Mobile ApplicationNo
Return to navigation


View all alternatives
Return to navigation

Reviews and Ratings


Attribute Ratings


(1-3 of 3)
Companies can't remove reviews or game the system. Here's why
Score 9 out of 10
Vetted Review
Verified User
TIBCO Rendezvous is a messaging software used in my department to provide a way to exchange data between applications. We mostly use it in our business to have robust communication across several programming languages and hardware systems. When something happens during execution of one application and you would like to inform, in real time, other applications not necessarily in the same environment, it could be good way to use TIBCO Rendezvous.
  • Faster broadcast data.
  • Exchange data across multiple networks.
  • It works without a central server.
  • Messages filtered based on specific subject.
  • Poor management tool.
  • TIBCO RV needs a good knowledge on own networks.
I would recommend TIBCO Rendezvous to a colleague for several reasons. One of most important could be to use it on different operating systems (i.e. Windows, Linux) and be able to create real-time communications. Another reason could be the easy message addressing: only those who subscribe to specific subject receive the messages.

  • POSITIVE - Broadcast message, so at the same time different applications can get the needed message.
  • POSITIVE - easy configuration.
  • NEGATIVE - Number of licenses to buy.
TIBCO EMS could be preferred to TIBCO RV for more reliable communication, because EMS guarantees data should not lost during network transmission. The plus point for EMS is that it's based upon JMS specification, so the integration with Java is very appreciated by programmers. EMS does not need to be installed on all clients: it is a very important consideration to keep in mind.
Attending an official TIBCO classroom training, where you can have an active participation with an expert teacher, you can find the answers to all yours needs. In any case, if you are not satisfied on your requests, the teacher takes the time to find the best solution.
I had the opportunity to attend one and I could learn all features I needed for my business: now I can say TIBCO Rendezvous is very usable.
I never needed support for TIBCO Rendezvous. I always used it without any issue and until now I don't remember some situations where it interrupted its 24/7 uptime.
February 15, 2018

TIBCO oldie...

Score 7 out of 10
Vetted Review
Verified User
TIBCO Rendezvous is TIBCO's version of ESB. Rendezvous was TIBCO's innovation by its founder Vivek Ranadivé. TIBCO Rendezvous is a messaging software used in message-oriented middleware. This is mostly used in banking applications for the ticker application and broadcast data in a reliable and faster manner.

Rendezvous is also used in EAI (Enterprise Application Integration) layer for integrating various applications. All the TIBCO Products communicate with each other via the TIBCO Rendezvous. Recently TIBCO has upgraded the Rendezvous to TIBCO FTL. Which is hailed to be faster than Rendezvous.
  • Tibco Rendezvous is used across multiple networks, to reliably transmit data between vast geography. Banks and Stock exchanges across the world communicate with each other using TIBCO Rendezvous.
  • TIBCO Rendezvous is faster and works well between the TIBCO applications. The default mode of communications between the TIBCO products is TIBCO Rendezvous. For example, TIBCO products like TIBCO BusinessWorks and TIBCO Administrator communicate with each other via TIBCO Hawk to monitor the health of all the engines and applications hosted by TIBCO products.
  • Rendezvous is the only mode of communication between the TIBCO suite of products. Although this is slowly getting replaced by TIBCO FTL, the newer generation of the TIBCO Rendezvous.
  • Rendezvous does not require a central server like Java JMS. Rendezvous uses Rendezvous daemon process running in each application to communicate with each other.
  • TIBCO Rendezvous is not recognized very well by other software vendors as much as Java "JMS" is recognized. Hence they are no supported out-of-box by all the software vendors.
  • Although Tibco Rendezvous does not require a central server to host all the communication, they need Tibco Rendezvous daemon process running in the application to be able to send and receive a Rendezvous message. Which means all the applications need a software license to communicate over the Tibco Rendezvous.
  • Comparing to Java JMS which an open source product, TIBCO Rendezvous needs a software license for communicating with each other.
TIBCO Rendezvous is a fast and reliable mode of communication, although they are already outdated by TIBCO FTL, which is even more faster and reliable than it's predecessor. They are more suitable for communication between the TIBCO products as all the TIBCO suite of products support the TIBCO Rendezvous. They are more widely used by banks and stock ticker applications to broadcast the ticker information.

Most of the applications support Java JMS mode easily and out of the box than the TIBCO Rendezvous. Hence the TIBCO software themselves have their own version of the JMS server called Tibco EMS ( Tibco Enterprise messaging service).
  • All a non-TIBCO based applications need to use the TIBCO Rendezvous APIs and reprogrammed to communicate with other application using the Tibco Rendezvous.
  • All applications and enterprises need to have an enterprise license to communicate with each other.
  • TIBCO offers their Rendezvous APIs in various programming languages. Hence any application can use these APIs to start using the Tibco Rendezvous. Although most application prefers not to as TIBCO Rendezvous is TIBCO 's closely guarded recipe.
Messaging is a very old concept offered by many software vendors, Although Tibco Rendezvous is very well recognized non-open source solution.In my opinion Tibco JMS is mostly used in all the applications than the IBM MQ and mule software -
I consult for the telecommunications industry. I am a senior integration consultant. I primarily work on complex integration scenarios, which needs an expert's view to provide solutions. I am also involved in reviewing new TIBCO products that are suitable for our organization. As it is TIBCO Rendezvous is not the primary mode of communication in our company. We use TIBCO EMS ( TIBCO's version of the java JMS) as the primary mode of communication.
My client does not own a license for TIBCO Rendezvous. But since this is the messaging product used by default by the TIBCO products, we are using without realizing that Rendezvous is used behind the scenes.

This means, most of the TIBCO products seamlessly use Rendezvous to communicate with each other and does not need any special skills to use them. But if we want to use custom monitoring using custom tools, then this requires knowledge of the TIBCO Rendezvous APIs and TIBCO Hawk APIs.
  • My organization does not have a license for using TIBCO Rendezvous. It is used for monitoring TIBCO products as the TIBCO Hawk uses TIBCO Rendezvous as the primary mode of communication.
Not likely to renew or buy the license as they are using the TIBCO EMS as the primary mode of communication.
July 27, 2016

TIBCO RV review

Mahendra Gutlapalli | TrustRadius Reviewer
Score 6 out of 10
Vetted Review
Verified User
We used TIBCO RV for broadcasting the stocks information to all of our users. We used TIBCO RV in only finance department not in whole organization. As TIBCO RV doesn't support centralized administration like EMS, we can't effectively use this protocol for synchronous communication. Even though it supports certified delivery by configuring Ledger file, it doesn't support to manage the services in run time without changing the configuration in physical code (where EMS supports this).
  • TIBCO RV supports faster delivery to broadcast any messages
  • This is a best protocol to be used when we wanted to do Asynchronous communications
  • RV supports multiple subscribers with a simple configuration
  • RV doesn't support centralized administration to manage the delivery of synchronous messages in run time without changing its configuration which was done in code base
For Asynchronous communications, RV supports well (like broadcasting a common messages to multiple subscribers, Ex:- sending promotional text messages to all customers who opted, sending stocks information to all subscribers at a time whoever opted to get that information). RV is the best protocol for faster delivery.
  • Positive - RV supports faster delivery of messages to multiple subscribers (asynchronous communications)
  • Negative - RV doesn't support centralized administration and guarantee delivery is more accurate like EMS Persistent delivery mode
TIBCO EMS provides centralized server administration to manger the delivery of services in run time
Return to navigation