liveBook · Manning

Traffic management

Traffic management is the coordinated control, routing, distribution, or shaping of moving flows through a system.

How 2 Manning books explain it

Google Anthos in Action

Traffic management is the control of how network requests are routed, distributed, delayed, or faulted across service instances and application versions.

How it is used
Controls microservice ingress, egress, version routing, progressive migration, and resilience testing within a service mesh.
How deep it goes
Explains traffic features and sidecar mechanics, but stops short of detailed configuration commands or troubleshooting procedures.
Examples
Uses version-based routing, single-user delivery, gradual migration, HTTP delays, and injected status-code faults as operating examples.
What you can do after
Apply it via Istio to route versions, split traffic, expose services, control egress, and test failure responses without application code changes.

Read how Google Anthos in Action explains traffic management →

Platform Engineering on Kubernetes

Traffic management is the controlled routing and distribution of requests among application versions or service instances.

How it is used
Supports safer release strategies by directing selected or copied requests to application canaries.
How deep it goes
Explains percentage, header, and mirrored routing, but defers detailed Istio Virtual Service configuration.
Examples
Demonstrates a 25% canary weight, 35% mirrored GET traffic, a ten-minute pause, and subsequent mirror-route removal.
What you can do after
Apply it via Argo Rollouts and Istio to test canaries with targeted, weighted, or mirrored requests.

Read how Platform Engineering on Kubernetes explains traffic management →

Related concepts

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.