TIBCO BusinessWorks vs Talend Stitch ETL comparison

"The most valuable feature of Stitch for us is ease of use. This solution is fire-and-forget. All an organization has to do is set up the connection or integration and move on."

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

"Good TIBCO BusinessWorks features are the admin console and the ability to roll back to the previous version."

"Stability-wise, I rate the solution a ten out of ten…On a scale from one to ten, where one is difficult, and ten is easy, I rate the initial setup a nine."

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

"One of the most valuable features is that it's a simple development. It takes a short time to get services to work."

"The Business Studio interface based on SCA Standards helps to show the business logic at first look and improve code maintenance."

"Areas for improvement would be the cloud fitness of the product and the ease of migrating to newer versions."

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

"Generally speaking, support is a pain point. In the next release, I would love to see a change in support from the current chat to a more comprehensive portal."

"There is room for improvement on the learning side."

"Challenges with TIBCO BusinessWorks were mainly due to unclear documentation, but these were overcome by referring to comprehensive documents and raising tickets with TIBCO support."

"The learning curve takes time compared to webMethods."

"The Business Studio tool can be improved, which is the tool for designing the processes. Improving the Business Studio tool will make this solution more stable. It has a steep learning curve, and it is pretty tough to learn."

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

"The cost has room for improvement."

"The creation of XSDs should be much simpler."

"The communication protocols could be improved."

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

"Licensing scheme is too rigid"

"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 give the cost of the solution a four out of ten."

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

"TIBCO BusinessWorks is expensive."

"TIBCO licensing is yearly and very costly for a company like ours."

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