We performed a comparison between Apigee vs IBM API Connect based on our users’ reviews in four categories. After reading all of the collected data, you can find our conclusion below.
Comparison Results: Apigee has an edge in this comparison because it received higher marks than IBM API Connect in the ease of deployment and support categories.
"This is a front-layer gateway that helps to improve our overall performance."
"It nice and easy for the clients and those using the product to access the product's help resources."
"The use case which I have installed serves the intended purpose."
"Easy interface to monetize and deliver APIs with very easy integration for third-party development environments/delivery."
"The initial setup isn't too complex."
"It's easy to use and the security features are valuable."
"Lifecycle management."
"I have not encountered instability with the product."
"This is a very easy to use solution."
"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."
"We really like the runtime capabilities of IBM API Connect. The creation of products and the control of the monetization and hit rate are some of the features which we've found very valuable."
"We are able to share those APIs instantly within the organization; even if we want to share it outside publicly, then we can have those capabilities."
"The functionalities on offer are very good."
"This product is well integrated with other products. Its ability to interact with IBM Secure Gateway and other integration products is the core feature. Also, the lead time to put it into production is relatively short ."
"The management of the API and API portal is good."
"Easy to configure security and generate API keys."
"Compared to its competitors, such as Axway AMPLIFY API Management and Layer7 API Management, Apigee could benefit from having more policies to cater to various use cases. This would reduce the need for writing custom JavaScripts. If more features come straight out of the box, we can leverage them instead of writing custom code to achieve the same functionality."
"We need better performance monitoring."
"We are experiencing some performance issues."
"I have heard there maybe be some security issues that need to be addressed. If this is the situation I would encourage taking a look at the security matters."
"I would recommend this solution to those who want to start using it, but it depends on the requirements and automation."
"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."
"I would like to see SOAP services and socket-based connectivity developed."
"When it comes to the rate limit, we don't have a specific category for rate limits for a particular customer."
"The implementation of IBM API Connect is complex, as it's an enterprise solution with many components that require more than one person. It's not a single product that you work on, and this is an area for improvement, but normally, it's good. Having a more structured model for IBM API Connect support is also room for improvement that would help customers better."
"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."
"The automation and the simplicity could be improved."
"The developmental process is not quite user-friendly."
"API Connect's analytics subsystem could be improved to make it easier to render content from the analytics system and offload it to an external database."
"Possible improvement is mainly around having more of the cloud oriented architecture bringing stability in adding new capabilities around security."
"It is expensive within this class of products."
"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."
Apigee is ranked 2nd in API Management with 82 reviews while IBM API Connect is ranked 5th in API Management with 73 reviews. Apigee is rated 8.2, while IBM API Connect is rated 8.0. The top reviewer of Apigee writes "Has a robust community and outstanding performance". On the other hand, the top reviewer of IBM API Connect writes "Offers basic API orchestration and provides robust security and governance features". Apigee is most compared with Microsoft Azure API Management, WSO2 API Manager, Amazon API Gateway, Layer7 API Management and MuleSoft Anypoint API Manager, whereas IBM API Connect is most compared with IBM DataPower Gateway, Microsoft Azure API Management, MuleSoft Anypoint API Manager, Amazon API Gateway and 3scale API Management. See our Apigee 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.
Of those three: MuleSoft Anypoint. But, cost-friendly is another term, I would choose a different solution. We are happy with Gravitee.