We performed a comparison between Apigee 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."Apigee's best features are flexibility and breadth of capabilities."
"Easy interface to monetize and deliver APIs with very easy integration for third-party development environments/delivery."
"Apigee Analytics dashboard is useful to monitor transactions, error percentage, transaction latency, etc."
"Its flexibility allows seamless management of different products, showcasing scalability to handle extensive solutions."
"Apigee has better scalability than WSA."
"The most valuable features of Apigee for me are analytics, security, ease of use, and integration capabilities."
"The following features are most valuable: API Management, Analytics, Quota, and the Developer Portal."
"Items around the mobilization of the API interface and the ability to automate validations for our APIs are the most valuable aspects."
"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."
"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."
"What I like the most about the solution is that it comes with ready-made tools like handling security tokens and OAuth."
"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."
"The developer portal is a valuable feature."
"There were no complexities involved in the setup phase...The product is able to meet my company's API protection needs."
"Areas like traffic handling of incoming requests, security features between third-parties and Apigee, and between Apigee and internal network servers, resources, or JSON areas, etc."
"The integration could be improved within the solution. There is a need to pay more attention to this."
"The company needs to better support webhooks. It used to support webhooks and their policies and they have since stopped. They had some issues in the product and they abandoned the support for them. It's not come back since."
"The analytical aspect of it could be better. I think it is fair if Apigee lets you configure some of the metrics of the key details you want to monitor in terms of analytics."
"Proxy versioning seems a bit confusing/buried in the publishing experience, especially for the URI-based versioning approach."
"The Apigee cloud admin UI could be more user-friendly by adding a few more features."
"The pricing for the product was a bit higher. I also found it challenging to manage sometimes."
"The solution’s scalability could be improved."
"The high price of the product is an area of concern where improvements are required."
"With respect to the API gateway, the runtime component, the stability after a new release is something that can be improved."
"The configuring of the JWT token would be improved as it is a confusing process. We require more information on this part of the solution."
"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."
"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."
"Understanding the overall architecture is difficult."
Apigee is ranked 2nd in API Management with 82 reviews while webMethods API Gateway is ranked 12th in API Management with 10 reviews. Apigee is rated 8.2, while webMethods API Gateway is rated 8.2. The top reviewer of Apigee writes "Has a robust community and outstanding performance". 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". Apigee is most compared with Microsoft Azure API Management, IBM API Connect, WSO2 API Manager, Amazon API Gateway and Layer7 API Management, whereas webMethods API Gateway is most compared with webMethods.io Integration, Kong Gateway Enterprise, webMethods Microgateway, 3scale API Management and CentraSite. See our Apigee 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.