Layer-7 load balancer
A layer-7 load balancer distributes and routes application-layer requests using information such as protocols, paths, hostnames, and request contents.
Google Anthos in Action
A layer 7 load balancer routes application traffic using information from protocols such as HTTP.
- How it is used
- Routes external HTTP(S) traffic into a GKE cluster through an Ingress.
- How deep it goes
- Contrasts layer-7 and layer-4 routing and provides Ingress configuration examples, without explaining load-balancer internals.
- Examples
- Uses an Ingress manifest mapping two hostnames to separate Services and ports.
- What you can do after
- Operate/configure HTTP(S) routing in GKE using a Kubernetes Ingress manifest.
Read how Google Anthos in Action explains layer-7 load balancer →
Kubernetes for Developers
A layer-7 load balancer distributes application-layer requests using information such as HTTP paths and hostnames.
- How it is used
- Routes HTTP traffic to multiple Kubernetes Services through one external IP, domain, or application entry point.
- How deep it goes
- Explains path and hostname routing, HTTPS termination, and Service requirements, but does not detail controller internals.
- Examples
- Demonstrates timeserver and robohash Services selected by URI paths or hostnames.
- What you can do after
- Operate/configure HTTP routing with Kubernetes Ingress manifests and inspect assigned addresses, backends, and health status.
Read how Kubernetes for Developers explains layer-7 load balancer →
What to know first
- HTTPHTTP is an application-layer protocol that defines request and response semantics for transferring representations and metadata between networked systems.
Related concepts
- Azure Application Gatewayincludes · Azure Application Gateway is a managed Azure application-delivery service that provides Layer 7 load balancing and HTTP-based routing to backend resources.
- Azure Front Doorincludes · Azure Front Door is a global Azure service for accelerating, routing, and load-balancing web application traffic across regions and origins.
- HTTPuses · HTTP is an application-layer protocol that defines request and response semantics for transferring representations and metadata between networked systems.
- NGINXincludes · NGINX is open-source web-server and reverse-proxy software that serves HTTP content, forwards requests, and can load-balance network traffic.
- L4 load balanceralternative to · An L4 load balancer distributes transport-layer connections among backend targets using information such as protocol, source and destination addresses, and ports.
- ingress objectimplemented by · A Kubernetes Ingress is an API resource that specifies rules for routing external HTTP and HTTPS requests to services within a cluster.
Questions about layer-7 load balancer
What is layer-7 load balancer?
A layer-7 load balancer distributes and routes application-layer requests using information such as protocols, paths, hostnames, and request contents.
Which Manning books explain layer-7 load balancer?
Google Anthos in Action and Kubernetes for Developers.
What should I know before learning layer-7 load balancer?
Manning books that teach layer-7 load balancer usually introduce HTTP first.
What is the difference between layer-7 load balancer and L4 load balancer?
A layer-7 load balancer distributes and routes application-layer requests using information such as protocols, paths, hostnames, and request contents. An L4 load balancer distributes transport-layer connections among backend targets using information such as protocol, source and destination addresses, and ports.
What kinds of layer-7 load balancer are there?
Kinds of layer-7 load balancer include Azure Application Gateway, Azure Front Door and NGINX.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.

