Gray Release (Canary Deployment) Design and Implementation Guide

Gray release, also known as canary deployment, is a technique that allows rapid iteration of internet products while ensuring quality and limiting the impact of potential issues by routing a portion of user traffic to a new version for testing.

The basic gray release architecture consists of three essential components: a strategy configuration platform to store gray policies, an execution program that applies these policies, and a service registry that records service instances with IP, port, name, and version.

Common gray strategies include traffic splitting based on request headers, cookies, or request parameters such as user UID modulo operations, with strategies classified as single or composite.

Execution control can be implemented in upstream services like Nginx (using Lua extensions and a local agent to receive and apply policies) or in gateway/business/data layers by integrating a configuration SDK to fetch and enforce policies.

Complex scenarios are illustrated:

Scenario 1 – Simultaneous gray release of multiple services: The new gateway tags requests with a tag T; downstream services forward requests based on the presence of tag T, directing them to either new or old versions.

Scenario 2 – Data‑centric gray release: When schema changes require separate databases, data is duplicated and written to both old and new databases (dual‑write) with synchronization via MQ to ensure consistency, and data comparison is performed to verify integrity.

The article concludes with a summary of key points and invites readers to join a discussion group for further learning.