My main use case for A10 Networks Thunder ADC is web application load balancing. If I have multiple web servers hosting the same application, I perform load balancing. I do SSL offloading for HTTPS encryption, which can be CPU-intensive. I use it for high availability, global server load balancing, DDoS protection, API gateway, microservices, Kubernetes Ingress, telecom 5G networks, active-active data center design, multi-cloud traffic steering, and similar applications.

I use load balancing extensively with A10 Networks Thunder ADC. For example, with A10 Networks Thunder ADC load balancing, the requests are distributed. If a server fails, the health check detects the failure. There are different kinds of load balancing, including round-robin, least connections, and weighted load balancing. There is also layer four versus layer seven load balancing. In a real enterprise example, such as a banking application, the customers might go to A10 Networks Thunder ADC and then be directed to a login application, payment application, or API application. A10 Networks Thunder ADC responsibilities include SSL termination, session persistence, DDoS filtering, health monitoring, and traffic routing.

Mostly, I use A10 Networks Thunder ADC with load balancing and also in a data center. I need an active-active data center design and also use it for security for DDoS protection.

My main use case for A10 Networks Thunder ADC is to ensure application delivery, security, and high availability.

One specific example of how I use A10 Networks Thunder ADC for application delivery and security in my environment is by using it for load balancing a public e-commerce website. A10 Networks Thunder ADC helps with load balancing on my public e-commerce site by ensuring this is critical for maintaining uptime and handling traffic spikes without impacting the customer experience.

I have another important use case for A10 Networks Thunder ADC, which is carrier-grade NAT or CGNAT. I use CGNAT with A10 Networks Thunder ADC for protection from DDoS attacks.

A10 Networks Thunder ADC is typically used for Global Server Load Balancing (GSLB) related use cases.

I primarily use A10 Networks Thunder ADC for load balancing and application delivery across my production environments, sitting in front of my critical web and API services that help solve problems by distributing traffic efficiently and maintaining uptime during peak loads. A significant part of the use case is ensuring high availability and minimizing downtime during maintenance or unexpected spikes whenever there is more traffic or a network issue. One of the main cases is also a combination of application delivery and basic security handling, using A10 Networks Thunder ADC to manage traffic across multiple application servers while leveraging features such as DDoS protection and SSL offloading. Whenever major traffic occurs, I use this to run it efficiently in a hybrid environment where some workloads are on-premises and others are in the cloud.

I use A10 Networks Thunder ADC mainly in front of my e-commerce platform that I have built for a client, and during seasonal sales, I saw traffic spikes at around three to four times the normal load that I was receiving on that site. A10 Networks Thunder ADC distributes the traffic across multiple backend servers and handles SSL offloading, which keeps response times stable, and without it, my app servers would have become overwhelmed very quickly.

A10 Networks Thunder ADC fits quite seamlessly into my overall workflow, and once it is set up, it became more of a set-it-and-monitor-it, autopilot mode component rather than something I constantly have to tweak. Most of my interaction is around policy updates or scaling decisions rather than day-to-day firefighting and working hard, shifting me to working smartly rather than hard.

A10 Networks Thunder ADC is primarily used in our environment for application delivery and traffic management of enterprise applications. We use it mainly for load balancing, improving application availability, SSL offloading, and ensuring reliable traffic distribution across back-end services.

We have onboarded enterprise applications using A10 Networks Thunder ADC primarily for load balancing and improving application stability and availability. We use the ADC product for SSL offloading and renewing SSL certificates, ensuring centralized SSL certificates so that we do not miss any SSL certificate expiration.

We use the solution for ProTechVIP, the software, the client, the servers, and the firewalls. We mix them, protecting the connection and the servers from direct access.

We use the solution for load balancing purposes.

A10 Networks Thunder ADC can be deployed on-premise or virtually.

A10 Networks Thunder ADC is used for global load balancing.

Our primary use case is load balancing, from Layer 4 to Layer 7, on different partitions. And it's also our internet gateway router with our ISP. We're using the standard DDoS protection which is on the box itself.

We have about 91 virtual IP addresses we're load balancing at the moment.

Our company uses A10 Networks Thunder ADC for its load balancing capabilities.

Our company uses the solution to enhance our client's connection to their data centers. One data center is in Brasilia and the other is in Sao Paulo. The solution bolsters the connection between the data centers.  

Our clients are using it for their entire network. They have multiple networks across India. They are using it for application load balancing. 

They have multiple servers. 

We are in the government sector and we use this solution for load balancing and application management.

Our primary use case is for servicing a remote workforce. Especially these days when a lot of people are working remotely, a solution like this is important. We have to deploy applications and we do not necessarily want to upload the applications into the cloud or locally on desktops or laptops. ADC is really good for desktop virtualization and application delivery. Instead of having a full client, you look at a projection hosted in the data center. All the processing is being done back in the data center in the corporate domain. Because of the fact that the processing is not being taken care of locally, ADC is a very lightweight client that handles the feed on your laptop. It also enhances security.  

Everything is kept in the server room, not exported locally to someone's house or whatever location they are working in. You do not have to worry about securing the data. There are certain programs that you have to patch a lot, like Adobe Flash — which seems to always need a patch. Instead of doing that on all 100 laptops that are in the field, you just do it once in the data center and everybody uses that same version. That type of simplification for your deployments is another benefit of ADC.  

Because the maintenance is all happening at the data center, it is a lot more controlled and it is way easier. Another thing that this helps with is that only certain people get access to certain applications. The accountants are really the only ones who need access to the accounting software. It is really easy to set up groups based upon Active Directory and then define who gets access to those applications. That ability to limit access is really kind of cool and can potentially save money and licensing costs.  

Our primary use case is the application delivery controller part where we mainly use the server load balancing features to front-end our back-end servers to give us additional high availability, some resiliency, and some failures.

All our applications are hosted on a private on-premises data center. We run our own data center with VMware being the main virtualization platform. Then, running on top of VMware, we have Windows and Linux clusters, so x86 Windows and x86 Linux.

Our biggest security concerns are malicious code, user data theft, DDoS attacks, insider attacks, brand damage/loss of confidence, and phishing/fake sites. Hacking/cyber defacement is one of our concerns, but not the biggest. A lot of these security concerns are around data loss and data loss prevention. We are a pension institution, so we do not want to lose any of our member data. We have security things in place using the application firewalls, as an example, to help with our front-end sites. 

We are running virtual machines and currently doing a proof of concept with containers. However, we're not working with containers on-prem yet.

The A10s that we have in Florida are being used for load balancing. We have a pair of A10s there, an active and a standby, and we are balancing the traffic between. We also use our A10s, in general, for provisioning wireless products. Eventually, we will use our new A10s for more stuff.

Our applications are hosted in a private on-premises data center, on public cloud in AWS, and in a hybrid cloud which is primarily public infrastructure.

Among our biggest security concerns are malicious code and DDoS attacks.

We use it for SLB and GSLB load balancing. We're using the Thunder ADC 1040 but before that we used their AX 2500.

We are using ADC for load balancing. Most of our enterprise applications are behind ADC.

It's on-premise.

• Load balance web traffic
• Load balance application traffic
• DDoS protection
• Carrier Grade Network (CGN)

We have the ADC product, as well as the CGN.

We are using both the public and private deployment model. We are using AWS as our cloud provider.

We use A10 Networks Thunder ADC for the application delivery controller. 

We are distributors and have been for a long time. We provide products to clients.

We use it to load-balance the website.

My primary use case is to use it as a software load balancer. 

Because of the industry that we operate in, we cannot use cloud. Therefore, we use it on-premise. We have 32 medium boxes, and that's what runs production.

The primary use case is server load balancing.

We use the on-premise deployment model.

Carrier-grade NAT is the purpose of using A10 Networks Thunder ADC at Turk Telekom Mobile.