#1 most frequent
United States of America
45.2%33 installations of 73
What is TIBCO Rendezvous?
TIBCO's Rendezvous is message oriented middleware. The software uses messages to enable distributed application programs to communicate across a wide variety of hardware platforms and programming languages.
Categories & Use Cases
Who Buys & Uses TIBCO Rendezvous
#2 most frequent
Korea (Republic of)
8.2%6 installations of 73
#3 most frequent
Canada
5.5%4 installations of 73
TIBCO RV: messages for all!!!
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.
Return on Investment
- POSITIVE - Broadcast message, so at the same time different applications can get the needed message.
- POSITIVE - easy configuration.
- NEGATIVE - Number of licenses to buy.
Alternatives Considered
TIBCO Enterprise Message Service
Usability
Other Software Used
Microsoft Teams, Microsoft Visual Studio Code, Eclipse
TIBCO RV review
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
Return on Investment
- 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
Other Software Used
TIBCO Enterprise Message Service
TIBCO oldie...
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.
Return on Investment
- 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.
Alternatives Considered
TIBCO FTL, Mule ESB and IBM MQ
Other Software Used
TIBCO ActiveSpaces, TIBCO Enterprise Message Service, TIBCO iProcess
