How to get the business to adapt to change
November 22, 2017

How to get the business to adapt to change

.john omahen | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User

Overall Satisfaction with TIBCO BusinessEvents

It replaces the current legacy fraud operational system. We incorporated a number of producers of real-time events (e.g. web UI claims process and RSA Web Threat Detection). TIBCO BusinessEvents (BE) is the consumer that runs a set of rules against those events to determine the next steps in the claims process.
  • Great event driven engine with a rich event model
  • Provides ability to use Web Studio to generate basic rules that will drive the outcomes
  • Allows for Java implementations of other rule sets
  • Has in-memory caching abilities
  • We had to write our own business rules interface that matched how our previous systems operated. Web Studio has gone through some great changes but in that time we have made a decision to move to Kafka, Kinesis, and Spark for our events streaming solution in AWS.
  • We did not modify our business process flow to take advantage of BE. If you are not truly running an adaptive business process effort, then BE could be overkill.
  • Online training
  • In-person training
  • Self-taught
We had great BE support from TIBCO. Since I had been around BE since the earlier years at TIBCO I put together a local training effort to ensure each of our original developers could build the basic patterns (e.g. from Paul Brown's book on Architecting Complex-Event Processing Solutions with TIBCO).
  • We are able to stay on top of major threats to our claims process
  • We have been able to at least help the business understand what an adaptive business process can do for them
BE has been a great tool. But our company is moving to AWS and not moving current TIBCO solutions to the cloud.
If you are truly event driven and are willing to implement an adaptive business process then BE is great. The challenge is involving the business and ensuring they are in charge of the product release. In our organization, when the business drove the product releases (which included BE applications) then BE was a winner. When developers took over and had no real event-driven background then all the calls were synchronous which is a killer to the event-driven process.