TIBCO BusinessWorks vs webMethods.io comparison

"The solution is stable. We haven't had any serious technical issues."

"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 most valuable feature is the low-code platform."

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

"The high availability, tolerance, and load balancing features are top-notch. Its scalability features are also pretty cool."

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

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

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

"Most of the work in our organization can be more easily done using the tool."

"High throughput and excellent scalability."

"It frankly fills the gap between IT and business by having approval and policy enforcement on each state and cycle of the asset from the moment it gets created until it is retired."

"It is good for communicating between the systems and for publishing and subscribing. We can easily retrieve data. It is good in terms of troubleshooting and other things."

"Within the new version, webMethods API Gateway gives us an end-to-end lifecycle from the creation of the API up into the development, deployment, and promotion into production/live. The current end-to-end lifecycle of the API gives us enough authority and governance of the API. We know what are currently live services, what is in the testing stage of development, and what version that has been commissioned. So, the full life cycle itself gives us full authority and governance of the API."

"Currently, we're using this solution for the integration server which helps us to integrate with the mainframe."

"It's obvious that the heart of the product lies here. It's comprised of all aspects of ESB (Enterprise Gateway, Adapter, TN, Java) and BPM (task, rules engine)."

"The tool supports gRPC."

"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 communication protocols could be improved."

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

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

"There are multiple plugins which increase the number of product installations."

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

"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 cost of the solution has room for improvement."

"With performance, there is room for improvement in regards to if we would like to put another extra layer of security on it, such as SSL. This is affecting their performance quite significantly. They need to improve the process of managing the SSL and other things inside their solutions, so there will not be quite such a significant impact to the performance."

"This product is for larger companies. Compared to TIBCO I think webMethods is better in terms of ease of use and support."

"Perhaps in the area of Microservices, where I think Trading Networks could benefit from some improvements."

"On the monitoring side of things, the UI for monitoring could be improved. It's a bit cumbersome to work with."

"The market webMethods Integration Server falls under is a very crowded market, so for the product to stand out, Software AG would need to get traction in the open source community by releasing a new version or a base version and open source it, so people can create new custom components and add it to the portfolio."

"The products, at the moment, are new and there should perhaps be support for the older version of the protocols."

"For code version control, you need to use some external software."

"This is a great solution and the vendor could improve the marketing of the solution to be able to reach more clients."

"The product is not cheap."

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

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

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

"I give the cost of the solution a four out of ten."

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

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

"There are no hidden costs in addition to the standard licensing fees for webMethods. For corporate organizations, it's a very cheap or fairly priced product, but for growing or small businesses, it's quite expensive. These businesses would probably need to consider an enterprise services bus at some point. Thus, from a pricing point, it closes out non-cooperate businesses."

"The product is very expensive."

"This is an expensive product and we may replace it with something more reasonably priced."

"There is a license needed to use the webMethods Integration Server."

"The pricing is a yearly license."

"Some who consider this solution often avoid it due to its high price."

"It is an expensive tool. I rate the product price a nine out of ten, where ten means it is very expensive."

"I do see a lack of capabilities inside of the monetization area for them. They have a cloud infrastructure that is pay per use type of a thing. If you already use 1,000 transactions per se, then you can be charged and billed. I see room for improvement there for their side on that particular capability of the monetization."