BE isn't really worth it
November 14, 2017

BE isn't really worth it

Anonymous | TrustRadius Reviewer
Score 2 out of 10
Vetted Review
Verified User

Overall Satisfaction with TIBCO BusinessEvents

Tibco BusinessEvents is being used by several groups across the company in non-legacy projects. It was supposed to be the business rules engine that would drive the event-driven, real time capabilities the company wanted. The in-memory rules engine was supposed to enable instant decision making over the life of the product.
  • The rules engine works well for simple rule sets in smaller batches
  • TIBCO consultants are usually very good with the product
  • The product does not scale well as a central manager of rules.
  • It can be difficult to deploy and scale without extensive knowledge of a lot of inner workings of the product, which is not widely available.
  • It is a very heavyweight product, requiring lots of resources with little visibility as to how resources are being utilized.
  • The BE language resembles Java, but is just different enough to have a learning curve and cause issues if one is unfamiliar with it. Plus it is not nearly as flexible as Java.
  • Self-taught
The online resources for training are very poor, almost requiring you pay for training. Most learning was done peer to peer as in-person training was prohibitively expensive for an already expensive product.
  • The company has spent years and many many man/woman hours working with BE, and will likely be retiring it sooner rather than later.
  • Large amounts were spent on this supposedly next-generation software suite that will be replaced by a much simpler, more open stack.
  • The choice of BE has likely delayed the business objectives it was originally supposed to enable.
These tools are all far better than BE in terms of flexibility and ability to scale with the right architecture and best practices. The wealth of resources available for open source and widely used technologies means that onboarding is so much easier than with any of the TIBCO stack. Deployment of applications is far simpler, and with that comes testing and debugging benefits.
It is very poorly suited to run a central rules engine for large numbers of transactions. Perhaps as an input-output rules engine it might be ok, but as far as managing those events itself it does a poor, overly complex job.