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
76
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 (7th), Integration Platform as a Service (iPaaS) (5th)
 

Featured Reviews

Allan Møller - PeerSpot reviewer
Sep 12, 2024
Transforms internal APIs with secure, manageable cloud compatibility
Our primary use case for Microsoft Azure API Management is to front internal APIs and make them cloud-compatible. It adds extra authentication on top of old APIs and acts as a proxy towards internal APIs, providing a single endpoint that can manage multiple APIs behind it. This is particularly…
Derrick Brockel - PeerSpot reviewer
Dec 14, 2023
An integration platform that enables you to automate tasks by connecting apps and services
Follow best practices,engage in their professional services to help build your messaging system and to be PR have some PR emphasis and and blue Bluegreen deployment You could take half your your clusters out, upgrade them, and put them back in so you have a quick callback. And also patch quarterly, we got we got downbound. And and at that point, it's a little hard to get into the cycle when you're releasing software every every week, and you're trying to, go through an upgrade seven fifty servers, it's a little hard to get into the upgrade flow when when you're running that tight. I rate the overall solution an eight out of ten.

Quotes from Members

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

Pros

"It's very well integrated with the Azure environment."
"The ability to easily connect back to Service Fabric is the most important for us."
"The solution's configuration capabilities are the most effective features for enhancing API security."
"The most valuable feature of Microsoft Azure API Management is the developer portal because it's very quick and easy to get something published."
"The ease of setting up a new solution is the most valuable feature. It's very easy to set up a new solution and to deploy it to production."
"Easy to integrate API management platform. It is a stable and scalable solution."
"The documentation and configuration of APIs."
"Most of the features are valuable to me."
"I like the tool's scalability."
"The tool helps us to streamline data integration. Its BPM is very strong and powerful. The solution helps us manage digital transformation."
"One valuable feature is that it is event-driven, so when new data is available on the source it can be quickly processed and displayed. Integration is definitely another useful feature, and B2B is one area where webMethods has its own unique thing going, whereby we can do monitoring of transactions, monitoring of client onboarding, and so on."
"The orchestration aspects of APIs, the integration capabilities, and the logging functionalities were the most critical features of our workflow."
"Application integrations are offered out-of-the-box, and that is extremely important to us. This is one of the main use cases that we have for it. It is about 60 to 70 percent of the workload in our application today."
"Some of the key features are the integration platform, query mechanism, message handling within the bus, and the rules engine. We've had a really good experience with webMethods Integration Server."
"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."
"The connectivity that the tool provides, along with the functionalities needed for our company's business, are some of the beneficial aspects of the product."
 

Cons

"Technical support could be more flexible and try to meet the client's needs a bit more effectively."
"From my understanding, there are some constraints around governance and service-to-service intercommunication managing priorities and our own governance."
"Could use clearer configuration when it comes to API policies."
"Microsoft Azure API Management could be improved by enhancing the preview feature, specifically the workspaces."
"Multi-tenant functionalities is missing from the system, especially when it comes to the developer code of features."
"It would be better if it were easier to transition to Azure from JIRA. For example, different nomenclature must be performed when you shift to Azure from JIRA. JIRA's storage, tasks, and ethics are treated differently from Azure. Here they might become functions, which is not an option in JIRA because that nomenclature difference is there. If someone has to get into the nomenclature, then there can be different tasks from clients, and here, they may be treated as functions. JIRA has sub-tasks, but sub-tasks don't exist in Azure. The nomenclature and the linking between ethics and a function and a story are different, and people may have to learn to adapt to the new nomenclature."
"The portal where we publish the APIs could be improved. Maybe this is because we didn't configure it. It is quite easy to bypass API management because we have a lot of information shared on the portal, where we publish our APIs. I worry there is potential for a security breach in the API publishing. There needs to be more security available on terms of the way we publish them."
"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."
"I would like to see the price improve."
"It is quite expensive."
"I would like to have a dashboard where I can see all of the communication between components and the configuration."
"The Software AG Designer could be more memory-efficient or CPU-efficient so that we can use it with middle-spec hardware."
"We need more dashboards and reporting engines that can provide detailed information for management. In short, we need better analytics."
"A potential drawback of webMethods.io API is its adaptability to legacy systems, which can vary in compatibility."
"Support is expensive."
"Other products have been using AI and cloud enhancements, but webMethods Integration Server is still lagging in that key area."
 

Pricing and Cost Advice

"Based on the resources that we are leveraging, the price we are paying to use this solution is slightly higher than other competitors. In a few cases, it has its own advantage in some resources."
"This is an expensive solution."
"It is an expensive solution, but any API solution will be expensive."
"Azure API Management is the most expensive solution on the market."
"It costs around 30,000 Kronas a month, which translates to about $3,000 dollars monthly."
"Licensing fees are paid on an annual basis."
"Azure is a pay-as-you-go model. You build out your virtual environment and pay a monthly price depending on CPU cores, storage, etc."
"It's pay as you go. The subscription packages have room for different scales. It's calculated by the number of apps or computers you use. You do not have to use the enterprise subscription. These subscriptions have different pricing, so you can find one to meet your needs for scalability."
"webMethods Integration Server is expensive, and there's no fixed price on it because it has a point pricing model. You can negotiate, which makes it interesting."
"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."
"The price of webMethods Integration Server isn't that high from an enterprise context, but open-source ESB solutions will always be the cheapest."
"With our current licensing, it's very easy for us to scale. With our older licensing model, it was very hard. This is definitely something that I would highlight."
"Sometimes we don't have a very clear idea what the licensing will entail at first, because it can be very customizable. On one hand, this can be a good thing, because it can be tailored to a specific customer's needs. But on the other hand it can also be an issue when some customer asks, "What's the cost?" and we can't yet give them an accurate answer."
"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."
"Pricing has to be negotiated with the local Software AG representative. SAG can always prepare an appropriate pricing model for every client."
"The price is high and I give it a five out of ten."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
815,854 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
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
 

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: October 2024.
815,854 professionals have used our research since 2012.