How to Set Up Traffic Shadowing

Traffic Shadowing (Patent 09)—also known as Behavioral Mirroring—is the highest-integrity way to validate changes before they reach users. Unlike traditional staging, MicroStax uses a Shadow Multiplexer (Tee-Proxy) to duplicate live production traffic into a secure, isolated branch environment.

This allows you to test:

• Behavioral Drift: Does the new version respond differently than the baseline for the same payload?
• Performance Parity: Does a refactor introduce latency under real-world load?
• Regression Safety: Catch "black swan" edge cases that only exist in real traffic.

1. Prepare your Baseline

Traffic shadowing requires a stable Baseline environment to act as the traffic source.

microstax env promote production-cluster-01

2. Create a Branch Environment (Overlay)

Sprout a lightweight branch environment from your baseline. This "Sparse Overlay" only instantiates the services you’ve modified, while proxying everything else to the baseline.

microstax overlay create --baseline production-cluster-01 --file ./patch.yaml --name shadow-test

3. Activate the Shadow Multiplexer

Enable the Tee-Proxy to start mirroring incoming requests from the baseline to your branch.

microstax env shadow shadow-test --enable

[!TIP] Zero Risk: Shadowed traffic is "fire-and-forget." Any errors or performance issues in your branch environment cannot propagate back to production or affect the primary user journey.

4. Analyze Behavioral Diffs

Once traffic is flowing, MicroStax compares the responses from the Baseline and the Branch in real-time. Use the Behavioral Diff Engine to identify discrepancies:

microstax env diffs shadow-test

What to look for:

• Shape Discrepancies: Changes in JSON keys or nesting.
• Status Code Mismatches: e.g., Branch returns 500 while Baseline returns 200.
• Latency Spikes: Significant deviation in response times for the same request.

Next Steps

• Learn more about Branch Environments
• Explore AI-Powered Diagnostics
• View Full CLI Reference