We performed a comparison between Axway AMPLIFY API Management and IBM API Connect 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."We like the portal for documentation a lot."
"The best feature of Axway Amplify API Management is its exceptional level of security, which is highly reassuring, coupled with its remarkable capacity to handle substantial volumes of data in impressively efficient turnaround times."
"There's drag and drop functionality so that you do not need to have a senior expert developer to make use of the tool. You can get more of your staff trained up to be able to use it as it's not overly technical."
"The API portal capability is a valuable feature."
"This product is a ten when it comes to API management."
"This platform can be highly scalable."
"I don't believe the Salesforce has been fully utilized yet. It gives us quick engagement."
"In general, API governance provides a better experience for providers."
"I have found IBM API Connect to be highly secure, efficient, easy to deploy, and has a great GUI. It can operate and integrate well with other vendors, such as Amazon, Google, and Microsoft."
"The functionalities on offer are very good."
"WSRR is a powerful component for getting the endpoints."
"The interface is very nice. It makes the solution easy to use and navigate."
"The developer portal has been the most useful feature."
"It acts as a central gateway for both external APIs and underlying systems. It's basically a central middleware for hosting APIs to the internet and consuming APIs from internal systems. It provides central governance for any APIs going outside the network, ensuring security and a common contract for API definitions."
"API Connect's most valuable feature is its ability to act as a gateway. It's very easy to configure security and everything else in it. You don't have to kill yourself implementing custom configurations."
"The product gathers data to measure API performance."
"Areas of improvement include marketing and enhancing the data products area by using ETIs."
"The installation process is a bit complex and it could be a lot simpler."
"Team management capabilities could be improved."
"Sometimes we find bugs where certain calls are not returning all the data we need."
"The areas for enhancement should be improving certain filters within the solution. Although they are generally functional, there are occasional problems that could be more precisely adjusted. Additionally, the solution performs well within its workload limitations, but it may not be suitable for scaling up or managing a larger volume of transactions through the gateway. To address this, it may be necessary to adopt a unique architecture rather than relying on traditional pre-packaged options."
"In terms of customer service, the company needs to be easier to contact, and the support team needs to understand the situation and the product itself better."
"This solution does have some limitations regarding the deployment model."
"It would be great if they have an asset report. It's hard to get support for that."
"The integration of an API gateway that implements the sidecar pattern, which can be deployed in cloud applications, and expose the microservices directly in each pod, this can be more decentralized components."
"We ran it on top of the Kubernetes cluster, so it wasn't a standalone service. In the worst-case scenario, API Connect couldn't stay online if all the containers went down. We had to restart all the services. We shut down all the containers automatically one by one."
"We have asked IBM for scalability and for some other features that we wanted. We had a dialogue with them and in the end, they have agreed to provide us with features related to API setup and security."
"The developmental process is not quite user-friendly."
"One thing about API Connect that could be improved is the security schemes. There are so many security schemes, and from a product perspective, IBM could improve the user experience of the configuration security scheme."
"Business applications could be exposed to users."
"I would like to see automation of the installation. If there could be a single-click function where you could automate everything, that would be helpful."
"Possible improvement is mainly around having more of the cloud oriented architecture bringing stability in adding new capabilities around security."
Axway AMPLIFY API Management is ranked 15th in API Management with 12 reviews while IBM API Connect is ranked 5th in API Management with 73 reviews. Axway AMPLIFY API Management is rated 7.8, while IBM API Connect is rated 8.0. The top reviewer of Axway AMPLIFY API Management writes "An API management solution for ESB and B2B integration between systems with security". On the other hand, the top reviewer of IBM API Connect writes "Good speed and performance, but it's based on a bit dated architecture". Axway AMPLIFY API Management is most compared with Apigee, Amazon API Gateway, Microsoft Azure API Management, Kong Gateway Enterprise and IBM DataPower Gateway, whereas IBM API Connect is most compared with Apigee, IBM DataPower Gateway, Microsoft Azure API Management, MuleSoft Anypoint API Manager and Amazon API Gateway. See our Axway AMPLIFY API Management vs. IBM API Connect 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.
