We have many use cases. We are doing an enterprise install for all CA API management tool searches which are covered under the ELA, Enterprise License Agreement. We have close to a 100 plus use cases that we want to deploy, the next is over a six months to one year timeline.
Technical Principal at FedEx Corporation
The company partners with us within the account and our organization. The vendor team for our install was lacking expertise.
Pros and Cons
- "The Mobile API Gateway is also great."
- "CA double up portal is a pain. It is something that we are struggling with right now."
What is our primary use case?
What is most valuable?
There are many things, which are really good, like the Gateway. That's really great and pretty useful. The Mobile API Gateway is also great.
How has it helped my organization?
We have not tested it to the extent that we should. Maybe six months down the line we will have a better picture.
What needs improvement?
At a high level, I would say the portal is a pain. CA double up portal is a pain. It is something that we are struggling with right now. That is just one of the products which is probably not sufficiently satisfactory. We are struggling to get it installed to be used now.
It is not a fully-baked product as a whole. So, individual solutions may be good, but they are evolving in their silos. There needs to be wholistic thinking about how each one of these products functions. Each one of these CA products under API management needs to work in synergy, and evolve in a more cohesive, coherent way so we as enterprise we can take it seamlessly without much pain.
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?
Less than one year.
How are customer service and support?
We have not used technical support yet.
Which solution did I use previously and why did I switch?
We have ELA with other product vendors, like IBM and Oracle. However, we thought CA might be a good option based on their support within the account. The CA folks who are working, partnering with us within the account and our organization, they have been very reachable and very cooperative.
So even though we have licenses with IBM and Oracle for the same kind of products, API management, we are going ahead with CA just because of the trust that they were able to build.
How was the initial setup?
It was probably not that straightforward, because the vendor team (CA Services) struggled a bit.
What about the implementation team?
We implemented using CA Services to come and install the software.
I felt there was a lack of expertise on CA's part, because there are many things within the API management. Maybe the consultant from CA services who came to our organization did not have the experience on all the tools that CA was releasing, which was why the initial setup may not have been straightforward for him. He was good with Gateway, but with the other pieces, he was struggling a bit. It took sometime for him.
Which other solutions did I evaluate?
We already have ELA with multiple product vendors. It is a matter of using which one we want and moving forward.
What other advice do I have?
CA is worth trying. It is definitely a key contender in the API management space.
Most important criteria when selecting a vendor: size and brand value.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Sr. Systems Engineer at a hospitality company with 1,001-5,000 employees
We were able to market our mobile app products with their security features.
Pros and Cons
- "Ease of use."
- "There is a need for the migration of policies, better reporting, and monitoring integration."
What is most valuable?
- Time to market
- Ease of use
- Strong support
How has it helped my organization?
We were able to market our mobile app products with their strong security features.
What needs improvement?
There is a need for the migration of policies, better reporting, and monitoring integration.
For how long have I used the solution?
I have used this solution for two years.
What do I think about the stability of the solution?
There were no stability issues so far.
What do I think about the scalability of the solution?
I did encounter scalability issues. I wish they could extend the MySQL replication to multiple nodes.
How are customer service and technical support?
The technical support provided is the best.
Which solution did I use previously and why did I switch?
Initially we were using MuleSoft Enterprise Service Bus (ESB) before we switched to CA API Management.
How was the initial setup?
The setup was straightforward.
What's my experience with pricing, setup cost, and licensing?
CA has great pricing for gateways, so negotiate with your sales team.
What other advice do I have?
Make sure you involve networking, security, and other infrastructure teams for the implementation.
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
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.
Manager - API Management at a insurance company with 5,001-10,000 employees
With the API model, access to the backend is already available so you can concentrate on building a good user experience. You can’t document all details in the current developer portal.
What is most valuable?
It’s central to our mobile-first strategy. The API layer is becoming the interface to all of our legacy back-end and all of our new app development is being built on top of our API layer.
Key features – integration with SiteMinder and its ability provide security in general, content-based routing, and ability to turn our existing SOAP service back-ends into new REST-JSON APIs.
How has it helped my organization?
As the APIs are built and published and made available to developers, we can build applications on top of those APIs in days and weeks as opposed to months.
In a traditional web application you’re building your UI, your integration layer, your back end, all at the same time, and there are dependencies – you can’t built the UI until you have database access, etc.
With the API model, all that access to the backend is already available so all you have to concentrate on is building a good user experience.
What needs improvement?
They have really stabilized the API gateway in the last couple of releases. There’s a developer portal that is used to document your APIs that is woefully behind the times, in terms of being able to provide a really good robust experience for the developers consuming your APIs. You can’t document all of the details you need in the current developer portal and really need a separate web site just to document your API.
You need to understand what you want from an enterprise API, what your vision, what your plans are for rolling out an enterprise API, before you just go out and buy a product.
What do I think about the stability of the solution?
It’s been rock-solid. When we’ve had problems with a gateway – we have a whole group of them – we typically get very good support from CA and production downtime has not happened.
What do I think about the scalability of the solution?
Because it’s a clustered environment, we can scale horizontally as many as we need to go. So far two production gateways that are in a cluster and they’re processing transactions for one of our APIs at 30 calls a second and there’s barely a blip on CPU.
How are customer service and technical support?
In general, I’d give them about a 7/10 or 8/10. They’re good – sometimes it can take a little while to get to the right person. They tend to come back to us with obvious suggestions, which we try before we call tech support. When we get to the right person we get an answer immediately.
Which solution did I use previously and why did I switch?
It was an architecture decision to move towards a mobile-first API strategy. We realized that in order to meet the requirements of an API of a really good, strong enterprise API we needed to centralize that. That started us looking at APIM technologies. We scored a number of different vendors and brought in some to do POCs.
How was the initial setup?
Nothing in IS is ever simple. However, the install went very smoothly. The OVA files that you install into your VMware infrastructure -- configuration and getting them set up in the clusters went smoothly (respecting internal processes). The setup and config wasn’t that difficult. There was much more of a learning curve on our end to leverage and learn how to use the API gateway. It’s sort of like a Swiss army knife in that you have to learn how to use which tools and when.
Which other solutions did I evaluate?
I look for stability in the vendor. I look for their ability to understand our needs. We get a lot of vendors who are not used to working with a Fortune 500 company and the size and complexity of our operation is big and complex. We need vendors that are flexible and who understand that their solution might solve a problem, but that might not solve it the way we need it solve. The flexible vendor that is able to provide multiple solutions typically ends up winning.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
ALiBS Solutions at ALiBS Solutions
Many API protections against attacks, reliable, and good technical support
Pros and Cons
- "When I have used technical support they helped me a lot. Sometimes they took a long time to respond because we had very complex issues that we asked them for help with, but I think it is a very good service."
- "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."
What is our primary use case?
Our clients use the solution for a secured layer to protect their API. Most of them have two kinds of API, the frontend, and backend.
What is most valuable?
There are many beneficial features in this solution that protect against attacks, such as SQL, injection, and the internet.
What needs improvement?
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.
For how long have I used the solution?
I have been using the solution for approximately three years.
What do I think about the stability of the solution?
I have found the stability very good.
How are customer service and technical support?
When I have used technical support they helped me a lot. Sometimes they took a long time to respond because we had very complex issues that we asked them for help with, but I think it is a very good service.
How was the initial setup?
The initial setup was very easy and straightforward. However, the first and second time we did it was a bit complex because we were not used to the installation.
What about the implementation team?
We have done the implementation and the time it takes depends on the client's use case. You can do the installation and have some APIs working to generate some values for the clients in approximately 30 days.
What's my experience with pricing, setup cost, and licensing?
This solution is a bit more expensive than competitors.
Which other solutions did I evaluate?
My clients evaluate others solutions before they chose this one, such as AWS, and Apigee from Google. The most common option that they evaluated was Apigee because of the price.
The main difference was AWS and Apigee to this solution is they have a lower price but they do not have all the features that this solution has. It depends on the client, they have to decide between what features they want to implement. If there are not many features to implement they can go with Apigee or AWS, but if there are more complex implementations they try to go with Layer7.
What other advice do I have?
I would recommend this solution to others. I really like the solution.
I rate Layer7 API Management a nine out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Sr. Manager - Delivery, Enterprise & Platform Architect at a tech company with 10,001+ employees
Video Review
Most valuable feature is security along with performance and scalability.
What is most valuable?
The most valuable feature is security, which is the most important to our company. Then comes performance, scalability, and I see tremendous performance value without compromising the security. It gives us peace of mind, for example there are so many penetration attacks happening, DDoS kind of attacks happen in our API infrastructure if you don't have the security. With the out of the box security features from CA API Management, I can focus on the business logic to deliver the real value to the consumers, without worrying about the security. It's very stable, we've been in production for the last year and we didn't have a single production incident because of the API Management solution. I'm really happy with that actually. It's very stable and very reliable.
What needs improvement?
I see a lot in the developer portal. It's not that flexible the way we want it to be, so it's kind of out of the box and we can only do the standard features that they have. If you want to customize, it's a little bit hard for us, so I really want to see some flexibility in the developer portal. For the monitoring module, I also want to see some stability in the ESM module.
What do I think about the scalability of the solution?
Scalability is really good and they could do an average transaction size of probably 50-100KB with around 20,000 transactions per second, which is really impressive. Initially we thought we needed many licenses, but we ended up using only one part of the licenses.
How are customer service and technical support?
Technical support is really good. Their level 1 and level 2 support is really good. Sometimes when we try to add new features, when the team really gets stuck and we open the ticket, we usually get a response within a few hours.
Which solution did I use previously and why did I switch?
We were using the ESB solution, we were using SOAP services and then we wanted to move to REST based services so that we could open up our internal assets to our customers directly.
How was the initial setup?
Initial setup is good. It's straightforward. It's not that tough and it's an appliance, so that kind of took away wireless installation and base installation time, so our IT infrastructure team really loved it.
Which other solutions did I evaluate?
We looked at Apigee, Axway, Intel Mashery and a few more vendors.
The main thing is whether the product is really good. Look at the Forester and Gartner reports and how the support is, because a lot of good products are out there but we have seen in the past that we don't get good support. These are the major criteria I look at.
What other advice do I have?
Rating: for CA API Management I would give it a 9 out of 10, but for the developer portal I would give it a 6 out of 7. ESM I would give a 5 out of 6.
It's definitely a great product, I would ask to have an open mind and check out the features. I haven't seen any problems, and I have seen so many problems in my previous product, with ESB, so it's definitely a top notch product.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
The product implementation was complex, but the tool has a good user interface and is easy to use
Pros and Cons
- "The solution helped us to quickly publish and monetize APIs. I have used versioning responses to publish or send APIs to different customers with different versions."
- "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."
What is our primary use case?
I have used this tool for my customers, as I am a service provider, not an end user. I have dealt with implementations and configurations for CA API Management.
We implemented the API versioning for software services and REST services.
How has it helped my organization?
Mostly, it can identify client IT and user accounts to give them a lot of business logic. It can also provide API versioning. It can provide different versions to different customers, but the original API are the same.
What is most valuable?
Controlling microservices for my customers.
It provides a good user interface and is easy to use.
What needs improvement?
It is not user-friendly because you have to know so many programming languages.
What do I think about the stability of the solution?
It is a stable product. I have had no issue with it.
What do I think about the scalability of the solution?
The scalability is good.
When it comes to supporting a large number of APIs or transactions, the performance is not bad, because it is in staging. We have not moved it to production.
Our client's environment has four CA API Gateways.
How is customer service and technical support?
The technical support responds very quickly by email. The last time that I communicated with the technical support, I asked them, "If MariaDB, instead of SQL, is compatible with CA API Gateway?"
However, now CA's entire product service is poor in Taiwan, as there is no local support.
How was the initial setup?
The implementation of CA API Management was complex. It took us (my colleague and me) six months to implement with two people. My colleague was responsible for implementing the API Gateway.
My colleague is a system engineer. Because I am a programmer, I am in charge of the design and customizability. It is a complicated solution. You have to know so much IT knowledge to do the implementation.
What was our ROI?
The solution helped us to quickly publish and monetize APIs. I have used versioning responses to publish or send APIs to different customers with different versions.
What's my experience with pricing, setup cost, and licensing?
It has a reasonable pricing model by instance.
What other advice do I have?
I would not recommend the product based on how it has performed to implement it. I did not like working with the product.
We have not used it to modernize legacy systems via microservices, APIs, or developing a new platform for mobile. We also did not use it for connecting data to apps via APIs.
I am not familiar with the security aspects of the solution.
We stopped offering the product as a service a month ago since the product no longer belongs to CA. In Taiwan, I believe no one will buy CA products anymore because it is no longer trustworthy as a company, since the products are no longer supported.
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner reseller.
Owner at Clarity Iq Inc
Rapid development and deployment of APIs; I can present data in the format in which the client wants to consume it
Pros and Cons
- "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."
- "The benefits are rapid development and deployment of APIs, which means that your information, your ability to handle information, to receive it and to send it, to visualize it, to report on it, to get intelligence out of it, happens fast and happens with accuracy."
- "The most valuable feature is that it enables me to present data in the format that the client wants to consume it. That client might be a visualization tool, that client might be a report, that client might be a customer's API requirements."
- "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."
What is our primary use case?
I use CA Live API Creator to integrate data from a variety of sources, and then to provide an API response to calls from my client applications.
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.
How has it helped my organization?
The benefits are rapid development and deployment of APIs, which means that your information, your ability to handle information, to receive it and to send it, to visualize it, to report on it, to get intelligence out of it, happens fast and happens with accuracy. Faster is better.
It really allows us to do things that we just weren't doing before, things that we always talked about doing. Some things that we talked about doing for decades.
One of the things that we talked about doing for decades was the ability to bring data together from different sources, sources that maybe wouldn't otherwise be available. Maybe they were not ours to own. Maybe they were in a place where we just couldn't connect securely to them and enforce our security policies. What we can do is, as those things have developed APIs, we can consume APIs so we're building an API to consume an API to deliver an API. People can keep their roles and responsibilities, they can be responsible for their data integrity, and yet we can use that information to do what we need to do.
What is most valuable?
The most valuable feature is that it enables me to present data in the format that the client wants to consume it. That client might be a visualization tool, that client might be a report, that client might be a customer's API requirements.
The challenge is, how do you get the data structured in the way they want it, as opposed to how do you get them to change. My job isn't to make them change, my job is to give them what they want. Honestly, when you give people what they want, it's easy. When you try to get people to change what they're doing, it's hard.
What needs improvement?
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 we've brought on MQQT, and other ways of talking to those sensors, that just makes my life easier. I'd to continue to see them expand the scope of the product. But I can say that I've been extremely pleased with the work they're doing. They're not sitting around, every six months we get a release with major improvements.
Larger organizations have a real challenge. They have to control all the people that touch their data, and when it goes wrong - you've seen it on the news recently - it ends up being major headline news story. "Equifax exposes data to 150 million customers." That's intolerable to these customers.
What happens is that the companies that are working with that type of data have extremely rigid policies for who can get access to what. As we continue to develop the product in that regard, we would like to see continued integration with other CA products that accomplish that goal. I'm not saying that it doesn't do it now, I'm just saying that scenario where there can be continuous improvement.
For how long have I used the solution?
Three to five years.
What do I think about the stability of the solution?
I've used it for four years and I have not had any issues with downtime or with performance. That's partly because it's leveraging networks; modern networks are stable. Ultimately, people want their Netflix and their movies over the networks. There is a lot of money going into uptime, and performance, and speed of mobile networks, of physical networks, that we just leverage.
We benefit because of the performance of those networks. All we're doing is leveraging public networks to move data securely.
What do I think about the scalability of the solution?
In my use case, I've not dealt with the type of data that usually responds to the scalability issue. Generally, when people ask that question, they're talking about scalability of hits, scalability of users. Where, all of a sudden now, you have tens of thousands of records happening within a very short period of time - will this scale? I don't have tens of thousands of records happening in split seconds. However, I do know that the product's been tested to that and has demonstrated outstanding scalability results in that regard.
There are other aspects of scalability. You might consider how well can I bring on new customers, how well can I scale my development team, how well can I handle additional API integration. Because of the efficiency of the product actually doing that, pulling data from disparate sources, and integrating it into the response format that I want, that my customer demands, that's so easy. It's 10 times, 40 times, 100 times faster than the way we used to do it, and that makes it very scalable.
How are customer service and technical support?
I use the technical support extensively. I actually read the documentation. I know that's not something that people normally do, but I actually read the documents. One of the guys said, "If so and so, whoever writes it, knew that, she'd kiss you." And I said, "Well, maybe we shouldn't go there, but... "
I actually call them, and they've been wonderful because I have their cell phones, I can text, I can call. They probably don't want everybody to do that, but they want their products to succeed, they want me to succeed, and I want to work with a vendor that wants me to succeed.
Which solution did I use previously and why did I switch?
You look where your pain is. If you can perceive pain, you know what you need to do. Where does it hurt? That's what you need to work on.
A different solution didn't exist. You developed things in code. You used C++, you used Java, because that was the only way to do it, to build it yourself. Now, much of the lifting is done, but the extensibility is still in the product. What you're forced into, or what you have the opportunity to take advantage of, is a system that has done a lot of the hard and mind-numbing, repetitive tasks; simplified so many of the things that you would have to do. Incidentally, that creates an opportunity for a mistake. Those things are automated, but the extensibility is still there on the product, so you can still do the things that are specific to your business's needs.
How was the initial setup?
I'm going to assume that this question is asking, "Was I involved when we got on board with this product?" Yes, because I bought it. They were there for support but the question is not relevant because it's so easy. It's deploying a WAR file. If you can deploy a WAR file, you're done.
Which other solutions did I evaluate?
Where I got involved with CA on this product, there were not really competitive products. Since that time, there probably are some companies that have come out, but honestly, I am busy enough, I don't really look because there's no reason to divorce myself from CA on this product.
What other advice do I have?
When selecting a vendor, there are a couple of things that you have to look at. One is: Are they going to be around? That's always a concern because if you've committed to something and the rug gets pulled out from under you, then you're scrambling. Depending on the time that happens, you might not have the time or the money to scramble. What if you're in the middle of a big implementation? CA has been around since the beginning. They're a four billion dollar a year company, something like 13,000 employees, I'm not worried about that. Yet they're easy to work with.
There are a couple of products that I work with that have not let me down, and there are a lot of products that have. I always use Microsoft Excel of an example of this. Excel is a wonderful product, you can do so much with Excel, it's an incredibly powerful product. But there are many times where Excel just leaves me short. I just can't do what I need to do with it. It has limitations, fundamentally.
There are a couple of products that I've worked with in my life that I haven't run into that. Maybe I still will someday, I don't want to be delusional, but this product, when I've had a need, I've been able to get it to work and that's nice, I like that.
It's hard for me to give tens, but I would give it a 10 out of 10.
My advice would be: Focus on its extensibility because of that exact issue we just discussed. There are so many times when you look at a product that is a tool to make something easier. Maybe you're building a web-based application. There are a number of tools on the market that make that a drag-and-drop opportunity or a drag-and-drop process. Those tools are great for the weekend warrior, you can get something done quickly. Maybe you're a high school kid and you want to build an app for something. (Access database would be like that too. You can get a database and it's not that hard, and you can make a form, but they're not enterprise class).
This product, at first blush, looks something like it's one of those weekend warrior tools, but it's not. It's an enterprise-class tool with the kind of usability that you wouldn't expect. And with that usability - how do you have your cake and eat it too? Well, it's because of the product's extensibility. It's very well-integrated with your existing Java library of processes and procedures, as well as your ability to write new extensions to it. You get so much of the base functionality but you don't give up the ability customize.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Technical Principal at FedEx Corporation
We can get more visibility into our data with their tool, however their upgrade solutions are complex
Pros and Cons
- "It is fairly stable for the Gateway side."
- "We can get more visibility into our data."
- "The Gateway can front our APIs very easily."
- "The initial setup was very complex."
- "The Portal is not stable."
What is our primary use case?
The primary use case is we are using the API Management Suite. It has the Gateway and Portal, and we are using the Gateway to front all the APIs in FedEx.
The Gateway is performing very well. The Portal is not.
How has it helped my organization?
We can get more visibility into our data.
The benefit of the Gateway is that it provides security, authorization authentication, and analytics. These are the main benefits which we are using it for.
What is most valuable?
The most valuable, for the Gateway, is it can front our APIs very easily, and it can integrate with FedEx easily, so those are good.
For the Portal, we are able to manage with APIs and documentation. However, there are a lot of improvements, which could be done on the Portal side.
What needs improvement?
For additional features, I would like to see how it can be deployed into the cloud platform out-of-the-box and not having to do a lot of the initial setup. If it can be done out-of-the-box, that will make customer's life very easy.
Their upgrade solutions are not straightforward. Therefore, we are running the older version. We wanted to go to the latest and greatest. However, it is really complex going from where we are to the next one.
What do I think about the stability of the solution?
It is fairly stable for the Gateway side. However, not for the Portal side.
What do I think about the scalability of the solution?
We have seen that it can scale both vertically and horizontally.
How is customer service and technical support?
We have used technical support quite often, and they are really good. We have opened multiple tickets, and they are very responsive, especially for the Severity 1 tickets.
How was the initial setup?
The initial setup was very complex.
What about the implementation team?
CA Service was helping me with the implementation.
Which other solutions did I evaluate?
Initially we were looking into different options. We looked into Apigee, Axway, and CA. We did the whole evaluation, and CA come out to be the winner, because CA is the market industry leader.
What other advice do I have?
From CA's new technologies, it looks like CA is moving in the right direction.
Look to your performance matrix and your benchmarks. What are you interested in? If you are looking for support, this is definitely the best solution.
Most important criteria when selecting a vendor: Performance is one of the major ones. Security is another.
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
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?