We performed a comparison between Microsoft Azure API Management and webMethods.io Integration based on real PeerSpot user reviews.
Find out in this report how the two API Management solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."Monitoring: It gives us a detailed overview of how clients are using the API and it allows us to see the consumption trends in real-time."
"It's very well integrated with the Azure environment."
"The tool's most valuable feature is the integration of CI/CD with the API gateway."
"The API management and the hosting of the API platform are great."
"I like the support they provide for the APIs more than the solution itself. First of all, documentation-wise, both Microsoft Azure and even Google Cloud are up there. But in comparison, the real-time consulting and support for APIs make Microsoft stand out a little. I also like the performance. Standard public cloud provider-built APIs are more resilient and flexible in terms of what feature you want to use and what feature you don't want to use, and they're more customizable. They are more resilient in terms of performance in that particular environment because that is the design aspect of the offering. When public clouds build APIs and deploy them after testing them on their framework for a certain amount of time, I feel there is a massive difference in the product's performance. On the interface, everything is strong."
"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."
"Everything is already available and ready to operate without a lot of preparation work."
"The solution is quite stable. We have no issues with it. there have been no crashes and we haven't experienced bugs or glitches. It's been quite reliable."
"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."
"The solution is scalable."
"It's easy to construct new interfaces like apps and client portals."
"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."
"I like the tool's scalability."
"There's hardware, software and application integration, providing hosting flexibility."
"If I compare this solution to others I have used in other phases of my life, having APIM being an Azure resource, it is easy to configure and deploy. However, this conversely reduced the flexibility. The difficulty is how do we configure it in a manner that a larger enterprise would probably want it to be. This creates a bit more complexity, working around the constraints of the resource itself. If comparing it to other solutions, it is more of a legacy design with an older approach. The various level components are still around resembling an on-premise type of design similar to other solutions, such as Apigee or Mulesoft. They are still predominantly carrying some legacy design. Which might be suited for organizations where they have a more complex network layout. APIM is easy to deploy, but on the other side of that, it is constrained to how Azure has designed it to be."
"One of the most important improvements for us would be if it supported the HTTP/3 version and new protocol over a quick connection."
"In terms of improvement, it would be helpful if they could develop an on-premises option."
"Microsoft Azure API Management is lagging behind Apigee and should also have a better CICD process."
"Microsoft Azure API Management should have the ability to allow multitenancy."
"Technical support could be more helpful and responsive."
"Multi-tenant functionalities is missing from the system, especially when it comes to the developer code of features."
"There is a limitation of 32 kb of data in the APIs. Having the limitation increase would be a benefit."
"webMethods.io Integration's installation is complex. It should also improve integration and connectors."
"The product's stability is an area of concern where improvements are required."
"The products, at the moment, are new and there should perhaps be support for the older version of the protocols."
"The solution's release management feature could be better."
"It is difficult to maintain."
"I am not satisfied with the solution because it takes too much effort to migrate and add new information. The migration could be easier."
"Rules engine processes and BPM processes should be improved."
More Microsoft Azure API Management Pricing and Cost Advice →
Microsoft Azure API Management is ranked 1st in API Management with 67 reviews while webMethods.io Integration is ranked 29th in API Management with 7 reviews. Microsoft Azure API Management is rated 7.8, while webMethods.io Integration is rated 7.8. The top reviewer of Microsoft Azure API Management writes "Efficiently manages and monetizes API ". On the other hand, the top reviewer of webMethods.io Integration writes "Though the tool provides great connectivity functionality, it needs to be made more stable". Microsoft Azure API Management is most compared with Amazon API Gateway, Apigee, MuleSoft Anypoint API Manager, Kong Gateway Enterprise and Axway AMPLIFY API Management, whereas webMethods.io Integration is most compared with webMethods Integration Server, SAP Cloud Platform, Apigee, Microsoft Azure Logic Apps and Amazon API Gateway. See our Microsoft Azure API Management vs. webMethods.io Integration report.
See our list of best API Management vendors.
We monitor all API Management reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
