Add support for Traffic Shadowing
Problem to solve
As a developer I want to test my new functionality with production traffic without actually harming production.
Intended users
User experience goal
The user should be able to "duplicate" some of the production traffic to another server and analyze the behavior of the new functionality with real traffic. This will allow testing performance degradations or for example existence of 500 errors an so on...
This connects very nicely to post deployment monitoring where the users can monitor the new environment and check that everything is ok before pushing to production.
Proposal
Further details
Traffic shadowing is a deployment pattern where production traffic is asynchronously copied to a non-production service for testing. Shadowing is a close cousin to two other commonly known deployment patterns, canary releases and blue/green deployments.
Permissions and Security
Documentation
Availability & Testing
What does success look like, and how can we measure that?
What is the type of buyer?
Is this a cross-stage feature?
Links / references
- https://www.krakend.io/docs/backends/shadow-backends/
- https://blog.christianposta.com/microservices/traffic-shadowing-with-istio-reduce-the-risk-of-code-release/
- https://www.getambassador.io/docs/latest/topics/using/shadowing/
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.