This product is used to expose some internal APIs to help us automate different activities.
Automation Engineer at a computer software company with 10,001+ employees
Stable, straightforward to set up, and has centralized management
Pros and Cons
- "It is helpful to have a central API that is hosted and managed."
- "If they had different levels of support available then it would be easier to justify the costs."
What is our primary use case?
How has it helped my organization?
What is most valuable?
It is helpful to have a central API that is hosted and managed. It reduces costs and customers, suppliers, and vendors receive a uniform interface.
What needs improvement?
The license model and the cost of licensing can be improved. Especially given that we are in a stable operational mode.
Buyer's Guide
Layer7 API Management
October 2024
Learn what your peers think about Layer7 API Management. Get advice and tips from experienced pros sharing their opinions. Updated: October 2024.
814,649 professionals have used our research since 2012.
For how long have I used the solution?
We have been using Layer7 API Management for five or six years, and we have been actively using it this year.
What do I think about the stability of the solution?
It has been working quite well for a long time.
What do I think about the scalability of the solution?
It's been working for us, from a scalability perspective. It's implemented within a central group, so there are just a couple of roles that run it. The APIs we host are stable.
How are customer service and support?
We are in a stable maintenance mode, so we haven't had to engage customer service/technical support for some time.
Which solution did I use previously and why did I switch?
We did not use another similar solution prior to this one.
How was the initial setup?
It's a complex product, but I would say that the initial setup is straightforward.
What about the implementation team?
Our in-house team handled the deployment.
We have a handful of IT admins and app admins who specialize in maintaining Layer 7
What was our ROI?
What's my experience with pricing, setup cost, and licensing?
It is a pricey product, although priced to the market.
Which other solutions did I evaluate?
What other advice do I have?
Overall, this is a good product. It's been stable and working for us, and our main difficultly is people calling out the price point on it.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Enterprise Architect at DXC Technologie
I love the composability of the policies, and having visibility into who is using which APIs
Pros and Cons
- "I love the API Gateway, especially the architecture, in terms of the composability of the policies. We approach it from a very software-engineering approach.We build on the policies, like legal blocks, and we deploy them throughout different environments. It's been working out great for us."
- "Some of the performance matrix that API Gateway gives off, we monitor them via SNMP traps, and then we tie them into our monitoring system. You can actually monitor some of the latencies and some of the performance aspects of both API Gateways, as well back end services. So having that line of sight surely helps in terms DevOps."
What is our primary use case?
We have the API Gateway deployed in production. The primary use case is for the API Gateway to provide API access, and authentication, and authorization for the APIs we expose through our product.
I am also looking forward to having the API developer portal deploy as well so we get a bit more insights into the analytics part, and also some of the API lifecycle management associated with it.
I love the API Gateway, especially the architecture, in terms of the composability of the policies. We approach it from a very software-engineering approach.We build on the policies, like legal blocks, and we deploy them throughout different environments. It's been working out great for us.
How has it helped my organization?
It definitely helps a lot with the DevOps and the support. Reliability is one thing, and having visibility into who is using which APIs.
Some of the performance matrix that API Gateway gives off - we monitor them via SNMP traps - and then we tie them into our monitoring system. You can actually monitor some of the latencies and some of the performance aspects of both API Gateways, as well back end services. So having that line of sight surely helps in terms DevOps.
What is most valuable?
The most valuable feature, as I mentioned, is the composability, because we use a lot of functionalities.
Also, right now we're looking into the Dockerized version of API Gateway because that would allow us to flow nicely into our Microservice Architecture.
What needs improvement?
The more automation the better. I think CA is stepping in the right direction. I went through the micro API Gateway presentations here at the CA World conference, on how you can automate more of the policy deployment via the JSON format, so you don't even having to touch the Policy Manager. Because every time you touch something in the Policy Manager you think, "Well, that's a GUI, humans need to go in and do something with it." So if we can automate everything with the APIs, that helps a lot in the DevOps lifecycle, where we want to automate everything.
For how long have I used the solution?
One to three years.
What do I think about the stability of the solution?
I've always been a fan of API Gateway. In the past we've used various API Gateways, some of them are open source. It's definitely very reliable and robust. The three years that we have them in production, not a single instance of downtime due to the API Gateway. We have issues, but it's mostly because of API backend issues or low balance issues and such, but API Gateway has been pretty reliable for us.
What do I think about the scalability of the solution?
The scalability has been good. Now we have exposed the APIs, we have a four-node cluster of API Gateways in production. It's been scaling out well for us. I haven't had any issue yet.
How is customer service and technical support?
I have ended up using technical support several times. I think it's fantastic. I've been working with a particular technical person in CA and he's been really, really helpful. He's been very busy, but the support that he gives me is above and beyond the call of duty.
Even going through the 24/7 support I usually get the answer back within 24 hours.
How was the initial setup?
It was three years back, and at that time there wasn't a lot of automation going on with the API Gateway. It was a lot manuals, so we're using the OVA version of the API Gateway. As time went on, with the API Gateway you can pretty much auto-provision things. But two years back at least, I wasn't aware of that, so there was some manual steps. But even manual it was still quite painless to get it done.
Which other solutions did I evaluate?
We did do some evaluations against other products. Just to name a few, we looked at Mulesoft, WS02. We went with CA because the solution is simple to implement, it fits our use case well, and in terms of price point it also chimes well with our VPs.
What other advice do I have?
I like that CA is continuing to improve the product, looking for new solutions using the API Gateway. That's something that we're familiar with. And that they're trying to make it work for different types of architectures. As I mentioned, we are moving toward Microservice Architecture and having the Docker form and the micro API Gateway to help with those kind of architectures is really helpful.
I'm an engineer, so from my perspective things have to be simple. If things get way too complicated then maybe you don't have the right solution, or you're not using the right solution to solve the right problem. In that case you may want to look for a different solution.
When selecting a vendor, as an engineer the solution that's offered by the vendor needs to be simple enough to solve my problem in an efficient way. Of course, I don't worry too much about cost because I'm not paying for it, but certainly cost does play a part in terms of licensing scheme.
The solution you choose depends a lot on the use case, so without really understanding a colleague's use case it would be hard for me to recommend anything at all. Definitely, if they want functionality like API management, I would recommend looking at CA to see it fits their use case or not.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
Layer7 API Management
October 2024
Learn what your peers think about Layer7 API Management. Get advice and tips from experienced pros sharing their opinions. Updated: October 2024.
814,649 professionals have used our research since 2012.
Cyber Security Advisor
The Gateway Migration Utility is a pretty good tool to use. Overall, this solution is not easy to integrate with others.
What is our primary use case?
Our primary use case is to enable our customers who are on the Internet. We want them to access our protective web series behind a corporate firewall. To do that, we like to use the OAuth ToolKit within the CA API. It can minimize the password exposure by generating a token using the ToolKit, then use the token to make the web services calls to our protected back-end services.
What is most valuable?
- The ToolKit with OAuth Manager
- The Policy Manager
- The Gateway Migration Utility (GMU) is a pretty good tool to use.
How has it helped my organization?
We are still evaluating it, so I cannot comment much on this.
What needs improvement?
I would like to see more documentation. The current documentation is there, but we do not find it very useful. For example, we wanted to integrate with PingFederate TV provider and there was not enough information to customize the way we wanted. It took a lot of effort and we had to reach out to the Gateway folks to help us out on how to do that customization. Thus, it is not easy to integrate with other solutions.
For how long have I used the solution?
Still implementing.
What do I think about the stability of the solution?
It is pretty stable. We have not seen any issues, anywhere, where we need to restart.
What do I think about the scalability of the solution?
We are still doing a PSA, so we will have to see how it scales once we ramp up volume and we roll out to the production with real life traffic.
How is customer service and technical support?
We engaged an architect from CA. They were pretty good.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Manager, Information Technology - Integration Technology Engineering at a financial services firm with 5,001-10,000 employees
We route all our policies and traffic through the gateway. It's reliable.
What is most valuable?
The best features of CA API Management are high quality and high reliability.
How has it helped my organization?
It provides a centralized security mechanism so that we can route all our policies and all our traffic through the gateway.
What needs improvement?
I would like more graphical interfaces for better usability.
What do I think about the stability of the solution?
API Management is highly reliable and highly available, so we haven't any problems with it.
What do I think about the scalability of the solution?
We haven't had any scalability problems. I don't know how far it can be scaled. We are a mid-sized company.
How are customer service and technical support?
I would say that the quality of technical support is moderate. It’s better than some, but not as good as others.
Which solution did I use previously and why did I switch?
I don't know if we had a previous solution before going with API Managment. We have a number of CA products. Some of them, we started with the CA product and some of them we started with other products and then switched to CA because of their high availability and high reliability. We are not looking to switch it. It’s nice and stable.
How was the initial setup?
I was not involved with the initial setup.
What other advice do I have?
Focus on developing a relationship with CA. They have a variety of products and they do a lot of cross selling, so it's important to develop a relationship and figure out how to manage that relationship as you go forward.
When selecting a vendor, the most important element is relationship.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Sr. Tech lead at a manufacturing company with 10,001+ employees
A helpful tool for authentication purposes
Pros and Cons
- "The security checking authentication is our primary use case for this solution."
- "We have experienced technical difficulties with the product in the past."
What is our primary use case?
The security checking authentication is our primary use case for this solution.
What is most valuable?
The API gateway is good.
What needs improvement?
We have experienced technical difficulties with the product in the past.
For how long have I used the solution?
Three to five years.
How is customer service and technical support?
Tech support is helpful. I would give it an 8 out of 10 rating.
What's my experience with pricing, setup cost, and licensing?
I do not have any experience with the pricing or licensing of the product.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
student at a tech services company with 1,001-5,000 employees
Provides secure API exposure but the cloud-native architecture needs improvement
Pros and Cons
- "The most valuable feature is the security with its out-of-the-box policies."
- "The cloud-native architecture of the product needs improvement."
What is our primary use case?
API security, API management, OAuth security, microservices, mobile app security.
How has it helped my organization?
Secure API exposure and driving Innovation through microservices.
What is most valuable?
Security, out-of-the-box policies.
What needs improvement?
Cloud-native architecture of the product.
For how long have I used the solution?
More than five years.
What do I think about the stability of the solution?
We haven't encountered any issues with stability. The hardware and virtual appliance-based form factor are solid. It's a stable product.
What do I think about the scalability of the solution?
The product does not scale the way cloud-native architecture does.
How is customer service and technical support?
Technical support is good.
How was the initial setup?
The initial setup was moderately complex, due to various deployment models and integration with its own components.
What's my experience with pricing, setup cost, and licensing?
It is in the lowest price range for such products but the pricing model needs to be changed.
Which other solutions did I evaluate?
I have experimented with all of the APIM solutions. Each one is fit for different situations but, overall, CA API Management is the best product for the expected functionality.
I have evaluated Apigee, Mulesoft, SoftwareAG, Akana, Kong, and IBM API Connect.
What other advice do I have?
If you are truly looking for API management features, CA API Management is the best solution. It might be a bit old in terms of cloud-native architecture but they are moving towards that.
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner.
Senior Engineer at a transportation company with 1,001-5,000 employees
Streamlines initial set up for single sign-on for web services, save us time
What is our primary use case?
Web services authentication.
So far so good, in terms of performance.
What is most valuable?
Quick response to the setup authentication for web services. That's important to us because we generally don't have a lot of time.
How has it helped my organization?
It's separating web services versus web applications, single sign-on. I would say that is the main benefit.
What needs improvement?
- More throughput
- More scalability
- Better built-in monitoring
What do I think about the stability of the solution?
So far stability is pretty good. We haven't experienced lag time or crashes.
What do I think about the scalability of the solution?
Scalability is very good.
How are customer service and technical support?
I think we have used tech support but the response has been so-so. They need more knowledgeable people.
Which solution did I use previously and why did I switch?
We didn't have a previous solution.
What other advice do I have?
When selecting a vendor the most important factors for us are
- cost
- validity of the product
- stable product
It's a very good product to use to initially set up single sign-on for web services authentication.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Associate Vice President at a financial services firm with 10,001+ employees
Go ahead. A very good product and a market leader in its segment.
What is most valuable?
Live API Creator.
How has it helped my organization?
The simple REST based APIs can now be delivered in hours which took days previously.
What needs improvement?
The product shouldn’t require to be connected to a server for doing development.
For how long have I used the solution?
Six months.
What do I think about the stability of the solution?
No.
What do I think about the scalability of the solution?
No.
How are customer service and technical support?
Good.
Which solution did I use previously and why did I switch?
No.
How was the initial setup?
Very easy.
What's my experience with pricing, setup cost, and licensing?
Not sure on that front.
Which other solutions did I evaluate?
Mashery and IBM.
What other advice do I have?
Go ahead. A very good product and a market leader in its segment.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
Download our free Layer7 API Management Report and get advice and tips from experienced pros
sharing their opinions.
Updated: October 2024
Product Categories
API ManagementPopular Comparisons
Microsoft Azure API Management
Amazon API Gateway
webMethods.io
MuleSoft API Manager
Kong Gateway Enterprise
IBM API Connect
IBM DataPower Gateway
WSO2 API Manager
3scale API Management
SwaggerHub
Axway AMPLIFY API Management
TIBCO Cloud API Management
Akana API Management
Buyer's Guide
Download our free Layer7 API Management Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- When evaluating API Management, what aspect do you think is the most important to look for?
- What is the difference between an API Gateway and ESB?
- In a Digital Banking Environment how do we see the role of ESB/ API Managers?
- What is an API Gateway?
- How do you protect your API from security threats?
- What should one take into consideration when choosing an API management solution to manage Microservices?
- Which API Management tools have the best developer portal?
- Which API management tool is the best?
- What is your favorite API Management tool?
- What are the key parts of an API strategy at an enterprise?