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 Summary
 

Categories and Ranking

Microsoft Azure API Management
Ranking in API Management
1st
Average Rating
7.8
Number of Reviews
73
Ranking in other categories
No ranking in other categories
webMethods.io
Ranking in API Management
10th
Average Rating
8.0
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 (6th), Integration Platform as a Service (iPaaS) (4th)
 

Featured Reviews

AK
Mar 9, 2023
Good API management with out of the box functionality and good support
We have to put the logs in Datadog. We need to use some other product to do all of the things we want. That costs extra. However, there are other solutions, like Dynatrace, that offer more features and have more functionalities. Right now, we have to use logic apps. You need more third-party apps to fill in the gaps. If I want to connect to other apps to Saleforce or Snowflake, et cetera, I need a quicker way to do mapping and to integrate everything together. I need to have microservice access. I'd like to have better flexibility and more capabilities.
RJ
Oct 21, 2022
Good designer and helpful support, but can be buggy
The solution can be buggy. If I compare it with IBM, before webMethods, we were using IBM DataPower. To be frank, DataPower had very, very minimal bugs. You may have one or two bugs in maybe a year, whereas with Integration Server, with customizations, it comes with all these caveats. We had to go back to support a bit for help. Support is expensive. There is not any capability as a managed service. Maybe a managed service would help people to use it. Or apart from that, I would also say there is a containerized microservices version, yet it is not in a usable format. If you look at a Kubernetes environment, if you want to have a containerized application running in Integration Server, it's still quite very heavy. Maybe webMethods should look at that perspective as well to run a pure proper cloud-native environment. If you look at Spring Boot or maybe a similar open-source application, you can easily containerize and run Kubernetes. In Integration Server, it's not very easy.

Quotes from Members

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

Pros

"What I like most about Microsoft Azure API Management is that it's flexible and user-friendly. The solution also has rich documentation and guides available, so users can configure and use it."
"The mediation and translation from SOAP to REST technology makes it possible to open up legacy systems that couldn't be opened before."
"The solution has significantly improved our organization by providing a user-friendly and easy-to-deploy API management system."
"The price is pretty reasonable for us."
"The most valuable feature is the developer portal, which has source code examples in various programming languages to help developers learn the API."
"We're very satisfied with Azure API Management. We've had no issues with bugs, everything runs smoothly, and the connection between the cloud and the on-premise infrastructure was good."
"The package as a whole is useful for our customers."
"The most valuable features of Microsoft Azure API Management are the easy configuration and deployment with automation."
"It is a very stable product."
"The synchronous and asynchronous messaging system the solution provides is very good."
"The comprehensiveness and depth of Integration Servers' connectors to packaged apps and custom apps is unlimited. They have a connector for everything. If they don't, you can build it yourself. Or oftentimes, if there is value for other customers as well, you can talk with webMethods about creating a new adapter for you."
"Our use case is for integration factory for SAP. It is mostly for SAP integration."
"Oracle's self-service capabilities, of which we make extensive use, is the most valuable feature."
"webMethods Trading Networks is a good solution for interacting with outside of the organization. We can integrate the solutions with multiple outside the organization."
"Segregation of deployment for the environments is the most valuable feature of the solution."
"It's a visual tool, so our transformations can be quickly implemented without a lot of fuss. The fact that we have an easy way to expose REST services is also very interesting. It offers the possibility to connect over GMS to synchronize message brokers."
 

Cons

"When you start with Azure API management, you also need to onboard the Azure console and the Azure cloud environment, which comes with a price."
"The product needs to introduce a developer portal."
"They're trying to implement versioning and trying to be able to manage different versions of your API all at the same time, but they're not doing that just quite right yet."
"The hybrid part could be improved because API Management is entirely cloud-based, but some of our resources are on-prem, so formatting is an issue. Our goal is dual implementation."
"The API gateway can be very complex."
"The solution’s security and performance could be improved."
"From my understanding, there are some constraints around governance and service-to-service intercommunication managing priorities and our own governance."
"The licensing tiers can be misleading."
"In terms of scale, I would give it a four out of 10."
"I would like to have a dashboard where I can see all of the communication between components and the configuration."
"Scalability and connectors to different cloud applications is lacking."
"The price should be reduced to make it more affordable."
"It would be nice if they had a change management system offering. We built our own deployer application because the one built into webMethods couldn't enforce change management rules. Integration into a change management system, along with the version control system, would be a good offering; it's something that they're lacking."
"Technical support is an area where they can improve."
"They should develop clear visibility for the onboarding."
"The solution should include REST API calls."
 

Pricing and Cost Advice

"It's an expensive solution"
"The price of the solution is reasonable compared to others."
"The product pricing is reasonable."
"There are additional costs to the standard licensing fees."
"We are paying standard fees to use Microsoft Azure API Management."
"Azure API Management is the most expensive solution on the market."
"It is an expensive solution, but any API solution will be expensive."
"We pay for a yearly license."
"Always plan five years ahead and don’t jeopardize the quality of your project by dropping items from the bill of materials."
"I am not involved in the licensing side of things."
"The price is high and I give it a five out of ten."
"Pricing is the number-one downfall. It's too expensive. They could make more money by dropping the price in half and getting more customers. It's the best product there is, but it's too expensive."
"webMethods.io is expensive. We have multiple components, and you need to pay for each of them."
"This is an expensive product and we may replace it with something more reasonably priced."
"The solution’s pricing is too high."
"The price of webMethods Integration Server isn't that high from an enterprise context, but open-source ESB solutions will always be the cheapest."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
801,394 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Computer Software Company
14%
Manufacturing Company
9%
Insurance Company
7%
Financial Services Firm
14%
Computer Software Company
14%
Manufacturing Company
11%
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
 

Learn More

Video not available
 

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: August 2024.
801,394 professionals have used our research since 2012.