Skip to main content

Mirrored/Shadow Deployment

This strategy is best for testing production traffic loads!

A Mirrored/Shadow deployment strategy is one where the new version is available alongside the old version, but a copy or forked version of traffic to the older version is sent to the new version for production testing. This deployment strategy is useful to test production load on a new feature. A rollout of the application is triggered only when stability and performance meet the requirements. This allows users to monitor the latest version under load without any possibility of customer impact.

Docs Version Dropdown

Advantages of Mirrored/Shadow Deployment#

The benefits of Mirrored/Shadow deployment strategy include,

  • This strategy allows performance testing of the application with production traffic.
  • There is no negative impact on the users.
  • There is no rollout until the stability and performance of the application meets the requirements, thus reducing the deployment risks.