Skip to main content
TrustRadius
Elastic Load Balancing

Elastic Load Balancing

Overview

What is Elastic Load Balancing?

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…

Read more
Recent Reviews
Read all reviews
Return to navigation

Pricing

View all pricing

Gateway

$0.0125

Cloud
Partial Hour

Application

$0.0225

Cloud
Partial Hour

Network

$0.025

Cloud
Partial Hour

Entry-level set up fee?

  • No setup fee

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services
Return to navigation

Product Details

What is Elastic Load Balancing?

Elastic Load Balancing Technical Details

Deployment TypesSoftware as a Service (SaaS), Cloud, or Web-Based
Operating SystemsUnspecified
Mobile ApplicationNo
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(14)

Attribute Ratings

Reviews

(1-2 of 2)
Companies can't remove reviews or game the system. Here's why
Score 9 out of 10
Vetted Review
Verified User
Incentivized
At the moment we are looking at using the elastic load balancer provided by Amazon web services in a trial fashion. Our company has been migrating more and more of our in-house developed applications from on-site platforms to the AWS web platform. Part of this involves routing traffic across the newly deployed microservices and we are looking into using the elastic load balancer to help with this. So far it seems promising although our scale is admittedly low. We have not yet decided to migrate everything over to elb from our previous setup however results are promising as with anything else on the AWS suite the more we use it the more we like it. As far as business problems being addressed it's simply a matter of the security of being the host of the cloud versus having to maintain everything on site and as such the more options we use provided by Amazon web services the less we have to do ourselves.
  • Most obviously it works great for routing traffic between components hosted on Amazon web services
  • The ability to dynamically spin up connections is fantastic.
  • In general the ease of use and configuration is a selling point.
  • So far our experience has been limited with the ability for elb to handle transactions when only part of the platform is on Amazon web services.
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.
  • Dynamically spitting off new connections as back end or front end services are spun up
  • Ease of integration within the AWS platform
  • The pay as you need the mentality of AWS in general and in specific with the elb is a wonderful benefit
  • Currently it is too soon to say for sure what kind of impact this will have.
  • The ideal goal is that this will be cheaper than having to host our own routing on site.
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 routing traffic across various applications hosted in the cloud.
Score 8 out of 10
Vetted Review
Verified User
Incentivized
We are using Amazon Elastic Load Balancing for our digital learning platform, as part of our suite of AWS products, in order to keep abreast of the stress on our various network targets and make sure the loads between them remain balanced. We also use it to troubleshoot slowdowns or bottlenecks in the network by running the diagnostics that Amazon Elastic Load Balancing provides.
  • I like being able to check the status of the load on any of our targets, in real time
  • It is helpful to be able to run diagnostics when we have slowdowns in the network
  • Amazon Elastic Load Balancing integrates well with the other AWS products we are using
  • Occasionally we have a huge number of users using our network at once, and Amazon ELB isn't quite fast enough to scale effectively when that occurs. But this doesn't happen very often as our usage is usually quite stable
  • If we want to add another application to our learning suite, we would have to add another load balancer, which would incur additional cost
  • The setup was not easy and could really only be handled by one person on our team with the technical background to do so
Amazon Elastic Load Balancing is great if you are already using a lot of other Amazon Web Services applications. It is built to integrate well with those, so your implementation will go a lot smoother. If you're already using other cloud computing services from different companies, you will have a much slower and more difficult time with integrating Amazon Elastic Load Balancing into your suite of applications.
  • Integration with other AWS applications
  • Ability to run diagnostics on network slowdowns or bottlenecks
  • Customization of notifications so we can tell when the network is having issues based on our own benchmarks
  • Allows us to troubleshoot and address network issues, which improves our end user experience
  • Provides an integrated way to balance our network load without having to deal with other suites besides AWS, saving time and effort
  • Allows us to see the effects that different code changes have on our network performance, which means more efficient development on the back end
Return to navigation