TrustRadius
TIBCO's Rendezvous is message oriented middleware.https://dudodiprj2sv7.cloudfront.net/product-logos/YX/1V/5RJKHRLB8ICC.pngTIBCO oldie...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.,7,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.,TIBCO FTL, Mule ESB and IBM MQ,TIBCO ActiveSpaces, TIBCO Enterprise Message Service, TIBCO iProcess,,2,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.,TIBCO RV reviewWe 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,6,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 Enterprise Message Service,TIBCO Enterprise Message Service
Unspecified
TIBCO Rendezvous
7 Ratings
Score 7.0 out of 101
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow'>trScore algorithm: Learn more.</a>TRScore

TIBCO Rendezvous Reviews

TIBCO Rendezvous
7 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow'>trScore algorithm: Learn more.</a>
Score 7.0 out of 101
Show Filters 
Hide Filters 
Filter 7 vetted TIBCO Rendezvous reviews and ratings
Clear all filters
Overall Rating
Reviewer's Company Size
Last Updated
By Topic
Industry
Department
Experience
Job Type
Role
Reviews (1-2 of 2)
  Vendors can't alter or remove reviews. Here's why.
No photo available
February 15, 2018

TIBCO Rendezvous Review: "TIBCO oldie..."

Score 7 out of 10
Vetted Review
Verified User
Review Source
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).
Read this authenticated review
Mahendra Gutlapalli profile photo
July 27, 2016

TIBCO Rendezvous: "TIBCO RV review"

Score 6 out of 10
Vetted Review
Verified User
Review Source
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.
Read Mahendra Gutlapalli's full review

TIBCO Rendezvous Scorecard Summary

About TIBCO Rendezvous

TIBCO's Rendezvous is message oriented middleware.

TIBCO Rendezvous Technical Details

Operating Systems: Unspecified
Mobile Application:No