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?
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.
In the configuration, where we need to customize, it takes more time that we expect it to, ideally. We have found workarounds for some of the issues, and we have given feedback on these things directly to TIBCO. The integration can be more user-friendly.