IBM Cloud Pak for Integration vs TIBCO BusinessWorks comparison

"The most valuable aspect of the Cloud Pak, in general, is the flexibility that you have to use the product."

"Redirection is a key feature. It helps in managing multiple microservices by centralizing control and access."

"It is a stable solution."

"The most preferable aspect would be the elimination of the command, which was a significant improvement. In the past, it was a challenge, but now we can proceed smoothly with the implementation of our policies and everything is managed through JCP. It's still among the positive aspects, and it's a valuable feature."

"Cloud Pak for Integration is definitely scalable. That is the most important criteria."

"I like TIBCO BusinessWorks because it has a user-friendly GUI for developing solutions."

"Customer support is very efficient."

"The initial setup of TIBCO BusinessWorks was straightforward since we have used the solution in our organization for a long time."

"The most valuable features are the stability and the time to market."

"The most valuable part of the solution is the ease-of-use and ease of deployment."

"The tool's most valuable feature is BusinessConnect. It's an older product but still quite useful, especially for transferring files from one location to another."

"The solution is very scalable. It can handle a lot. We have encryption plus integration servers running on that platform currently."

"BusinessWorks reduces development time, helping developers to focus on business logic."

"The initial setup is not easy."

"Enterprise bots are needed to balance products like Kafka and Confluent."

"The pricing can be improved."

"Its queuing and messaging features need improvement."

"Setting up Cloud Pak for Integration is relatively complex. It's not as easy because it has not yet been fully integrated. You still have some products that are still not containerized, so you still have to run them on a dedicated VM."

"TIBCO BusinessWorks needs to improve its digital IDs and data processing capabilities. It will benefit small and medium businesses."

"This solution's cloud could be improved. I don't know whether it was because we didn't have the internal expertise or if it was the product itself, but since they came later—I think only two or three years into the cloud—after many other iPaaS that had been in the cloud for longer, I feel that maybe they haven't matured in terms of the cloud."

"I would like the solution to be integrated into the cloud."

"I'd like to see a new cloud approach in the next release. They need to work on integrations, stability and management issues on their cloud platform."

"The container-based image is too large and this makes auto-scaling difficult."

"Its price can be improved. For medium enterprises, it is a very expensive tool. In the market, you won't get many resources for this solution. You won't find many developers in the market very easily. The latest version of TIBCO (6.4 or 6.x) is not very stable. It has got many issues. We have raised this with TIBCO, and they are taking a lot of time to come up with a fix, which is making us move away from this product. Some of the performance-tuning aspects are also missing in version 6. They should provide performance-related fixes, which will be helpful for the customers. If you are migrating from the current version to the container-supported version, it is quite expensive. The product has evolved, but it is very pricey. That's one of the challenges. They have provided all the features that are there in other products, but this is a platform upgrade. The platform has completely been changed from 5.x to 6.x, and we can't use the same environment. We can't run both versions on the same server as VM. The development environment is entirely different. In version 5.x, there was a proprietary designer. Now, it has common plug-ins developed on top of Eclipse."

"There are not many plugins available to integrate the databases. We have to write it in Java and integrate it. The developers should have more knowledge. These are the three main aspects that they could improve."

"The technical support's turnaround time is an area where TIBCO needs to consider improvements...Getting support from TIBCO on a particular issue takes a lot of turnaround time."

"The solution's pricing model is very flexible."

"It is an expensive solution."

"I would rate the solution's pricing a three out of ten."

"The license is expensive, and I would rate it one out of ten."

"I think BusinessWorks is more expensive compared to other products. We have the ELA, so at least we have some sort of bargain or discount with that. But for a start-up, it's very expensive compared to other ESBs."

"TIBCO BusinessWorks is a very expensive solution."

"Its price policy has changed quite a lot in the last two years. It was extremely expensive previously. Nowadays, you can buy a license for BusinessWorks for €2000. Looking at what you get in return in terms of support, TIBCO community, and stability, it is fairly reasonable. It is not too expensive."

"I don't have the prices of the products, but I know that TIBCO is not a cheap solution. I think that this solution is more suitable for large companies because I don't think that small- or medium-sized companies would have the money for this solution. WSO2 has the community version for free, so many of the smaller companies can use it. I'm not sure what the prices are for support, though, so I suppose the support for WSO2 is not cheap either."

"It is a bit expensive for medium-sized companies. If you are migrating from the current version to the container-supported version, it is quite expensive. The existing licensing will not work because the product platform itself is different."

"The solution is too expensive. It's one of the most expensive solutions out there, particularly because there are so many open-source competitors on the market. I don't know the exact numbers, however."