Enterprises are surrounded by hundreds of thousands of events that occur continuously. Hidden amongst them can be stalled business processes, opportunities for value creation, potential fraud, dissatisfied customers, failing equipment, and more. TIBCO BusinessEvents® proactively identifies these critical events, responds intelligently in real-time to navigate the fast-moving business environments and optimize outcomes. Decision-making in businesses requires a comprehensive…
N/A
TIBCO Rendezvous
Score 6.3 out of 10
N/A
TIBCO's Rendezvous is message oriented middleware.
TIBCO BusinessEvents is part of the CEP (Complex Event Processing) family, this means that it fits perfectly in all those scenarios where a correlation between incoming events is required. Where a stateful process is necessary. It does not fit well for a kind of Process Orchestrator scope, where simple events are coming in, and there is a well-defined behavior the system, would have on incoming request, and no particular reason to use a rule engine and its complexity. Anyway, there are particular cases where BusinessEvents would be a good actor in orchestrating a portion of CEP solutions activities
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).
It allows us to build rule-based model-driven application, to collect, filter, analyze, correlate various business events in our real-time event flow
It makes various business applications/components easy to integrate (loosely decoupled but chained via the events flow) together
Its distributed rule engine and embedded in-memory data grid (ActiveSpace) gives us a lot of flexibility and room to play with a large amount of rules and data with high performance
Better integration with R versions and better debug for R-scripts in Spotfire. There are inconsistencies in syntactic expressions accepted by R-studio and not accepted in Spotfire. Accelerating the debug would be awesome. Having a command like View (data frame) that directly output in the dashboard would be a great accelerator.
Attending an official TIBCO classroom training, where you can have an active participation with an expert teacher, you can find the answers to all yours needs. In any case, if you are not satisfied on your requests, the teacher takes the time to find the best solution.
I had the opportunity to attend one and I could learn all features I needed for my business: now I can say TIBCO Rendezvous is very usable.
I never needed support for TIBCO Rendezvous. I always used it without any issue and until now I don't remember some situations where it interrupted its 24/7 uptime.
I was not part of evaluation of the products in this space in my organization. But I feel BE is better in terms of RIO if compared with some commercial products from Orcle, IBM and SAP. I strongly feel difficulty in using cloud native features is one big shortcoming in current product offering. This will tend customer like us to explore options that are well suited with ur cloud first vision.
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.
