liveBook · Manning

Shadow testing

As explained in The Coder Cafe

Shadow testing runs a change in parallel with production traffic while preventing it from affecting real users.

Shadow testing runs a change in parallel with production traffic while preventing it from affecting real users. It validates correctness before the change is enabled. section 6.14.2

Use shadow testing as part of a controlled rollout:

  • Run the proposed change alongside live production traffic without exposing its effects to users. section 6.14.2
  • Validate the change before enabling it, reducing the blast radius of failures and increasing confidence during iteration. section 6.14.2
  • Contrast it with feature flags, canary releases, and progressive rollouts, which control exposure differently. section 6.14.2

Production validation

A new change processes production traffic in parallel, but its output cannot affect real users. The results provide a correctness check before activation. section 6.14.2

How The Coder Cafe covers it

How deep it goes
Defines parallel execution and safe validation but stops short of implementation details or operational procedures.
Examples
Uses a proposed change processing production traffic in parallel without affecting real users.
What you can do after
Evaluate a change’s correctness before enabling it for real users.
How it connects
Connects shadow testing with feature flags, canary releases, progressive rollouts, observability, and controlled rollouts.

Also explained in

Compare how 3 books explain shadow testing →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of The Coder Cafe. The section links point to the parts of the book it draws on.