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

Microsoft Azure API Management 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:
 

ROI

Sentiment score
6.6
Microsoft Azure API Management cuts integration times by 90%, supports multi-environment apps, saves costs, and enhances operations.
Sentiment score
7.1
webMethods.io delivers rapid ROI through cost savings, reduced downtime, and increased productivity, depending on specific implementations.
Proper configuration of the solution, implementation strategy and correct scaling tier selection are other factors that influence the ROI.
Most of the time, where we work in companies, it is more of an internal policy or security guidance that we need to have an API gateway.
It helps connect all multi-environment applications to a single dashboard and give beautiful reports.
 

Customer Service

Sentiment score
6.7
Microsoft Azure API Management provides efficient service, though improvements in response speed and flexibility are needed, especially across time zones.
Sentiment score
6.6
webMethods.io's customer service is praised for responsiveness, but users note occasional delays and desire improved technical support communication.
Technical support is very poor and needs a lot of improvement.
We have regular sessions with Microsoft where we can have private previews of new features.
I rate the support from Microsoft Azure API Management a ten out of ten.
 

Scalability Issues

Sentiment score
7.9
Microsoft Azure API Management is praised for scalability, flexibility, and regional integration, despite potential scaling costs.
Sentiment score
7.2
webMethods.io is praised for its scalability in cloud and on-premises environments, with some licensing constraints noted.
I rate the scalability of Microsoft Azure API Management a ten out of ten.
Because it is on Microsoft Azure, we don't have to worry about scalability.
It can host it in different regions, and we can point to the same set of backups and try to expose the APIs.
Vertically, scalability is fine, however, I have not expanded horizontally with the product yet.
 

Stability Issues

Sentiment score
8.0
Microsoft Azure API Management is generally reliable, with minor performance issues, rated eight or nine for stability.
Sentiment score
7.6
webMethods.io is generally stable and reliable, with minor issues in specific modules and cloud version maturity needed.
This is the best service we have used within Azure and it has high availability.
I can't guarantee its stability or flexibility until all our databases and financial systems are integrated.
Microsoft Azure API Management is very stable.
There are some issues like the tool hanging or the need for additional jars when exposing web services.
 

Room For Improvement

Microsoft Azure API Management needs improvements in scalability, integration, security, cost efficiency, deployment, and user experience for better functionality.
webMethods.io needs clearer documentation, better scalability, intuitive interfaces, and improved integration and cost-effectiveness for enhanced user experience.
The service is extensive and expensive, and this added flexibility would make it more manageable and less prone to errors.
Support for GraphQL, which is a different communication specification, needs to improve.
It's quite expensive, which could be a barrier for some users.
A special discount of at least 50% for old customers would allow us to expand our services and request more resources.
 

Setup Cost

Microsoft Azure API Management offers competitive pricing, but premium features and additional service charges require careful cost management.
Enterprise buyers find webMethods.io costly but valuable, offering flexibility and comprehensive solutions, particularly beneficial for large-scale enterprises.
Moreover, there are additional costs to the standard licensing fees.
The more enterprise-level features you go to, the more expensive it gets.
The solution is highly expensive.
 

Valuable Features

Microsoft Azure API Management offers robust access control, seamless integration, and scalability, supporting diverse enterprise needs effectively.
webMethods.io excels in seamless integration, user-friendliness, robust security, and scalability, offering efficient tools and reliable management for diverse needs.
It's a low-code, no-code model of API hosting.
The platform's most valuable features are its rule-based permissions and comprehensive API lifecycle management capabilities.
The ability to create a subscription model for APIs allows companies to monetize valuable data and share it securely.
It facilitates the exposure of around 235 services through our platform to feed various government entities across the entire country.
 

Categories and Ranking

Microsoft Azure API Management
Ranking in API Management
1st
Average Rating
7.8
Reviews Sentiment
7.0
Number of Reviews
80
Ranking in other categories
No ranking in other categories
webMethods.io
Ranking in API Management
10th
Average Rating
8.0
Reviews Sentiment
6.8
Number of Reviews
92
Ranking in other categories
Business-to-Business Middleware (3rd), Enterprise Service Bus (ESB) (3rd), Managed File Transfer (MFT) (10th), Cloud Data Integration (7th), Integration Platform as a Service (iPaaS) (5th)
 

Mindshare comparison

As of March 2025, in the API Management category, the mindshare of Microsoft Azure API Management is 19.1%, down from 19.7% compared to the previous year. The mindshare of webMethods.io is 2.1%, up from 1.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management
 

Featured Reviews

Rajiv Bala Balasubramanian - PeerSpot reviewer
Efficiently manages and monetizes API
It is a scalable solution. You can add more computing power to your APM gateway. It also gives you the ability to have VNet integrations with your on-prem. It is one of the leading products in the API management space. It is not just software for users but software to handle requests. For example, for a B2C e-commerce store, all requests that users make from within the store pass through this API gateway. So it is defined by the number of requests to the API gateway, not by the number of actual users who use it. If you look at the number of requests, it would be a lot from all the different systems we have within Pampers.
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.
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
842,296 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Computer Software Company
13%
Manufacturing Company
9%
Insurance Company
7%
Financial Services Firm
14%
Computer Software Company
13%
Manufacturing Company
12%
Retailer
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

How does Apigee differ from Azure API Management?
Apigee offers both cloud-based and on-prem options while Microsoft Azure API Management currently only offers a cloud-based solution. Both solutions are easy to use. Apigee allows for the ability...
Which is better - Azure API Management or Amazon API Gateway?
If you use Azure products, API Management is a great solution. It solves many of the problems of externalizing web services. For example, when you need versioning, establish a developer portal and ...
What do you like most about Microsoft Azure API Management?
Microsoft Azure API Management is a good, comprehensive solution for enterprise implementation.
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.
 

Also Known As

Azure API Management, MS Azure API Management
Built.io Flow, webMethods Integration Server, webMethods Trading Networks, webMethods ActiveTransfer, webMethods.io API
 

Overview

 

Sample Customers

adnymics GmbH, LG CNS, Centrebet, netfabb GmbH, MedPlast, Accelera Solutions, Sochi Organizing Committee, realzeit GmbH, Opensistemas
Cisco, Agralogics, Dreamforce, Cables & Sensors, Sacramento Kings
Find out what your peers are saying about Microsoft Azure API Management vs. webMethods.io and other solutions. Updated: March 2025.
842,296 professionals have used our research since 2012.