1. Home
  2. Message Oriented Middleware
  3. TIBCO Rendezvous Reviews
  4. User Review of TIBCO Rendezvous
TIBCO oldie...
February 15, 2018

TIBCO oldie...

Anonymous | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User

Overall Satisfaction with 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 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.
  • 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 -
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).

Using TIBCO Rendezvous

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