Design and implement Azure load balancer using the Azure portal - Training
learn.microsoft.com/en-gb/training/modules/load-balancing-non-https-traffic-azure/3-design-implement-azure-load-balancer-using-azure-portal
1 Users
0 Comments
92 Highlights
2 Notes
Tags
Top Highlights
use a single DNS name.
You can choose None, or Client IP, or Client IP and protocol
l for the duration of a session.
Azure Load Balancer operates at layer 4
of the Open Systems Interconnection (OSI) model
It's the single point of contact for clients. Azure Load Balancer distributes inbound flows that arrive at the load balancer's front end to backend pool instances.
A public load balancer can provide outbound connections for virtual machines (VMs) inside your virtual network.
translating their private IP addresses to public IP addresses.
External load balancers
An internal load balancer is used where private IPs are needed at the frontend only
Internal load balancers are used to load balance traffic from internal Azure resources to other Azure resources inside a virtual network
from an on-premises network
fall into three categories:
Azure services that support availability zones
Zonal services:
Zone-redundant services:
Non-regional services:
Resources can be pinned to a specific zone.
across three zones so that a zone failure does not impact its availability.
are always available from Azure geographies and are resilient to zone-wide outages
Ready to highlight and find good content?
Glasp is a social web highlighter that people can highlight and organize quotes and thoughts from the web, and access other like-minded people’s learning.