I have worked with these tools for eight years there has never been an issue that has brought the system down and unrecoverable. Patch release is every quarter which include OS, applicate patches for form factor appliances and test builds for containers [Containers have now been in the build form the last three years releases i.e from version 9.x to the latest].

This is definitely a stable solution. 

We have not had many problems, but again, we are not testing under full, live production loads.  

It is a stable solution. Stability-wise, I rate the solution an eight out of ten.

Regarding stability, Layer7 API Management is an eight out of ten.

The stability of Layer 7 API management is generally good, with occasional instability after changes requiring restarts. In a production environment, once things are set up, stability is solid, and I would rate it around an eight out of ten.

The solution is very stable.

It is stable, as per our observations.

Layer7 API Management is stable. 

Our deployment is stable. The company was using API Management before I joined. It's pretty stable and people are developing their APIs on it. The integration Layer7 provides works well in our environment.

We do promotions and that's the only time you see some crashes. But overall it's pretty stable product and we haven't had issues with it.

It is very good software from the standpoint of making an API commercializable and making an API accessible. The security industry is extremely complex, to provide various security capabilities to an API that's fairly simpler. However, we are facing challenges in scaling the CA API Management software so we have seriously faced certain challenges when if your API usage goes beyond a certain limit, say 100,000 transactions per minute, I'm just throwing out a number, I can't provide you the real number but we are facing seriously challenges in scaling, in clustering the CA API Management software and then making sure that we can reliably meet our transactions as your usage grows on the Cloud.

Layer7 API Management is stable.

I haven't seen many issues with the product's stability. 

The product is stable. The Gateway is the most mature out of the product set.

We had some issues initially with Live API Creator, but they were resolved by understanding the product behaviour and how it functions. Once the back-end databases were aligned, the stability was okay.

CA was quite quick in fixing any issues with the product. The issue was rather with our side not deploying the fixes that we requested at the same speed as it was resolved.

The release intervals are very short, and you should plan for that. If your company still has a long interval view, then you will have to adapt.

The solution is very stable. There have been no issues.

It is quite stable. 

We have more than 100 nodes and things are going well so far. However, there are a few cases where we are learning about some outages and that is when getting good visibility of what is actually happening would be the key. In a few of the sessions of in CA World, I was able to get to know more about what additional add-ons we can do, how we can get good visibility, and what is lacking currently. 

I have found the stability very good.

I did not encounter any issues with stability.

In big industry stability is always challenge, some times internal users report that 3 out of 4 connections are successful and one is never reached to API Gateway, while diagnose report always says system is healthy, restart will make it work again

One of the reasons that we chose to go with another tool was because we found that CA API Management was crashing quite often. We called technical support about this, but since the deployment time was so short, we only called them a couple of times before we made a decision.

No issues with stability.

We have not experienced any issues with stability.

The solution is stable.

Layer7 API Management appears to be stable. No one has called me to say that it's not working.

The product is becoming more stable as the product has become more mature. At this point, it's a pretty stable product.

I think it’s a solid product. We’ve had some issues with the proprietary hardware that we’re running it on, but we’re getting rid of that and going to VMs, so the issue will probably go away. At one point in order to do certain types of upgrades to not only do it through a web interface, but we had to get deep into the system – multiple things we had to do in order to upgrade so it wasn’t as seamless as we had hoped.

No issues with stability.

We found a lot of stability issues in the 8.3 version. But even after reaching out to the CA engineering team, they were not able to diagnose the issue, so we upgraded it to 9.2. Most of the stability issues have been resolved and we're not seeing that many issues now. So the stability issues have calmed down but we faced a lot of them in 8.3.

Stability has been fine for us in tests. We have a challenge around some log rolling and it bringing it down in tests, but in production it's been great.

It's been very stable for us. We're using it as an appliance, so whenever we need to put new ones in, we just download it, implement it, and then just pull over the configuration files for it. It's been very, very stable for us, and the patching's been fantastic.

There were no stability issues so far.

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.

It is a stable product. I have had no issue with it.

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.

It is fairly stable for the Gateway side. However, not for the Portal side.

Stability is great. We run a high resilient load balance configuration. We haven't had any problems with it.

It's been very good. 

We have had some issues. Technically it's like a database replication issue, where our operations people tell me that the audit logs have been quite large, and that has caused some replication issues between the two nodes in our cluster. 

But outside of that, it's been very good.

Once it goes live, it's very stable, clearly, it's as stable as your infrastructure or authority or testing is, but once it goes live, as long as you sort of adhere to all the policy management, and make sure you're progressing code, you're testing it correctly, once it goes live it's pretty stable. We've not had any failures with it in the year and a half that it's been live, and it's very stable. From a performance perspective, it's great. You can throttle, you can do rate limiting, so it's very flexible for us.

The stability is excellent. The product is very good.

The stability is good except when we went live with AWS; that's when we had initial hiccups but slowly it improved. We are good at this point.

At our organization, we're still not into production but we have some references from other industries like the telecom industry. What we have seen is that there are some initial hiccups, as you encounter with any new technology.

However, once you have proper organizational structure in place to support and manage API gateway appliance, things become smoother.

It is extremely stable.

So far the stability has been really good, we haven't had any problem. I believe we have been using it for sometime. As per the industry standards, it's been quite stable. Personally, I have been involved for almost 2 years but I understand that our organization has been using it for quite some time. We are in a business which sees lots of volume, trillions of volumes of calls. The system that we work with has to handle those trillion number of volumes of calls. All of that also happens in the real time, so the system has to scale up to spikes. Sometimes during holiday season and all that, we see quite a lot of spikes going in. The system has to manage all those spikes and CA has been able to do that.

I rate the product’s stability an eight out of ten.

It is a stable product.

There are some issues from the front and backend, but none relating to the API portal.

We have not faced many issues with its stability.

We had some problems getting it installed, but it has been running fine ever since.

It needs to be a bit more stable. I think they see that, as Support is working on that. We have our own challenges related to the stability. For example, the log space filling up the entire disk because of gateway went down. CA is aware of this issue.

But otherwise, as I said, we have had a pretty good experience with the product.

We have not experienced any stability issues. The product has been very stable.

We've had it working for about 4 or 5 years now and apart from upgrades, we have never had a problem with outages or components breaking down.

The cloud-based solution that we use right now is stable. We have an on-premise solution as well, which we still have some issues with, but we're still moving forward.

This product is stable.

It has been stable from day one. We haven’t seen anything to suggest it won’t continue to be.

It's really stable. That I can assure you. That is the one thing which I have to fight for with my managers because they ask why we should not move to a different solution. They said another solution is more stable. I told them that they are looking at the market analysis. We should test it ourselves. It's a really major banking project that we're working on.

Our solution has been around for several years now. It is FIDO certified. It has got compliance certification from the government, so it is very stable. The underpinnings of Samsung Pay deployed in South Korea. There are five and a half million consumers using that platform. That is one of the largest biometric deployments probably out there today. Then, we are a global organization, so we have deployments throughout the world and across different industries. 

This solution is very stable. Once you have the other patches applied it's really stable.

Layer7 is absolutely stable. It impresses me as a product because it never goes down. It always does what it is supposed to do.  

No issues with stability.

None.

Verbose logging in production has caused us a couple of issues, never enable this in production! In addition pay attention to name servers for DNS.

We are pretty happy with the stability. We had our challenges from the beginning, that’s part of the learning curve that we go through no matter what product we choose. But as we learned a little bit more about the product, and as we started leveraging the key features and the functionality of what it can bring to the table, I think we are pretty happy.

We've had no issues with stability.

It has been working quite well for a long time.

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.

It is pretty stable. We have not seen any issues, anywhere, where we need to restart.

API Management is highly reliable and highly available, so we haven't any problems with it.

Layer7 API Management is a highly stable solution.

We haven't encountered any issues with stability. The hardware and virtual appliance-based form factor are solid. It's a stable product.

So far stability is pretty good. We haven't experienced lag time or crashes.

No.

It's very good.

There were no stability issues. It is a very stable and mature product. So far, there have not been many complaints from clients regarding the stability.

It is a very resilient solution.

Regarding stability, we have not seen any issues as of now. It's a more stable product.

We are not in the production state at the moment so I cannot say anything about its stability.

We did not encounter any issues with stability.

It's stable, lightweight, works as expected and we don't see any problems with it.

If an entire cluster fails, we have disaster recovery with this solution. It provides an exact replica.

Because it contains Java, the heap memory needs to be cleaned constantly or problems will occur.

For day-to-day maintenance, two people are enough staff, e.g., checking the logs.

We have not had any issues with stability.

CA API Management solution is very stable also scalable.

We actually started with this product a few years back. It is definitely improved significantly since then. I think the amount of releases and bug fixes that they have pushed out have really helped.

We have never had any issues, to be frank. From the time that we had it installed we have never had any issues, whether in the non-prod or in production. So I would give it top rating from the stability point of view.

It is very good in terms of stability and functionality, it just lacks a little bit in terms of SOAP services.

Not yet.

There were no stability issues.

Stability-wise it's good. We are not really seeing any issues. We have had CA products for almost four years, and until now we haven't see any outage or any impact of the gateway.

From an API Portal 4.1 perspective, I did encounter multiple issues.

It's pretty stable. Once in a while we'll have an issue or we have to restart it but the product itself is very stable for us.

The stability of CA API Management is very good. We have very little problems with the solution. Just once, there were a couple of days that became filled up with logs of reporting information. Overall, CA API Management is certainly stable.

No issues with stability.

It's not stable. I want to publish new APIs with a socket, but it’s not stable enough for this. They need to fix this bug in order for it to be stable.

Lately, we have had a replication problem, but it's possible the problem is on our side. We are still unsure.