Gray Deployment Request Routing with Load Balancing

DevOps & CI/CD · flowchart diagram · unknown license

Illustrates how a normal request is routed through a gateway and a load balancing algorithm to either a gray deployment instance or a stable instance of a

Source: https://github.com/labidc/labidc-gray-deploy/blob/2a233e2d91eaabd0b0d24ce0ce83a73626e5630c/readme/1.md
Curated by labidc
Gray Deployment Canary Release A/B Testing Load Balancer Zuul Microservices DevOps

Mermaid source

graph LR
    start[正常请求] --> input[网关 gateway/zuul ]
    input --> conditionA{负载均衡算法}
    conditionA -- 命中 --> B{服务1-实例1}
    conditionA -- 未命中 --> C{服务1-实例2}
    B --> D{服务2}
    D --> E{服务3}

What this diagram shows

This flowchart details the journey of a normal request through a system employing gray deployment. It shows a gateway (like Zuul) receiving the request, followed by a load balancing algorithm that decides whether to route the request to a specific "gray" instance (Service 1 - Instance 1) or a standard, stable instance (Service 1 - Instance 2). Subsequent services (Service 2, Service 3) are also shown.

When to use it

Use this diagram to explain or plan strategies for gradual rollouts, A/B testing, canary releases, or controlled feature testing in a production environment. It's ideal for visualizing how traffic is split and directed to different service versions.

How to adapt it for your project

This diagram can be adapted by adding more complex load balancing rules, incorporating monitoring and rollback mechanisms, detailing specific criteria for "hit" or "miss" (e.g., user groups, headers), or extending the service chain to show more microservices involved in the gray deployment.

Key concepts