A10 Networks offers their application delivery controller, Thunder ADC.
N/A
Elastic Load Balancing
Score 6.6 out of 10
N/A
Amazon's Elastic Load Balancing automatically distributes incoming application traffic across multiple targets, such as Amazon EC2 instances, containers, IP addresses, and Lambda functions. It can handle the varying load of your application traffic in a single Availability Zone or across multiple Availability Zones. Elastic Load Balancing offers three types of load balancers with the vendor states all feature the high availability, automatic scaling, and robust security necessary to make…
$0.01
Partial Hour
Pricing
A10 Thunder ADC
Amazon Elastic Load Balancing
Editions & Modules
No answers on this topic
Gateway
$0.0125
Partial Hour
Application
$0.0225
Partial Hour
Network
$0.025
Partial Hour
Offerings
Pricing Offerings
A10 Thunder ADC
Elastic Load Balancing
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
A10 Thunder ADC
Amazon Elastic Load Balancing
Considered Both Products
A10 Thunder ADC
No answer on this topic
Elastic Load Balancing
Verified User
Anonymous
Chose Elastic Load Balancing
Again as noted we're still in the trial process seeing if we want to migrate over but the biggest benefit of elb is its interconnectivity with other Amazon web services hosted applications that our company is using and the in-house support from AWS. This is very attractive when …
We have not used any other solution out there in the market but our dev-ops team did deep research and AWS provided us the solution we needed to be cost-effective. Also, the decision to keep working with Amazon was strategic. We were already using other AWS features and [Amazon …
In the past we use physical Load Balancers. That solution works, but it had several negative points. The first, it was not elastic. It requires a physical server setup in order to work. Also a technician works for one or more days to set up the solution. And then, we had the …
It really is a straight-up situation. From my current experience if you have two or more services hosted on Amazon web services that need transactions between each other with a variable flow of traffic then elb is a fantastic method for routing that traffic and making sure that no one back and component gets overloaded with requests while other existing components are just standing there idle waiting for some traffic. As noted earlier in my review we are still doing a trial run with the service as not all of our components are hosted on AWS yet and we aren't having as great luck with transactions between hosted and non-hosted but that could also simply be a learning curve on our part.
AWS Elastic Load Balancing has this trick. First, you need to know how it works. ELB is not the only piece here. ELB has a very close relation with AWS Target Groups. You create or select a target group every time you create a Load balancer. Target groups allow you to connect the load balancer to EC2 autoscaling groups, Lambda functions, or even a single EC2 instance. While this sounds complex, it becomes easy, once you know his tricks. Thanks to the user interface, managing a ELB is an easy task. The rules editor is really useful, although it will need a bit of improvement to some interface items
Support said the devices will work in our environment but when we had the device working we realized that it was not possible to do what we wanted, for this reason, our experience was not entirely good and we did not like the way they approached us for the sale of the device.
AWS gives you several support plans. On the free plan, you basicaly need to google for help, but the good news is that AWS Elastic Load Balancing works. We has more than 15 load balancers and we never run into a problem that require support. But you mght consider a support plan if you are going to do something more complex or critical
We have not used any other solution out there in the market but our dev-ops team did deep research and AWS provided us the solution we needed to be cost-effective. Also, the decision to keep working with Amazon was strategic. We were already using other AWS features and [Amazon Elastic Load Balancing] integrates great with those.
A10 Thunder ADC had a negative impact on the company, due to the fact that the client had to monitor a large number of sites, which could not be achieved with this device.
This led to looking for another alternative.
It is more beneficial for companies that do not need to monitor a large number of websites as the security and stability provided by the device are excellent.
