TIBCO Rendezvous

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.

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 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).

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).

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.