liveBook · Manning

Load balancer

A load balancer is a hardware or software component that distributes incoming network traffic or requests among multiple servers, service instances, or endpoints.

How 3 Manning books explain it

Google Anthos in Action

A network load balancer is a Layer 4 load balancer that distributes TCP traffic using network-level forwarding and addresses.

How it is used
Exposes Kubernetes Services to external or VPC clients and provides reachable VIPs for hybrid-cluster traffic.
How deep it goes
Traces VIP-to-NodePort-to-Pod forwarding and details provisioning choices, address planning, and manual backend requirements.
Examples
Uses an annotated internal LoadBalancer Service, on-prem VIP planning, and a Seesaw creation command.
What you can do after
Operate/configure it by choosing internal, external, bundled, or manual deployment and preparing the required Service, VIP, and backends.

Read how Google Anthos in Action explains load balancer →

Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform

A load balancer is a network component that distributes incoming traffic across multiple service instances or endpoints.

How it is used
Exposes Kubernetes microservices externally while distributing requests across replicas for testing and production continuity.
How deep it goes
Explains request sharing, failover, and Kubernetes configuration, but defers detailed balancing algorithms and performance tuning.
Examples
Uses an Azure LoadBalancer Service, a video-streaming deployment, and three gateway replicas as concrete configurations.
What you can do after
Operate/configure a Kubernetes Service that exposes a microservice and routes traffic across replicated instances.

Read how Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform explains load balancer →

Spring Microservices in Action

A hardware or software component that distributes requests among multiple servers or service instances.

How it is used
Resolves service locations in traditional data centers by routing requests to hosted service instances.
How deep it goes
Traces DNS resolution, path-based routing-table lookup, server selection, forwarding, and standby failover.
Examples
Names F5 and HAProxy and describes a primary-secondary load-balancer pair.
What you can do after
Understand how DNS and path-based routing send service requests to one of several servers.

Read how Spring Microservices in Action explains load balancer →

Also covered in

What to know first

Related concepts

Questions about load balancer

What is load balancer?

A load balancer is a hardware or software component that distributes incoming network traffic or requests among multiple servers, service instances, or endpoints.

Which Manning books explain load balancer?

Google Anthos in Action, Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform and Spring Microservices in Action.

What should I know before learning load balancer?

Manning books that teach load balancer usually introduce domain name system, availability, HTTPS and IP address first.

What kinds of load balancer are there?

Kinds of load balancer include HAProxy.

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.