Traffic splitting
Traffic splitting is the distribution of requests among multiple backends, instances, or application versions according to configured proportions or relative weights.
Platform Engineering on Kubernetes
Percentage-based traffic splitting distributes requests among application versions according to configured traffic percentages.
- How it is used
- Supports canary releases by routing controlled portions of requests to stable and new service revisions.
- How deep it goes
- Explains configuration, validation, progressive rollout, rollback, scaling, and multi-revision percentage constraints.
- Examples
- Uses the notifications service, Knative YAML, kubectl edits, curl responses, and 50/50 revision traffic.
- What you can do after
- Apply it via Knative Service traffic rules, validate versions with curl, increase rollout percentages, or revert to the stable revision.
Read how Platform Engineering on Kubernetes explains traffic splitting →
Google Anthos in Action
Traffic splitting is the controlled distribution of requests among service versions or destinations according to configured proportions or rules.
- How it is used
- Controls service-version releases, A/B tests, canary deployments, and failure simulations within a service mesh.
- How deep it goes
- Explains percentage- and rule-based routing, progressive migration, and fault simulation but does not provide configuration syntax.
- Examples
- Uses an urgent microservice fix, percentage-based canary rollout, rule-based parallel versions, and fault-injection scenarios.
- What you can do after
- Operate progressive releases by directing, validating, increasing, and eventually migrating traffic between service versions.
Read how Google Anthos in Action explains traffic splitting →
Related concepts
- blue-green deploymentcontrasts with · Blue-green deployment is a release pattern that maintains separate active and replacement environments and switches traffic between them after the replacement is validated.
- weightconfigured by · A weight is a numerical quantity assigned to an element to represent its contribution, influence, importance, strength, or resource amount in a calculation or system.
- study designuses · Study design is the planned arrangement of procedures, conditions, measurements, and comparisons used to investigate a question and support valid conclusions.
- Knative Serviceuses · A Knative Service is a Kubernetes resource that defines and manages a serverless application’s deployment, revisions, traffic routing, and autoscaling.
- canary deploymentuses · A canary deployment is a release strategy that exposes a change to a limited portion of users, traffic, or infrastructure before expanding it more broadly.
- service meshused by · A service mesh is an infrastructure layer that manages communication and cross-cutting concerns such as traffic control, security, and observability between distributed services.
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.