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.
"Its flexibility allows seamless management of different products, showcasing scalability to handle extensive solutions."
"It's a good return on my investment."
"The security provided by the solution is excellent."
"The security that you have with Apigee is very good and aligns with compliance."
"The usability is one of the best aspects of the product."
"It is scalable."
"The solution is stable and reliable."
"The flexibility allows you to quickly run a cloud-native application architecture."
"The Mobile API Gateway is also great."
"Easy to use, nice UI, and good search functionality."
"The initial setup process is easy and flexible."
"It can be scaled as we need. And it can be used in different regions. We have different data centers in the U.S. and Beijing. We use it on-premise, on-cloud, and it can be hosted and used at any place and scaled across the regions."
"The solution's technical support is good."
"I work for an information security company. CA API Management is capable of using tokens for authorization to manage access control for the APIs."
"There are a couple aspects of performance. One is just speed and uptime, and it's stellar in that regard. The other is, how much effort is it to put it in place in the first place, and then how much effort is it to keep it operational. That's where its real strength is. I'm able to do things quickly and easily that I couldn't do before."
"Every API that we get from external or from internal goes through this layer first, and it should not be a bottleneck. That was the problem we had before. Now it's no longer a bottleneck. It's more like a throughput, this process is less than 10 milliseconds for any particular API."
"They have an external developer platform that was a little bit painful."
"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."
"Apigee could do more to make users aware of what is available in the add-ons."
"They need to work on the cost of the solution."
"The entire user across all the layers should be singly authenticated through an external authentication system."
"The initial setup for the on-prem solution is a little complex."
"Better functionality for validating inputs and outputs would be helpful."
"They should improve the monitoring tools for on-premises environments."
"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."
"They need a multifactor authentication solution for the API layer and the other layers, as well."
"They need a workflow for the API Developer Portal, where the process only allows requests to go to the correct person."
"They should incorporate deeper monitoring features into the solution to make the offering more complete. Doing so would help to showcase traffic patterns and usage to better engage customers and partners proactively. It would also help with API management and capacity planning."
"we cannot add gateways on the fly because there are a lot of moving parts; endpoint connectivity is one of them. If we add more nodes then the rate-limiting feature is affected. This kind of gateway always has the scalability issue. But, I think CA is coming up with its Microgateway, which is in Beta. If they stabilize their Microgateway platform, we could do very well in terms of scalability."
"There is room for improvement in terms of innovation and investment, especially when compared to other leading products in the market."
"As the number of instances increases, its complexity of installation increases if you do not use the OVA."
"It would be nice if we could create APIs directly from Swagger files. We're doing that ourselves with a middle layer. But if you could integrate with open API Swagger specs, and then just create a Swagger and upload it to the gateway and it would create all my API template policy, and would apply the OAuth restrictions, the types of security restrictions I have on there, that would be pretty cool."
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.