コンテンツへスキップ
LatchkeyLatchkey home

Traffic Mirroring とは?

traffic mirroring はシャドウイングとも呼ばれ、本番の実リクエストを複製し、そのコピーをサービスの別バージョンへ転送する一方で、プライマリは実際のレスポンスを処理し続けます。ミラーされたレスポンスは破棄されるため、ユーザーは影響を受けません。これにより、誰かに提供する前に、新しい build を現実的な負荷で動かせます。

なぜ重要か

mirroring は、deploy pipeline において新しいリリースを本番のトラフィックパターンに対して検証する安全な方法です。ユーザーに見えるエラーのリスクなしに、合成テストでは見逃すリグレッションを捉えます。

Where this shows up in a real pipeline

A definition is only useful if you can recognise the thing in your own logs. In practice this concept surfaces when a job behaves differently between a local run and a runner, which is where most CI debugging starts.

  • Compare a local run against a CI run of the same command before assuming a tool is at fault.
  • Runner environments differ in shell, PATH, TTY availability, available memory, and disk. Most CI-only behaviour traces to one of those five.
  • Pin tool versions so an environment difference cannot be introduced by an unrelated update.

よくある質問

What is What is traffic Mirroring??
Traffic mirroring, also called shadowing, duplicates real production requests and forwards the copy to another version of a service while the primary continues to handle the actual response. The mirrored responses are discarded, so users are unaffected. It lets you exercise a new build with realistic load before it serves anyone.
Why does What is traffic Mirroring? matter in CI/CD?
Mirroring is a safe way to validate a new release against production traffic patterns in a deploy pipeline. It catches regressions that synthetic tests miss without risking user-facing errors.

関連ガイド