Try our new research platform with insights from 80,000+ expert users

WSO2 API Manager vs webMethods.io comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 17, 2024

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

webMethods.io
Ranking in API Management
9th
Average Rating
8.0
Reviews Sentiment
6.8
Number of Reviews
91
Ranking in other categories
Business-to-Business Middleware (4th), Enterprise Service Bus (ESB) (3rd), Managed File Transfer (MFT) (10th), Cloud Data Integration (8th), Integration Platform as a Service (iPaaS) (5th)
WSO2 API Manager
Ranking in API Management
8th
Average Rating
8.0
Reviews Sentiment
6.9
Number of Reviews
40
Ranking in other categories
No ranking in other categories
 

Featured Reviews

Michele Illiano - PeerSpot reviewer
Can function as an ESB along with the core product, with decent integration of message protocols
I have noticed that webMethods ActiveTransfer has had problems when handling large files. For example, when we receive (and perform operations on) files that are larger than about 16 MB, the software starts losing performance. This is why, for most customers who have to deal with big files, I suggest that they use a product other than ActiveTransfer. I would like to note that this problem mainly concerns large files that undergo extra operations, such assigning, unassigning, or file translation. When these operations take place on large files, ActiveTransfer will use up a lot of resources. Within the product itself, I also believe that there is room for improvement in terms of optimization when it comes to general performance. I suspect that the issues underlying poor optimization are because it is all developed in Java. That is, all the objects and functions that are used need to be better organized, especially when it comes to big files but also overall. webMethods ActiveTransfer was born as an ESB to handle messages, and these messages were typically very short, i.e. small in size. A message is data that you have to send to an application, where it must be received in real-time and possibly processed or acknowledged elsewhere in the system as well. So, because it was initially designed for small messages, it struggles with performance when presented with very large files. All this to say, I suggest that they have an engineer reevaluate the architecture of the product in order to consider cases where large files are sent, and not only small ones. As for new features, compared to other products in the market, I think Software AG should be more up to date when it comes to extra protocol support, especially those protocols that other solutions have included in their products by default. Whenever we need to add an unsupported protocol, we have to go through the effort of custom development in order to work with it. Also, all the banks are obligated to migrate to the new standards, and big companies are all handling translations and operating their libraries with the new protocol formats. But webMethods ActiveTransfer doesn't seem to be keeping up with this evolution. Thus, they should aim to be more compliant in future, along the lines of their competitors such as IBM and Primeur.
VishalSingh14 - PeerSpot reviewer
Easy to deploy APIs and easy to manage CORS configuration
I have used WSO2 Store and WSO2 API Manager at the architecture level. I worked on two versions, namely WSO2 API Manager 2.6.0 and 5.7.0. I have also worked with WSO2 Identity Server versions 5.7 and 5.11. There are certain things that Apigee handles better than WSO2 API Manager. The user interface of WSO2 API Manager is much easier than that of Apigee. The scope of flexibility was much greater in Apigee. In WSO2 API Manager, we had little flexibility and were restricted to a specific software or tool. On the other hand, we had the scope of customization in Apigee.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"webMethods Trading Networks is a good solution for interacting with outside of the organization. We can integrate the solutions with multiple outside the organization."
"The most valuable feature of the webMethods Integration Server is its reliability. It has a lot of great documentation from the service providers. Additionally, it is easy to use."
"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 solution is scalable."
"What I like best about webMethods Integration Server is its portfolio of connectors."
"The orchestration aspects of APIs, the integration capabilities, and the logging functionalities were the most critical features of our workflow."
"One of the most important features is that it gives you the possibility to do low-level integration. It provides a lot of features out of the box, and over the years, it has matured so much that any problem that is there in the market can be solved with this product. We can meet any requirements through customizations, transformations, or the logic that needs to be put in. Some of the other products struggle in this aspect. They cannot do things in a certain way, or they have a product limitation, whereas, with webMethods, I have never faced this kind of problem."
"I feel comfortable using this product with its ease of building interfaces for developers. This is a better integration tool for integrating with various applications like Oracle, Salesforce, mainframes, etc. It works fine in the integration of legacy software as well."
"Its open-source features are very good, especially for your production work."
"Most of the time, we need to install a plug-in without having any lapse in services or restarting the application. The WSO2 platform can do all deployments without any downtime."
"As far as I am aware this solution is the first API Publisher that allows you to create and publish API and to manage the API lifecycle."
"WSO2 API Manager provides OAuth2 token capabilities that our customers use to interact, onboard new customers, and provide approvals whenever a customer is onboarded."
"It is possible to scale up and scale down with the solution...I can say that I have not seen any issues related to scalability."
"This is a flexible and versatile API management solution that has the power to integrate with more than just API."
"It's very scalable, which is one of the best features."
"WSO2 API Manager is a stable solution."
 

Cons

"The configuring of the JWT token would be improved as it is a confusing process. We require more information on this part of the solution."
"webMethods Integration Server could improve on the version control. I'm not sure if Web Method has some kind of inbuilt integration with Bitbucket or GitHub or some kind of version control system. However, that's one area where they can improve."
"On the monitoring side of things, the UI for monitoring could be improved. It's a bit cumbersome to work with."
"Some things could be improved, especially how ActiveTransfer handles third-party file transfers. It would be nice to have a native file-watching mechanism for when you're scheduling jobs with a third-party scheduler. Currently, we are using an outside file watcher solution to check the files before the file transfer. It checks the location to see if the file is there. If the file is there, it will prepare it for transfer. If the file isn't available, it will send an email it can create a ticket send it now. We recommended adding this file watcher mechanism."
"The solution has big instances when deployed under microservices or in a containerized platform. They need to improve that so that it is competitive with other integration solutions, like Redis and Kafka. Deployments under microservices with those solutions are much more lightweight, in the size of the runtime itself, compared with Software AG."
"With respect to the API gateway, the runtime component, the stability after a new release is something that can be improved."
"webMethods Integration Server needs to add more adapters."
"Support is expensive."
"The solution could be more user friendly for engineers."
"Lacks some new features and updated functionalities."
"The user interface needs to improve, it is a bit outdated."
"The pricing models offered by WSO2 API Manager could be more flexible and should offer different options so that more people can access them."
"From a product perspective, the first thing is that although the documentation provided by WSO2 is good, it could be much better. We're in the middle of a complex migration, moving away from VMs to Kubernetes with the latest version of WSO2 and good documentation is essential to us right now."
"I would like it to be a more stable solution. Maybe in the last version that is approved. For me it would be good if they had a community established version."
"Integration is an area that needs to be improved."
"The product hasn’t been updated for some time."
 

Pricing and Cost Advice

"I do think webMethods is coming under increasing pressure when it comes to their price-to-feature value proposition. It's probably the single biggest strategic risk they have. They're very expensive in their industry. They've been raising the price recently, especially when compared with their competitors."
"Always plan five years ahead and don’t jeopardize the quality of your project by dropping items from the bill of materials."
"Most of my clients would like the price of the solution to be reduced."
"I would like to see better pricing for the license."
"The product is expensive."
"It is an expensive tool. I rate the product price a nine out of ten, where ten means it is very expensive."
"Some of the licensing is "component-ized," which is confusing to new users/customers."
"I don’t have much idea about prices, but webMethods API Portal is not something cheaper."
"We use the open-source version — the free version."
"For our projects, we found the pricing to be a little high."
"We have not opted for the paid version of WSO2 but we have implemented the free and open source WSO2 software to a great extent and it is working as per our expectation."
"It is an open-source product."
"WSO2 API Manager is a low-cost solution. It is one of the most affordable solutions."
"My previous company paid about 1.2 million dollars, and my current company pays about 300k. Both companies are at the enterprise level."
"The challenge is the increasing pricing, which has led some customers to consider alternatives, like using Spring Boot solutions instead. The rising costs, especially as cores and usage increase, have been a concern, prompting some to migrate to other products."
"WSO2 API Manager is quite an expensive tool. I rate the product's pricing a nine on a scale of one to ten, where one is low and ten is high."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
831,265 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
13%
Computer Software Company
13%
Manufacturing Company
13%
Energy/Utilities Company
6%
Computer Software Company
20%
Financial Services Firm
16%
Government
8%
Manufacturing Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about Built.io Flow?
The tool helps us to streamline data integration. Its BPM is very strong and powerful. The solution helps us manage digital transformation.
What is your experience regarding pricing and costs for Built.io Flow?
webMethods.io is expensive. We have multiple components, and you need to pay for each of them.
What needs improvement with Built.io Flow?
webMethods.io needs to incorporate ChatGPT to enhance user experience. It can offer a customized user experience.
What do you like most about WSO2 API Manager?
It is possible to scale up and scale down with the solution...I can say that I have not seen any issues related to scalability.
What needs improvement with WSO2 API Manager?
One area for improvement is monitoring. Dashboards for application monitoring of the APIs would be beneficial, allowing us to check for faulty APIs.
What is your primary use case for WSO2 API Manager?
We use WSO2 API Manager for our microservices and our APIs, both internally and externally.
 

Also Known As

Built.io Flow, webMethods Integration Server, webMethods Trading Networks, webMethods ActiveTransfer, webMethods.io API
No data available
 

Learn More

Video not available
 

Overview

 

Sample Customers

Cisco, Agralogics, Dreamforce, Cables & Sensors, Sacramento Kings
1. eBay 2. StubHub 3. Cisco 4. Verizon 5. T-Mobile 6. Vodafone 7. Orange 8. BT Group 9. Telstra 10. Deutsche Telekom 11. Swisscom 12. AT&T 13. Sprint 14. Telefonica 15. O2 16. British Airways 17. Lufthansa 18. Emirates 19. Qatar Airways 20. Etihad Airways 21. Air France 22. KLM 23. American Express 24. Visa 25. Mastercard 26. PayPal 27. Western Union 28. Citibank 29. HSBC 30. Barclays 31. Santander 32. Goldman Sachs
Find out what your peers are saying about WSO2 API Manager vs. webMethods.io and other solutions. Updated: January 2025.
831,265 professionals have used our research since 2012.