It scales well. I haven't found any inconsistencies between the data sheets and the hardware specs. For our purposes, we haven't run into any degraded performance or the like.

As I said, we don't use them for too much, just for load balancing and our 911 service. We have different internal switches that are connected to the A10 to load-balance the traffic, so we don't use the A10s 100 percent but between 20 and 50 percent for now. But as time goes by we are going to be using them more.

We currently have about 25 to 30 people who log into it to do provisioning on a daily basis. 

As for our plans to implement technologies or strategies in the next three years, we may look at moving from hardware appliances to software/scale-out solutions. Our company is always looking at new solutions to meet market needs. We will also look at multi-cloud failover, upgrading from TLS/SSL capabilities to modern PFS/ECC encryption standards, and moving applications to the public cloud.

I know that they are scalable, but we personally have never outgrown the boxes that we have. We've never really had to scale.

We definitely plan to increase usage. Today, A10 is used on a production website that gets hundreds of thousands of visits a week. I would expect an increase in the number of visits to the website, which is on the load balancing side. For the Carrier Grade Network, we are currently using it to net roughly 9500 users through the A10. So, we're doing CGN for 9500 people in all of our residences. That number is expected to double within the next five years.

We have about 20 to 25 people administrating or helping support it: network engineers, network architects, software engineers, security engineers, support staff, and web developers.

Scalability-wise, I rate the solution a seven out of ten because other vendors provide better LB and WAF features. So, the WAF features are not up to the mark in A10 Networks Thunder ADC.

It scales well. We are using the hardware appliance. For us to scale up, we buy new hardware. We always buy bigger than what we need so that way we can grow into it.

Internally, we have close to 600 people using it. Externally, we have 400,000 to 500,000 active members who pass data through the device. Typically, everything is web browsing or API calls.

We do not have plans to increase usage at this time, but with the cloud coming up, that is a possibility.

The product can scale. It's not an issue. 

Less than ten people are using the solution in our organization.

The solution is scalable by adding new appliances. 

Scalability for us is more horizontal, so it's easy for us to add nodes into the cluster. It's not really scaling vertically where we need more power. We're using the smaller devices; we don't use their chassis where you can add more power.

It is our only load balancing solution. We plan to transition into Azure, but we don't see a need, based on the way we use it, to grow it. It will just be transitioned.

A10 Networks Thunder ADC is scalable.

We have approximately a team of six using A10 Networks Thunder ADC.

I haven't needed to vertically scale beyond this box. It does scale horizontally.

The journey started with four servers and two websites and now I run close to 32 servers and service 36 applications, consisting of Web, application, and microservices. CPU utilization has moved marginally, by about three percent.

The scalability is appropriate.

It's moving along based on the business growth, so there are no plans to increase usage.

It's definitely scalable. We've not had any problems. I'm looking at the CPU graphs and it's not bothered at the moment.

The scalability depends on the resources you have. We do have resources so we are on the higher end in terms of what we bought, and we do have the scalability built-in. We are not using the virtual chassis. But if we want to expand it and have partitions created, to create a separate virtual chassis, we do have that scalability. If we need to add another appliance to it, the process is pretty simple. So it's scalable.

There are talks, internally, that all our applications should be behind ADC. As soon as we get to that level, even if it is just one server-application, the application will be behind ADC. Right now, we have our major enterprise applications, our major ERP systems, our email systems, and our tier-one applications behind ADC.

We never really tried to scale the internal initial deployment hands-on. It has been left as is. More users have been added over time but nothing so crazy that it really required some type of scaling of the product. This company is a little over a hundred users. They are all using it remotely, from home, daily.  

Roles for the users are just all over the board.  

It scaled well for our numbers, up to 3 million subscribers for our most crowded region.

The scalability is really good. You can easily unify many devices at once. ADCs are simple to configure and each device is powerful. We have two engineers managing and monitoring multiple systems and it works well for us.