Anonymous UserAPI Application Security Specialist
Ashutosh AggarwalVice President at a comms service provider
We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
"This solution is useful for making new APIs."
"This solution gives you a unified way to have your API accessed."
"In terms of most valuable features, it would say that it is really easy to start working with it."
"Its security feature is the most valuable because it is mainly a security solution. It has easy authentication and authorization, and its integration is also useful."
"It's easy to integrate and provide support for existing AWS services if I use the AWS API gateway."
"API Connect is a very good platform for the development of APIs."
"It is quite stable. We've not had any problem. It has made for a good buy because we are finding that other companies that have similar set ups go down maybe once a month."
"Our version supports containerized integration. I can write APIs, which can be moved into a testing environment without needing a forklift. It can check if APIs are compliant before moving them into production."
"It allows enterprises to expose some of their tech to outside stakeholders."
"The technical support is good. Whenever we need anything, we have our IT team work with IBM to change whatever requirement is needed."
"The gateway is the most valuable aspect of this solution."
"The centralized management: this provides a management module that can deploy and apply security policies to all APIs, including all the gateways that are deployed on-premises and on any cloud because the gateway component can run at a VMware or in a Kubernetes cluster."
"The capabilities are very good."
"There should be more videos and documentation about the new features that are released every month."
"The only real problem is that you have to know a lot about what is outside of the API gateway in order to make the best use of it."
"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."
"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."
"I am not completely satisfied with Technical Support."
"They seem to have left out a feature for microservices and also a certification module for OIDC."
"I would like to see support for non-Java based services. We struggle a bit to be able to deploy and connect our .NET services because of things like data types. We had to map a couple of things. For one solution provider, we had to move them to .NET Core before we could use it properly. I would like to see more agnostic tool service platforms rather than moving it more towards Java or open source."
"There are issues with upgrading in the cloud version. The cloud version is extremely buggy. We prefer to use the on-premise version."
"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."
"Extracting the data could be improved."
"In terms of what needs improvement, some of the product documentation could be better."
"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."
"It would be helpful to have access monitoring."
"This is a pay-per-use service, where you only pay for what you use."
"API Connect is quite pricey."
"I haven't seen anyone go from on-premise to the cloud. In fact, I am seeing people go from the cloud to on-premise because the costs can quickly grow on the cloud."
"It would be a good idea to bring down the pricing by at least 20 to 30 percent."
"The pricing is too expensive with IBM. Sometimes, we prefer to go with an open source or something more lightweight."
"It is expensive when compared to other products in this class. There were no extra fees for add-ons or technical support."
"It's an expensive product."
"IBM API Connect could be cheaper."
"It is quite an expensive product."
Amazon API Gateway is a fully managed service that makes it easy for developers to create, publish, maintain, monitor, and secure APIs at any scale. With a few clicks in the AWS Management Console, you can create an API that acts as a "front door" for applications to access data, business logic, or functionality from your back-end services, such as workloads running on Amazon Elastic Compute Cloud (Amazon EC2), code running on AWS Lambda, or any Web application.
Amazon API Gateway is ranked 8th in API Management with 5 reviews while IBM API Connect is ranked 5th in API Management with 18 reviews. Amazon API Gateway is rated 8.0, while IBM API Connect is rated 8.2. The top reviewer of Amazon API Gateway writes "A scalable solution with End-to-end protection for your service, and ties in well with the AWS ecosystem". On the other hand, the top reviewer of IBM API Connect writes "Offers a good SLA, with technical support available to help, but lacks documentation". Amazon API Gateway is most compared with Microsoft Azure API Management, Mulesoft Anypoint API Manager, Apigee, WSO2 API Manager and Kong Enterprise, whereas IBM API Connect is most compared with Apigee, IBM DataPower Gateway, Mulesoft Anypoint API Manager, Microsoft Azure API Management and 3scale API Management. See our Amazon API Gateway 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.