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.