Senior Consultant at a tech services company with 11-50 employees
Real User
Sep 13, 2022
Due to the high price-point of this solution we would suggest this product is better suited to larger organizations with a larger budget. I would rate this solution a seven out of ten.
I think most people use NGINX. It's pretty much open-source and there is no cost barrier. But for the enterprise edition, it's another story. If you already have experiences in NGINX, you can probably easily configure it onto the lightning ADC controller. It's a good IT solution. I think it requires a license to integrate it with other things. Most of the people that I see here in Pakistan, in the industry, use NGINX on the front-end. Lightning ADC is pretty much for clients not residing in Pakistan, but residing in America — the licensing is not cheap. On a scale from one to ten, I would give Lightning ADC a rating of seven. Kubernetes' environment is not simple. I used it in the last company that I worked for and it could be a real mess if there were issues during production. If you don't have the right set of tools, it can be really problematic for whoever is managing the cluster. The spike would occur at roughly 2 am when everybody's sleeping. We would get a few alerts and then the application would crash because the containers were dead or something really weird happened. After a while, you start to realize what the problem is. You start looking at the NGINX side: how many client connections are there? What is happening with the traffic that is being brought in from the front-end towards the Kubernetes side? How is the traffic getting to the ports? Watching YouTube videos and demos can be a big help. They can give you a better picture of what is happening from the front-end to the back-end. It might also help to slow down the video to help you with problems you may encounter at various points with the application. The problem happens in the production environment. If the application chokes or there's a really bad bottleneck that occurs, it's going to be really hard to fix. The easiest way that people seem to resolve this issue is by restarting the port — restarting everything and giving the application some downtime. The problem is, once the application has some downtime, the findings are affected. These issues could be reduced with the help of some simple videos and demos. If they incorporated some, it would be a huge improvement and I would give them a higher rating.
Find out what your peers are saying about A10 Networks, NetScaler, Progress Software and others in Application Delivery Controllers (ADC). Updated: December 2025.
Application Delivery Controllers enhance application performance and availability. They efficiently manage data traffic, improving the distribution of network resources and optimizing web applications critical for business operations.Application Delivery Controllers serve as an integral component in a network infrastructure, providing distribution of traffic across multiple servers. They ensure high availability, improve performance, and provide capabilities like SSL offload, Web Application...
I would rate it an eight. It has performed well in most areas and meets our requirements effectively.
Due to the high price-point of this solution we would suggest this product is better suited to larger organizations with a larger budget. I would rate this solution a seven out of ten.
I think most people use NGINX. It's pretty much open-source and there is no cost barrier. But for the enterprise edition, it's another story. If you already have experiences in NGINX, you can probably easily configure it onto the lightning ADC controller. It's a good IT solution. I think it requires a license to integrate it with other things. Most of the people that I see here in Pakistan, in the industry, use NGINX on the front-end. Lightning ADC is pretty much for clients not residing in Pakistan, but residing in America — the licensing is not cheap. On a scale from one to ten, I would give Lightning ADC a rating of seven. Kubernetes' environment is not simple. I used it in the last company that I worked for and it could be a real mess if there were issues during production. If you don't have the right set of tools, it can be really problematic for whoever is managing the cluster. The spike would occur at roughly 2 am when everybody's sleeping. We would get a few alerts and then the application would crash because the containers were dead or something really weird happened. After a while, you start to realize what the problem is. You start looking at the NGINX side: how many client connections are there? What is happening with the traffic that is being brought in from the front-end towards the Kubernetes side? How is the traffic getting to the ports? Watching YouTube videos and demos can be a big help. They can give you a better picture of what is happening from the front-end to the back-end. It might also help to slow down the video to help you with problems you may encounter at various points with the application. The problem happens in the production environment. If the application chokes or there's a really bad bottleneck that occurs, it's going to be really hard to fix. The easiest way that people seem to resolve this issue is by restarting the port — restarting everything and giving the application some downtime. The problem is, once the application has some downtime, the findings are affected. These issues could be reduced with the help of some simple videos and demos. If they incorporated some, it would be a huge improvement and I would give them a higher rating.