InRule vs. TIBCO BusinessEvents

With InRule, we are expecting to be able to move business logic out of the developer domain and back into the business domain. Business logic is currently captured in UI (data validation) and middleware layers. These are areas in any application where leveraging InRule's capabilities allow for changes in business logic to be made with little or no IT involvement.

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

• It is easy to tweak business rule parameters.
• Create new logic with low barriers.

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

• Needs more debugging capabilities.

• 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

InRule's Support Portal provides a "one stop shop" for submitting support questions, accessing training information, managing licenses, and getting updates on InRule's roadmap.

InRule offers a more organized software design, a well-structured framework in design, and is easier for new users to start contributing given documentation. Drools is spreadsheet-based and lacking the capability to do really advanced pseudo-programming.

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

• It is always reliable and efficient.
• Has won customers over.

• 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