Apache Kafka vs TIBCO Rendezvous

• High volume/performance throughput environments
• Low latency projects
• Multiple consumers for the same data, reprocessing, long-lasting information

Read full review

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

Read full review

• Still a bit inmature, some clients have required recoding in the last few versions
• New feaures coming very fast, several upgrades a year may be required
• Not many commercial companies provide support

Read full review

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

Read full review

• Easier deployment and horizontal scalability
• Messaging cost reduction
• Developments require adaptation and some paradigm shift to interoperate with Kafka

Read full review

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

Read full review