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."

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

"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."

"It is a stable solution."

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

"We use the solution to develop applications."

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

"We are using only plugins for the database and SAP."

"It is very stable. It is a market leader, and it has connectors to many of the legacy systems. It also has enterprise cloud connectors."

"It is a very robust system."

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

"Drag and drop make it easier to build the service end to end."

"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."

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

"Its queuing and messaging features need improvement."

"The initial setup is not easy."

"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."

"The pricing can be improved."

"Could be more user friendly in the development area."

"Technical support is average. It's not the best."

"A possible improvement could be to give the capability to use different profiles for each AppNode when an application is deployed on an AppSpace."

"Improve Business Studio's stability to further minimize development time."

"The challenges I have faced with TIBCO BusinessWorks mostly relate to financial applications that do not come with those adapters, so that requires custom coding."

"Performance and latency could be enhanced. Additionally, having signaling stack support would be beneficial."

"The cost of the solution has room for improvement."

"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 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."

"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 licensing is yearly and very costly for a company like ours."

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

"Licensing scheme is too rigid"

"TIBCO BusinessWorks is a very expensive solution."

"The payments made for service are the only addition to the standard licensing fees that we pay for the solution."

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