We performed a comparison between Amazon API Gateway and webMethods API Gateway 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."One of the most valuable aspects of API Gateway is its native integration with AWS services."
"t is easy for integrations if it is deployed in AWS Services."
"The solution is user-friendly."
"API Gateway offers a multitude of configuration parameters that enable versatile request filtering and protection against potential attacks."
"The initial setup is straightforward."
"It's easy to integrate and provide support for existing AWS services if I use the AWS API gateway."
"The most valuable feature in Amazon API Gateway is the itinerary release."
"In terms of scalability, I haven't encountered any issues with API Gateway. We've significantly increased our traffic from hitting it once or twice a minute to now hitting it ten to fifteen times within a minute. In an hour, we're receiving hundreds of hits. So, it's performing excellently."
"It's a good tool, and it has a stable messaging broker."
"There were no complexities involved in the setup phase...The product is able to meet my company's API protection needs."
"In the API gateway, there is a new feature that allows us to filter logs within a payload. This has been a useful feature."
"I like the solution's policies, transformation, mediation, and routing features."
"The most valuable aspect of this solution for me has been the configuration-based UI. Once you get the hang of it, it enables you to easily develop an API. In addition, it has many in-built policies that are quite handy."
"Within the new version, webMethods API Gateway gives us an end-to-end lifecycle from the creation of the API up into the development, deployment, and promotion into production/live. The current end-to-end lifecycle of the API gives us enough authority and governance of the API. We know what are currently live services, what is in the testing stage of development, and what version that has been commissioned. So, the full life cycle itself gives us full authority and governance of the API."
"This solution has given us a competitive advantage because we have better automation and insight."
"The cloud version of the solution is very easy to set up."
"Their support services come at a considerable cost, leaving room for improvement."
"The pricing could be improved. In cases where customers require real-time sync or real-time calling groups with IoT, the volume of data and time lag become a concern."
"The user interface, in general, can be better. The user interface for the entire Amazon cloud can be more friendly. There are some scenarios that are not really easy to manage and configure through the user interface."
"Amazon API Gateway will wait for only 30 seconds to get a response from other services, such as the Lambda function."
"It would be useful to have a more complete development environment for the developer, with different integrative capabilities to manage all the life cycles for the API. I think the full version formula for that is really useful. They should improve the development environment for easier integration."
"When working with XML payloads, there can be issues due to the lack of a seamless connection between API Gateway and Lambda functions."
"Monitoring could be improved."
"API Gateway lacks some governance features that MuleSoft offers, and there are additional features that could make it even better."
"There are things that could be improved with the webMethods API gateway. One thing is that it's too attached to the integration service and we'd like it to be a little bit more independent. We would like for them to separate operations so that it doesn't rely on the bulky integration server and so that it can be used everywhere."
"With respect to the API gateway, the runtime component, the stability after a new release is something that can be improved."
"Understanding the overall architecture is difficult."
"They should develop clear visibility for the onboarding."
"The high price of the product is an area of concern where improvements are required."
"With performance, there is room for improvement in regards to if we would like to put another extra layer of security on it, such as SSL. This is affecting their performance quite significantly. They need to improve the process of managing the SSL and other things inside their solutions, so there will not be quite such a significant impact to the performance."
"The price has room for improvement."
"It is an expensive solution and not very suitable for smaller businesses."
Amazon API Gateway is ranked 3rd in API Management with 37 reviews while webMethods API Gateway is ranked 11th in API Management with 10 reviews. Amazon API Gateway is rated 8.2, while webMethods API Gateway is rated 8.2. The top reviewer of Amazon API Gateway writes "Easy initial setup and highly stable solution". On the other hand, the top reviewer of webMethods API Gateway writes "We developed several services in the cloud using a sandbox environment for our last hackathon". Amazon API Gateway is most compared with Microsoft Azure API Management, MuleSoft Anypoint API Manager, Apigee, WSO2 API Manager and Layer7 API Management, whereas webMethods API Gateway is most compared with Apigee, webMethods.io Integration, Kong Gateway Enterprise, webMethods Microgateway and MuleSoft Anypoint API Manager. See our Amazon API Gateway vs. webMethods API Gateway 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.
