Please share with the community what you think needs improvement with TIBCO ActiveMatrix Service Bus.
What are its weaknesses? What would you like to see changed in a future version?
In terms of the cloud, I don't feel that TIBCO is mature enough. The cloud version was only released two years ago. Sometimes there are issues with the loads. If the load is too high or if you have high traffic, you will experience some issues with the throughput. They need improvements with the cloud version and the handling of the traffic. Initially, we had the professional services with the TIBCO because we are in Africa, but unfortunately, they terminated it because they sold their business in Africa to another service integrator who didn't really understand the product. This service integrator was not as experienced using TIBCO, or maybe just assisting us with the TIBCO issues that we were having. Issues with the support, the fees, and the termination of the professional services are reasons we are looking for other solutions.
The intermediate version that we are using has stability issues. These stability issues should be resolved, but it seems like TIBCO is not focusing on resolving these issues. The resolution timelines are quite high even for high-priority incidents. Its price should be lower. Its licensing cost is considerably high as compared to other ESBs.
When I compare the new version 6.X with the classic 5.X, they are not giving the same kind of look and feel or the ease of use which we are used to. They are improving the DevOps and other new things we have now, but they still have to improve and mature. When someone is planning to move away from their version 5.X to the latest one, they will have both options. Either upgrade to the latest version of TIBCO or go towards some other vendor. That's where they are not giving any competitive advantage or anything with the latest versions. I think they need to improve. They need to really show the consumers what they'll get if they upgrade to the latest version.
Our version does not have cloud capabilities. Containerization is not supported. The is no support for Agile development.
If TIBCO could be able to sort the size of their base image in the Container edition, it would be really marvelous. Right now it's around 299 MB. We'd really want it to reduce to a few MBs. TIBCO needs to improve its monitoring capability to be able to make use of alerts and to be able to have an alert threshold. For example, if there is an API, if it encounters a given number of errors or long response times, it could send an alert to a configured list of users either via email or SMS. The solution needs to have cloud integration. There should be continuous integration and continuous deployment of new features.
One of the areas that this solution could be improved is to provide the vendors with updated information. We don't always know what is going on with the development of the solution. In the next release, there should be improvements made to the API manager. Other platforms are better.
The transparency, complexity, and stability of some products, such as Tibco BC, need to be improved. Migration from BW 5.x to 6.x still has issues. Migration to cloud solutions or products should be made convenient, transparent, and easily understandable. Improvements can be made in the product support area. At times, effective and accurate solutions were not provided.
What do you like most about TIBCO ActiveMatrix Service Bus?
Thanks for sharing your thoughts with the community!
I am looking for few suggestions on key focus elements while evaluating ESBs with consideration to the services that will be accessing Big Data.
Your ideas are much awaited and appreciated.