TIBCO BusinessEvents vs. TIBCO Messaging

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

Incentivized

If you need a robust, extensible, reliable Enterprise Service Bus, with "Enterprise" being the key word here, TIBCO [Enterprise Message Service] will be able to fulfill every expectation. As proof of concept, or ad-hoc implementations, it might not be as well suited due to the infrastructure required.

Incentivized

• 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

Incentivized

• Tibco EMS performs very well, and it meets our stringent performance requirements for corporate messaging backbone.
• Tibco EMS scales well, and this is another of our stringent requirements.
• Tibco provides good support for the EMS product, and continues to improve it. This is important as we don't want to use something that does not keep up with the changes in the technology landscape.

Incentivized

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

Incentivized

• In terms of TIBCO Messaging, it would nice to have a more out-of-the-box way of linking its objects (queues, topics) directly to those of other popular solutions like MQ or Kafka.
• Not being able to filter (that is, using selectors) through patterns/subtexts on the message body is missed on occasions.
• Given the current trends and state-of-art, lift & shift of on-premise EMS clusters to cloud architectures should be more directly attainable.

Incentivized

EMS is a solid system and I see no reason to abandon it, in fact I am eager to see what the next versions will offer and future road maps. Knowing we have support to help us in case of problems is invaluable, both in case of critical issues and to improve overall performance.

Incentivized

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.

Incentivized

We also use other messaging products: IBM MQ, especially for integration with other systems (server2server), which has been an industry standard for a long time, and Apache Kafka for cloud-native applications. EMS is a worse option compared to them, but it is still acceptable.

Incentivized

• Positive : Real-time event stream processing helps handle transactions very efficiently.
• Negative : Earlier versions of BE (5.0 & 5.1) had major issues in data handling in cache that impacted the data integrity of the application.
• Positive : Decision Tables are a huge plus in TIBCO BE.

Incentivized

• Improved developer productivity as TIBCO Enterprise Message Service requires minimal coding
• Quicker time to market as the configuration / onboarding can be automated with this tool
• Ability to onboard more clients/consumers as the tool can handle large volumes seamless
• Improved visibility on the end to end process as the product provides monitoring by using JMS header information