Palantir Gotham vs TIBCO BusinessWorks comparison

"This solution is seamless. From one platform, we can do just about anything."

"It is user friendly, it's not complex."

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

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

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

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

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

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

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

"I think there should be less coding involved. Currently, using it involves a tremendous amount of coding."

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

"Cloud fitness is lacking"

"Scaling with the solution is costly because if we need to scale up, we have to buy more memory. That means more money. Solutions like Camel or Pulsar come with built-in options to scale horizontally, vertically, region-wide or country-wide."

"The creation of XSDs should be much simpler."

"The learning curve takes time compared to webMethods."

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

"The creation of XSDs should be much simpler. They should ensure that what was working in the previous version must also work in the new version of BW six."

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

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

"The product is not cheap."

"My understanding is that the licensing is very costly."

"Licensing scheme is too rigid"

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

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

"TIBCO BusinessWorks is a very expensive solution."