Application Gateway
- Web traffic LB to distribute traffic to web applications
- Web Apps can reside in VM, VMSS or on-premise servers
- The
Application Gatewayis anOSI Layer 7 LB(At this layer the info is understandable, e.g., the path) - Support for
Secure Sockets Layer(SSL/TLS) Autoscalingcan be enabled for the AGWeb Application Firewallcan be enabled for the AGSession Afinitycan be enabled'- An
empty subnetis necessary for the AG
Components
Frontend IP: access to the gatewayListener: Logical entity that checks for incomings requests. There can be multiple listenersBasic listener: listen to a single domain siteMulti-site: listen and map to multiple domain sitesRouting rules: Route traffic from the listener to the backend poolBasic routing rule: all requests to to the backend pool directlyPath-based routing rule: requests are routed based on the URL of requestBackend pools: NICs, VMSS, Public IP, Internal IP, SQDN, etcHealth probes: Defines how the AG will monitor health of the resources in backend pool
Application Gateway vs. Load Balancer
-
Load Balancer
-
Simply redirects traffic to backend pool (machines)
-
LB 4
-
Application Gateway
-
Redirects traffic to a specific backend pool based on
routing rules(E.g., the path of the request /images, /videos) - LB 7

OSI Model
- Physical
- Data Link
- Network
- Transport
- Session
- Presentation
- Application
