Staging can promise a safe rehearsal yet diverge from production: data, infrastructure size, and real traffic are hard to match. Production testing uses the live environment as a final validation loop, where software encounters actual system conditions. section 13.7
The tradeoff is exposure. Programmable routing controls—including dark launching, inversion feature flags, and canary proxies—can put code on live servers while limiting which users see it. If failures can be isolated to a small share of users within milliseconds, production may serve as the final checkpoint. section 13.7.1
Use this decision rule:
- Keep a physical staging gate when compliance, data privacy, or observability maturity cannot support real-time control of the blast radius. section 13.7.1
- Consider production the final validation loop when traffic controls can quickly confine failures to a small group of users. section 13.7.1
Figure 13.11 The Staging Dilemma: Traditional staging often promises perfect parity, but in reality, it frequently drifts from production, offering a false sense of security.

The staging dilemma illustrates how a nominally production-like environment can drift and offer false confidence. section 13.7

