Networking: Load Balancers Flashcards
Load Balancer: Backend pools
To distribute traffic, a back-end address pool contains the IP addresses of the virtual NICs that are connected to the load balancer
Internal Load Balancer:
is used where private IPs are needed at the frontend only. Internal load balancers are used to load balance traffic inside a virtual network. A load balancer frontend can be accessed from an on-premises network in a hybrid scenario.
Public Load Balancer:
Can provide outbound connections for virtual machines (VMs) inside your virtual network.
Public Load Balancers are used to load balance internet traffic to your VMs.
Maps the public IP address and port number of incoming traffic to the private IP address and port number of the VM.
Azure Load Balancer:
The load balancer distributes inbound traffic to backend resources using load-balancing rules and health probes.
Four components that must be configured for an Azure Load Balancer:
Frontend IP configuration, Backend pools, Health probes, and Load-balancing rules.
Load Balancer rules
A load balancer rule defines how traffic is distributed to the backend pool. The rule maps a given frontend IP and port combination to a set of backend IP addresses and port combination.
Azure Load Balancer: Session Persistence
Session persistence specifies how traffic from a client should be handled.
The default behavior (None) is that successive requests from a client may be handled by any virtual machine.
You can change this behavior.
Azure Load Balancer: Health Probes
A health probe allows the load balancer to monitor the status of your app.
It dynamically adds or removes VMs from the load balancer rotation based on their response to health checks.
When a probe fails to respond, the load balancer stops sending new connections to the unhealthy instances.
Azure Load Balancer: five-tuple hash
The hash is used to route traffic to healthy backend instances within the backend pool.
Source IP Source Port Destination IP Destination Port Protocol Type
Load Balancer SKU: # Backend Pool Instances
Basic- 300,
Standard - 1000 instances
Load Balancer SKUs: Health Probes
Basic- HTTP/TCP
Standard - HTTPS/HTTP/TCP
Load Balancer SKUs: Availability Zones
Basic - No
Standard - Zone Redundant and zonal front ends for inbound and outbound
Load Balancer SKUs: Multiple Front End restrictions
Basic - Inbound only
Standard - Inbound and Outbound
Load Balancer SKUs: Default Security
Basic - Open by Default
Standard - Closed to inbound flows
Load Balancer SKUs: SLA
Basic - None
Standard - 99.99%