We performed a comparison between Apigee and Layer 7 API Management 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 very high availability and makes it easy for users to manage the entire lifecycle of the API. It offers vast opportunities for easy customization. Users find some of Layer 7 API Management’s tools and features difficult to implement and bulky, causing processes to slow down. Layer 7 could also use more cloud-native features.
"Highly scalable from any initial topology to horizontal extension"
"I have not encountered instability with the product."
"The developer portal is very useful to customers."
"I have found the most valuable features to be tracing a proxy, and managing proxy versions and revisions via the Edge UI component."
"The analytics function and the developer portal are the two valuable features of Apigee. The analytics part is very good, and the developer portal is quite rich in features."
"The most important feature is the security capabilities and the way it integrates very quickly with other security providers. We have integrated it with Azure and it integrates quite seamlessly."
"It is a stable solution...It is a scalable solution."
"A simple platform that's easier to work with than IBM API Connect. Support for it is really good and gives it advantage over other providers."
"The latest version that just came out at the first of October really was a powerful move in the right direction. I was very, very pleased with that because it allows now beginning to use information of things. We've got this IOT infrastructure that we can plug into, and for my use cases there are a lot of outdoor sensors that provide valuable information to my customers."
"As an organization grow, you can use CA API Management for authentication purposes through the CA API Gateway. It allows for multiple identity providers with different Active Directories."
"The Gateway can front our APIs very easily."
"We have more than 50 applications in the backend. We monitor the infrastructure through a database monitoring tool. Our daily tasks involve working on P1 incidents, managing change requests, conducting patching updates, working on P2 tickets, backend server certificate renewals, etc."
"Has great drag-and-drop features and requires minimal coding."
"It's pretty easy to use, and once we have templating set up we can add new APIs, at least through the gateway, and apply the security to them; it takes a minute."
"The solution's technical support is good."
"Easy to use, nice UI, and good search functionality."
"Access restrictions can be improved."
"When there is an update on a new version or an automatic update, you have to be present and double-check that the update is reflected in the environment with no issues."
"It is an expensive solution."
"I don't have any notes for improvement."
"We've encountered challenges in leveraging Connect functionality, prompting us to explore additional tools, such as Fergus, to address implementation and security issues."
"Technical support model for OPDK should be more exposed and mature in terms of providing support during installation, run, and debug of Apigee in production on OPDK mode."
"There should be an integrated continuous integration and continuous deployment approach with Apigee. Currently, for development at a more integrated level, you have set it up yourself."
"Integration should be improved."
"There could be more integration options included in the product."
"I feel there is a lot to improve in terms of providing plug-and-play functionalities, as at the moment it requires a lot of coding in their specific language for implementing a medium-complexity use case."
"The entire lifecycle management approach needs improvement: from the API management, development, deployment, some of the settings around the quotas, and some security policy applications, etc. for the APIs. We found the Apigee platform a lot more robust in that area."
"The OTK, however, is a complex upgrade. They tend to change the schemas on the database behind it, between the versions, which can be a pain to have to migrate all of our existing clients from one database schema to the other."
"The implementation of CA API Management was complex. It is a complicated solution. You have to know so much IT knowledge to do the implementation."
"The Policy Manager tool that is used to manage the solution is very heavy to use because it is based in Java. Sometimes it takes a long time to load. There could be some improvements to it. If they could make Policy Manager on a web page that would be a good alternative."
"It needs better mobile features and HA configuration."
"Layer7 API Management should improve the quota policy for the number of API calls."
Apigee is ranked 2nd in API Management with 82 reviews while Layer7 API Management is ranked 10th in API Management with 109 reviews. Apigee is rated 8.2, while Layer7 API Management is rated 8.4. The top reviewer of Apigee writes "Has a robust community and outstanding performance". On the other hand, the top reviewer of Layer7 API Management writes "Has great drag-and-drop features and it requires minimal coding ". Apigee is most compared with Microsoft Azure API Management, IBM API Connect, Amazon API Gateway, WSO2 API Manager and MuleSoft Anypoint API Manager, whereas Layer7 API Management is most compared with Kong Gateway Enterprise, Amazon API Gateway, MuleSoft Anypoint API Manager, Microsoft Azure API Management and IBM API Connect. See our Apigee vs. Layer7 API Management 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.
