Elastic Load Balancing is considered to be an important part of the Amazon Web Service since 2009 which was launched as the part of three-pack that consists of Amazon CloudWatch and Auto Scaling. After that, there have been many upgrades and features are added and also introduced the Application Load Balancer. Application Load Balancer is designed to support content-based routing to the application that operates in containers, Application-level, streaming, real-time workloads and Application load Balancers integrates well with microservices.
Customers are now using the Elastic Load Balancer to support application and website that operate on any scale for over the years. Simple Site runs on T2 instance or two, which stretches to the complex application that operates on the large fleets of high-end instances which handles large amounts of traffic.
Elastic Load Balancer monitors the traffic and automatically scales so that to meet the demand. This process will include a generous buffer of headroom that is more responsive and quicker over the years and works perfectly well even the customers use the Elastic Load Balancer to support live broadcasts holidays, “flash” and sales. In some situations such as extremely spiky workloads, instantaneous fail-over among the regions, AWS has worked with the customers to pre-provision Elastic Load Balancer in anticipation of the traffic surge.
New Network Load Balancer:-
The New Network Load Balancer is developed and designed in such a way that it can handle tens of millions of request per second and at the same time maintaining high throughput at the ultra-low latency with no need to do any configuration on your part. The Network Load Balancer is an Application Programming Interface compatible with the Application Load Balancer that consists of full programmatic control of the Targets and the Target Groups.
The Important features in the new Network Load Balancer are as follows:-
1. Static IP Addresses:
Each and Every Network Load Balancer will offer a single IP address for each Availability Zone in its own boundary. You can also choose an existing Elastic IP for each Availability Zone for greater control.
2. Zonality:
The IP address for per Availability Zone decreases the latency with improved availability and improved performance via isolation and fault tolerance that makes use of the Network Load Balancers transparent to the client applications. Network Load Balancer takes the effort to route a series of request from a specified source to targets in a single Availability Zone while still offering automatic failover for those targets should become unavailable.
3. Maintaining Source Address:
The Origin source IP address and source ports for the incoming connections remain unmodified with the new Network Load Balancer. With this, the application software will not require any support X-Forwarded-For, other workarounds, and proxy protocol. VPC Security Groups and the normal firewall rule can be utilized on the targets.
4. Long Connections:
Network Load Balancer manages the connections between built-in-fault tolerance and can manage the connection that is open for years or month by turning them into a great fit for gaming, messaging applications, and IoT.
5. Failover:
The new Network Load Balancer support failover between IP addresses across and within regions that is powered by Route 53 health checks.
Let’s learn as to how to Create a Network Load Balancer:-
1. Open the Amazon Elastic Compute Cloud Console by choosing the Load balancer and click on the Create Load Balancer. After doing this you have to enter the details by selecting the Elastic IP address for each subnet in the target Virtual Private Cloud and then tag the Network Load Balancer.
2. Now move on to Configure Routing and build a new target group. Enter the name and select the port and protocol. You can also set up the health checks that lead to the traffic port or the alternate choice of the user. After entering the details click on the Register Targets and the Elastic Cloud Compute instances that will receive the traffic and click on to add to register. Review the whole configuration and then click on Create.
3. You will then notice that the state of the new load balancer is provisioning by switching to active within some minutes. Simply select the DNS name of the Load Balancer from the console for the purpose of testing and then you can send a ton of traffic. You can use this tool Bees with Machine Guns for testing purpose.
Amazon Web Service Network Load Balancer is available in all the AWS commercial regions except China (Beijing).
No comments:
Post a Comment