Elastic Load Balancing Reviews & Insights

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.

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.

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.

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.

We use the Amazon Elastic Load Balancing as a single entry point for end-clients or end-users of the EC2 instances to distribute incoming traffic across all machines available in the different availability zones to receive requests. We use it across all applications we deploy to the different environments. It fits well with the security groups and auto-scaling settings.

We use Amazon Elastic Load Balancers to serve mobile applications and websites. It works really well. We have not had any problems until now. Last year we integrated the AWS ELB with the EC2 Auto Scaling and now we have a fully working elastic solution. We increase/decrease EC2s instances based on traffic over our load balancers.

We decided to use Amazon Elastic Load Balancing in conjunction with Amazon EC2 Auto Scaling to host our websites. We have websites that have peak traffic on some periods of the year, so we needed an elastic infrastructure that helps us to serve our websites with no downtimes and good performance. And that's what we get using this platform. So, we now have more reliable websites.

We use AWS Elastic Load Balancers to serve websites. And for this purpose, works extremely well. In the past we used physical load balancers and that was very costly, and not to mention hard to work with on the server content replication side. Now, with AWS Elastic Load Balancers and EC2 Auto Scaling, we have a complete elastic solution, that works as it's supposed to be.