The following explains the Azure Discussion Space and will discuss networking and the Azure Load Balancer (ALB).
What is the Azure Gateway Load Balancer?
The Gateway Load Balancer is just a high-end version of the Azure Load Balancer with third-party integrations and some advanced networking concepts. With the help of this, you can easily deploy and maintain network appliances in Azure. It just requires a click to enable a Gateway Load Balancer.
With this, you can easily add or remove network functionality. With this technology, you can easily route traffic to your appliance rather than directly moving traffic to your infrastructure.
It maintains flow stickiness for a specific instance in the backend pool along with flow symmetry.
What are the benefits of the Gateway Load Balancer?
You can easily integrate your virtual appliance with Azure and can scale it while maintaining the costs of interlink applications across various regions
It can be attached to a standard public load balancer. Once attached to it on a virtual machine, no additional configuration is needed to ensure traffic from the application endpoint.
Why do we use the Azure Gateway Load Balancer?
The Gateway Load Balancer easily helps you to deploy, scale, and integrate your third-party network virtual appliance. It gives you one gateway for distributing traffic across multiple virtual appliances while scaling them up or down based on demand.
You can use your appliances in a different scenario, such as in Firewall IDPS Traffic monitoring and mirroring also help with DDOS attacks on custom appliances across your network.
What are the updates related to the Gateway Load Balancer?
The Gateway load balancer borrows a majority of the same concepts as the standard load balancers that customers are familiar with today. As you can compare the components like frontend IPs, load balancing rules, backend pools, health probes, and metrics, here you will get to see a new component unique to the load balancer, i.e., VXLAN tunnel interfaces.
It is an encapsulation protocol utilized by GWLB. This allows encapsulation and decapsulation with the help of its headers as they provide the appropriate data path, all while maintaining their source IP and also a component known as flow symmetry, which does not require SNAT or other things like user-defined routes (UDRs).
The VXLAN tunnel interfaces are configured as part of the Load Balancers' back-end pool and enable the network virtual appliances to isolate "untrusted" traffic from "trusted" traffic.
Tunnel interfaces can either be internal or external, and each backend pool can have up to two tunnel interfaces.
Typically, this ex-traffic is used for "untrusted" traffic—traffic coming from the internet and headed to the appliance. Correspondingly, the internal interface is used for "trusted" traffic—traffic going from your appliances to your application.
They are now generally available in all regions, and you can have a try in the China region also.
Comments