You can create a load balancing law to distribute traffic from the front to the back pool. Load Balancer uses a hashing algorithm to distribute incoming flow (not bytes). Upload balancer rewrites flow articles to reverse pool conditions. The server is available to receive the new flow when a health check indicates a healthy endpoint.
By default, the load balancer uses the hash Five Tuple.
The hash includes:
Source IP address
Location IP address
The number of the IP protocol to the map flows to the available servers
The proximity of the source IP address is created using two or three hashes. The same flow packets reach the same state after the expiration of the previous load measurement.
The source hole changes when the client starts a new flow from the same IP source. Because of this, a hash of five tuples may cause traffic to a different reverse destination. For more information, see Configure Load Balancer Distribution Mode.
The following image shows a hash-based distribution:
Application independence and transparency
Upload balancer does not directly associate with TCP or UDP, or application layer. Any TCP or UDP application status can be supported. The load balancer does not close or establish the flow or share the paid load flow. Upload balancer does not provide application gateway functionality. Protocol handshake occurs regularly between the client and the back-end pool stage. The response to the incoming flow is always the response from the visible machine. When the stream reaches the visible device, the actual source IP address is also saved.
- A VM turns on every endpoint. For example, a TCP handshake occurs between a client and a selected background VM. The response to the forward request is a response made by the background VM. When you successfully verify the connection in the front, you ensure the connection to every background device.
- The loading of the application is clear on the load balance. Any UDP or TCP system can be supported.
- Because the load balancer does not interact with TCP uploads and provides reduced TLS, you can create wider encrypted scenarios. Using the balancer load gains greater measurement of TLS applications by eliminating the TLS connection to the VM itself. For example, your TLS lock time is limited only by the type and number of VMs you add to the back storage pool.