Shulou(Shulou.com)06/03 Report--

The knowledge points of this article include: the difference between Standard Load Balancer and Basic Load Balancer, as well as the advantages and simple use of Standard LB. I believe you have a certain understanding of Standard Load Balancer after reading the complete article.

Azure's load balancer is a very basic component, and the LB function of each cloud is actually different. The layer 4 LB of Azure is relatively basic, but the advantage is that this thing is free, but Azure actually came out with another kind of LB later, so there are actually two kinds of layer 4 LB of Azure.

1. Basic LB

2. Standard LB

Basic LB will not say much, Standard LB is equivalent to an advanced product, compared with Basic LB will be more powerful, but at the same time there are some limitations, you can use the following table to understand the difference between Standard LB and Basic LB

Standard SKU

The basic SKU backend pool size supports up to 1000 instances of any virtual machine in a single virtual network of backend pool endpoints, including a mix of virtual machines, availability sets, and virtual machine size sets. A virtual machine with a single availability set or virtual machine size set. Health probe TCP, HTTP, HTTPSTCP, HTTP Health probe stop behavior TCP connection remains active when instance probe stops and all probes stop TCP connection remains active when instance probe stops. All TCP connections terminate diagnostic Azure Monitor, multidimensional metrics (including byte and packet counters), health probe status, outbound connection health (SNAT success and failure flows) unavailable HA ports Internal load balancer (internal load balancer) not available default protection public IP, common load balancer endpoints, internal load balancer endpoints block inbound traffic Unless the inbound flow is on the allow list by default by a network security group, the network security group can select an outbound connection that can explicitly define a pool-based outbound NAT using outbound rules. Multiple frontend can be used when each load balancing rule chooses to exit. _ must _ explicitly create an outbound scheme for virtual machines, availability sets, and virtual machine size sets to use outbound connections. The virtual network service endpoint can be accessed without defining an outbound connection and does not count the processed data. Any public IP address (including Azure PaaS services that are not provided as VNet service endpoints) must be accessed through an outbound connection and be counted as processed data. If only one internal load balancer serves virtual machines, availability sets, or virtual machine size sets, outbound connections via the default SNAT will not be available, so use outbound rules instead. Outbound SNAT programming is specific to the transport protocol and is based on the protocol of inbound load balancing rules. A single front end is randomly selected when there are multiple front ends. If only internal load balancers serve virtual machines, availability sets, or virtual machine size sets, the default SNAT is used. Outbound rules use public IP addresses or public IP prefixes or both, Declarative outbound NAT configuration that can be configured for outbound idle timeout (4-120min) or custom SNAT port assignment is not available when idle TCP is enabled for any rule idle timeout reset TCP (TCP RST) unavailable multiple front-end inbound and outbound only inbound management operations most operations are less than 30 seconds usually 60-90 seconds SLA has a data path of 99.99% to two running virtual machines. Not applicable pricing is free of charge based on the number of rules, the amount of data associated with the resource and processed inbound and outbound

Let's summarize some of the advantages of Standard LB:

1. Internal LB HA port rules that provide scaling and resilience for network virtual devices and other scenarios

two。 Integrated monitoring (traffic counters, health probes, TCP connection attempts, outbound connections) and continuous data plane health metrics

3. Larger backend pool capacity

4. Can support HTTPS probe

5. Feel free to add VM without the need for VM to be in the same availability set

But at the same time, Standard LB has some disadvantages:

1. Basic LB is free, but Standard LB is charged.

2. VM of Standard LB backend cannot be SNAT to Internet by default

3. Basic Public IP cannot be mounted to Standard LB

Generally speaking, Standard LB certainly has its advantages, but some basic scenarios can actually consider using Basic LB. In fact, they are not a complete substitute, and both sides have some usage scenarios.

Here are some examples of the advantages of Standard LB over Basic LB

1. Probe supports HTTPS

two。 The backend pool does not need to be limited to the same availability set, so you don't have to worry about it in the future.

After reading the above, do you have any further understanding of Azure Standard Load Balancer? If you want to learn more skills or want to know more about it, you are welcome to follow the industry information channel. Thank you for reading.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.