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.
Pros
Faster broadcast data.
Exchange data across multiple networks.
It works without a central server.
Messages filtered based on specific subject.
Cons
Poor management tool.
TIBCO RV needs a good knowledge on own networks.
Likelihood to Recommend
<div>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.</div><div>
</div>
VU
Verified User
Engineer in Information Technology (10,001+ employees)
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.
Pros
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.
Cons
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.
Likelihood to Recommend
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).
VU
Verified User
Consultant in Information Technology (501-1000 employees)
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).
Pros
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
Cons
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
Likelihood to Recommend
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.
