Service discovery is not new. The idea of a tool that can discover how processes and services talk to each other and help facilitate connections has been around for some time. However, with the rise of increasingly dynamic environments, the important role service discovery plays continues to grow. Indeed, since the beginning of the year at Flux7 we have seen a surge of customers looking for container-based microservices architectures that highlights the need for service discovery due to its dynamic nature.
Just last month we wrote about Docker upping the security ante with a number of new security controls built into Docker 1.10 and here we are yet again. Dockercon 16 is coming up fast - June 19-21, 2016 in Seattle - and we're looking forward to sharing the Dockercon stage for second time with a customer - Fugro this time - to talk about how enterprises can use Docker and AWS to address common challenges. Check out the speaker list here.
Amazon Web Service (AWS) Elastic Load Balancing (ELB) is widely used to build highly available and highly scalable architectures. Nowadays, ELB is as common as EC2 is for many customers using AWS. And, Elastic Load Balancing supports the following protocols: HTTP, HTTPs, TCP and TCPs.
This is part 1 of the AWS Autoscaling Tutorial for LAMP in AWS series. This AWS autoscaling step-by-step guide would walk you through:
AWS Elastic Load Balancing automatically distributes incoming application traffic across multiple Amazon EC2 instances. It helps to achieve better fault tolerance in applications by seamlessly providing the amount of load balancing capacity needed in response to incoming application traffic.
Based on the incoming application traffic, Elastic Load Balancing automatically distributes traffic across EC2 instances. Elastic Load Balancing detects unhealthy instances and moves traffic to healthy instances till the unhealthy instances are restored back.