We performed a comparison between IBM API Connect 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."The solution is very scalable because it's on the cloud."
"This is a very easy to use solution."
"The management of the API and API portal is good."
"The most valuable features of IBM API Connect are its performance and user-friendliness."
"The developer portal has been the most useful feature."
"API Connect is a good product, and everything works fine. All the analytics are good, and it is easy to follow up. I like it in that sense. I'm more focused on following up on analytics by seeing how many API calls we are getting and where we see a lot of problems. I was working on that API level."
"The product gathers data to measure API performance."
"It is a very scalable solution."
"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."
"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."
"It's a good tool, and it has a stable messaging broker."
"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."
"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."
"The installation was difficult with the IBM toolkit."
"IBM info-center help documentation also needs improvement. Competitive product like Apigee provide out of the box policies to run Javascript, JAVA and better/flexible logging policies."
"Possible improvement is mainly around having more of the cloud oriented architecture bringing stability in adding new capabilities around security."
"They seem to have left out a feature for microservices and also a certification module for OIDC."
"Automation for our Domino applications could be improved."
"The design time setup has a lot of customizable fields, but we need certain standard fields to be added, such as what all of the consuming systems are. This needs to be very clearly articulated during the design time."
"Like any typical IBM infrastructure setup, you need to learn to set it up yourself. It's not one of those simple zip files or an archive unzip and you're up and running in some few minutes. Knowledge to set it up is key."
"In terms of what needs improvement, some of the product documentation could be better."
"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."
"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."
"It is an expensive solution and not very suitable for smaller businesses."
"Understanding the overall architecture is difficult."
"They should develop clear visibility for the onboarding."
"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."
"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."
IBM API Connect is ranked 5th in API Management with 73 reviews while webMethods API Gateway is ranked 11th in API Management with 10 reviews. IBM API Connect is rated 8.0, while webMethods API Gateway is rated 8.2. The top reviewer of IBM API Connect writes "Good speed and performance, but it's based on a bit dated architecture". 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". IBM API Connect is most compared with Apigee, IBM DataPower Gateway, Microsoft Azure API Management, MuleSoft Anypoint API Manager and Amazon API Gateway, whereas webMethods API Gateway is most compared with Apigee, webMethods.io Integration, Kong Gateway Enterprise, 3scale API Management and webMethods Microgateway. See our IBM API Connect 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.
