Design and Implementation of a Gray Release System for Microservices

Gray (canary) release is a technique that allows fast iteration of internet products while ensuring quality by routing a portion of user traffic to new versions for validation, and quickly rolling back if issues arise, essentially functioning as an A/B testing system.

The basic architecture consists of three core components: a strategy configuration platform storing release policies, an execution engine that applies the gray logic, and a service registry where each service registers its ip/Port/name/version information.

Release strategies are defined in the configuration platform and commonly include traffic splitting based on request headers, cookies, or request parameters such as a user uid modulo operation to target a specific percentage of users.

Strategies can be single (e.g., modulo on uid , token , or ip ) or composite, where multiple services are released together using a shared tag identifier.

Execution control varies by upstream component. When using Nginx, a Lua extension is required to interpret gray policies and perform routing, with a locally deployed Agent fetching policies from the configuration platform and updating Nginx configuration for graceful reloads.

In gateway, business, or data‑access layers, integrating the configuration platform SDK enables services to receive policies and execute them directly without additional proxy logic.

Complex scenarios include:

Simultaneous gray release of multiple services in a call chain, where a request is tagged with tag T at the gateway and forwarded to new versions of services that recognize the tag, while untagged requests continue to hit legacy services.

Data‑layer gray releases where schema changes require separate databases; a dual‑write approach copies data to a new database, uses a message queue (MQ) to ensure eventual consistency, and compares data between old and new stores to avoid loss.

These designs enable controlled, incremental rollouts of new functionality across microservice architectures while maintaining system stability.