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."I'm still evaluating, but in terms of overall performance and stability, it's quite good."
"Anyone with basic knowledge can build an API."
"It nice and easy for the clients and those using the product to access the product's help resources."
"The ability to convert from language to language using a single tool."
"Apigee is a great product with good feedback and recommendations from clients."
"They capture the details of all the incoming and outgoing traffic of your APIs. Based on 300+ default dimensions you can generate beautiful and insightful reports on usage and consumption of APIs."
"It is easy to deploy, configure, and monitor the APA."
"Highly scalable from any initial topology to horizontal extension"
"There were no complexities involved in the setup phase...The product is able to meet my company's API protection needs."
"I like the solution's policies, transformation, mediation, and routing features."
"The cloud version of the solution is very easy to set up."
"It's a good tool, and it has a stable messaging broker."
"The developer portal is a valuable feature."
"In the API gateway, there is a new feature that allows us to filter logs within a payload. This has been a useful feature."
"This solution has given us a competitive advantage because we have better automation and insight."
"What I like the most about the solution is that it comes with ready-made tools like handling security tokens and OAuth."
"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."
"The account simplification process can be improved."
"I don't have any notes for improvement."
"I'd like this solution to improve on releasing new features; I'd like it to be more frequent."
"Role-based access management needs to be improved. It would also be nice if the solution could be integrated with code versioning systems like Git/Bitbucket."
"The technical support could be improved because their response time is slow."
"I would like them to add features, such as caching and mediation policies."
"In terms of the functionalities of a typical API gateway, Apigee is actually doing its job, but when it involves integration with backend applications, which some gateways have, I don't believe it has this functionality. You have to do Java or do some other low-level coding before you are able to do the integration. Apigee has a lot of components, which means that management will be a bit difficult. It probably has ten different components, and all of these components leverage open-source utilities, such as NGINX. When those open-source vendors upgrade their utility, Apigee usually lags behind because they need to do a lot of tests and any required development in their own platform. They need to do rigorous testing to make sure that nothing breaks. Because of that, it takes them a while to upgrade whatever components have been upgraded by the open-source vendor that owns the utility. We've been chasing them for a particular upgrade for well over a year and a half, and they have not done that upgrade. It is creating a security risk for us as an enterprise, but that upgrade has not been done, even though the open-source vendor, the owner of the utility, has upgraded it a long time ago."
"With respect to the API gateway, the runtime component, the stability after a new release is something that can be improved."
"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."
"The high price of the product is an area of concern where improvements are required."
"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."
"Understanding the overall architecture is difficult."
"The price has room for improvement."
"In terms of improvements, maybe on the API monetization side, having users able to create separate consumption plans and throttle all those consumption plans towards the run time could be better."
"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."
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.