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.