9、Nepxion Discovery 之服务灰度发布参数的支持

绝地灬酷狼 2022-12-27 09:17 188阅读 0赞

`Nepxion Discovery` 对于服务灰度发布参数支持：外置`Header`、 `Parameter`、`Cookie`、`域名`规则策略驱动。并且还内置本地和远程、局部和全局规则策略驱动。并且还支持正则表达式以及通配表达式支持。并且`Nepxion Discovery`支持`Spring Cloud Gateway`、`Zuul网关`和`微服务`三大模式的灰度发布和路由等一系列功能。 所以`Nepxion Discovery` 对于灰度发布的支持场景还是很丰富的，基本能够满足生产的大多数场景。关于`Nepxion Discovery`的策略博主准备分解成三篇文章来讲解：

*  `配置中心对灰度的配置`：包括初始化、对不同配置中心的适配以及配置中心策略变更的通知
 *  `服务灰度发布参数的支持`：包含上面外置、内置规则策略驱动以及远程配置灰度参数的优先级
 *  `对网关和微服务三大模式的支持`：包含不同模式对下游参数的传递以及如何进行负载均衡的

在上一篇博客 [8、Nepxion Discovery 之配置中心支持灰度配置][8_Nepxion Discovery] 中讲解了 `Nepxion Discovery` 对于内置本地和远程、局部和全局规则的策略驱动。在这一篇文章，首先会来分析一下框架对外置参数的支持，然后会来分析一下基于配置中心的策略策略驱动的具体分析。为了框架灵活性，配置中心的策略驱动配置还是蛮复杂的。

> 注意：为了看懂这篇博客建议在电脑上观看，因为需要对照代码与 xml 配置才能更好的理解

## 1、服务发布类型 ##

在分析远程配置策略之前，首先要介绍一下版本发布里面的一些概念。长期以来，业务升级渐渐形成了几个发布策略：蓝绿发布、灰度发布和滚动发布，目的是尽可能避免因发布导致的流量丢失或服务不可用问题。

### 1.1 蓝绿发布 ###

蓝绿发布Blue-Green Deployment：项目逻辑上分为AB组，在项目系统时，首先把 A 组从负载均衡中摘除，进行新版本的部署。B 组仍然继续提供服务。当 A 组升级完毕，负载均衡重新接入A组，再把B组从负载列表中摘除，进行新版本的部署。A组重新提供服务。最后，B组也升级完成，负载均衡重新接入B组，此时，AB组版本都已经升级完成，并且都对外提供服务。

![在这里插入图片描述][watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L3UwMTI0MTA3MzM_size_16_color_FFFFFF_t_70]

> 优点：流量在新版本升级和老版本回滚迅速。用户可以灵活控制流量走向  
> 缺点：成本较高，需要部署两套蓝绿环境。新版本如出现问题，切换不及时，会造成大面积故障

### 1.2 灰度发布 ###

灰度发布 Gray Release（又名金丝雀发布Canary Release）：不停机旧版本，部署新版本，低比例流量（例如：5%）切换到新版本，高比例流量（例如：95%）仍走旧版本，通过监控观察，如无问题，逐步扩大范围，最终把所有流量都迁移到新版本上。属无损发布。  
![在这里插入图片描述][watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L3UwMTI0MTA3MzM_size_16_color_FFFFFF_t_70 1]

> 优点：灵活简单，不需要用户标记驱动。安全性高，新版本如出现问题，只会发生在低比例的流量上  
> 缺点：流量配比递增的配置修改，带来额外的操作成本。用户覆盖狭窄，低比例流量未必能发现所有问题

### 1.3 滚动发布 ###

滚动发布(Rolling Release)：每次只升级一个或多个服务，升级完成后加入生产环境，不断执行这个过程，直到集群中的全部旧版本升级到新版本。停止旧版本的过程中，无法精确计算旧版本是否已经完成它正在执行的工作，需要靠业务自身去判断。属有损发布

![在这里插入图片描述][watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L3UwMTI0MTA3MzM_size_16_color_FFFFFF_t_70 2]

> 优点：出现问题影响范围很小，只会发生在若干台正在滚动发布的服务上  
> 缺点：发布和回滚需要较长的时间周期。按批次停止旧版本，启动新版本，由于旧版本不保留，一旦全部升级完毕后才发现问题，则无法快速回滚

## 2、StrategyWrapper ##

`Nepxion Discovery` 要实现灰度发布肯定是需要从外部请求中获取传递过来的参数，它本身支持`Spring Cloud Gateway`、`Zuul网关`和`微服务`三大模式的灰度发布功能。在这里我们就以 `Spring Cloud Gateway` 为例来分析一下对外置规则策略驱动的支持以及远程配置灰度策略的优先级讨论。

我们都知道对于 `Spring Cloud Gateway` 框架如果我们需要对它进行扩展，只需要扩展它的 Filter 就行了。`Nepxion Discovery` 通过 `AbstractGatewayStrategyRouteFilter` 实现 `Spring Cloud Gateway` 的 `GlobalFilter`来进行对请求参数的解析。当然这个类现在涉及到对下游的参数传递，现在我们不讨论这个问题，再下一篇博客会详细讨论它对`Spring Cloud Gateway`、`Zuul网关`和`微服务`三大模式的灰度发布功能的支持。这里提到它主要是它是入口，我在学习东西的时候喜欢从入口找到出口。这样能够把所有的知识点都串联起来，记忆也更加深刻。好了废话就不多说了，进入我们主题。下面我来画一下调用到核心处理类的时序图，如果大家对中间过程想要了解可以自行分析哈。在这里只是给大家把整个框架的核心概念给串起来。

![在这里插入图片描述][watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L3UwMTI0MTA3MzM_size_16_color_FFFFFF_t_70 3]  
在上面的时序图里以获取路由版本为例，以 `Spring Cloud Gateway` 它的扩展 `Filter` 开始调用到 `StrategyWrapper` 这个灰度发布策略核心类为终点的时序图。在 `StrategyWrapper` 里面的方法比较多，大家看到这个类可能有点蒙圈。我们由简入繁，先通过 `Nepxion Discovery` 对路由版本为例，然后再逐渐深入分析`Nepxion Discovery`的灰度发布策略。

> StrategyWrapper.java

public class StrategyWrapper { 
    
        // 从远程配置中心或者本地配置文件获取版本路由配置。如果是远程配置中心，则值会动态改变
        public String getRouteVersion(Map<String, String> headerMap) { 
            String routeVersion = getConditionBlueGreenRouteVersion(headerMap);
            if (StringUtils.isEmpty(routeVersion)) { 
                routeVersion = getConditionGrayRouteVersion(headerMap);
                if (StringUtils.isEmpty(routeVersion)) { 
                    routeVersion = getGlobalRouteVersion();
                }
            }
    
            return routeVersion;
        }
    
    	......
    
    }

上面的代码逻辑其实就是对上面的发布类型优先级的支持：

*  条件蓝绿部署配置路由版本为第一优先级
 *  条件灰度部署配置路由版本为第二优先级
 *  基于Http Header传递的策略路由，全局缺省路由为第三优先级

在最下面有 XML 最全的配置，其实里面的配置已经说明情况了，我就把相关的信息截取出来。

<?xml version="1.0" encoding="UTF-8"?>
    <rule>
        
        <strategy>
            
            <version>{"discovery-springcloud-example-a":"1.0", "discovery-springcloud-example-b":"1.0", "discovery-springcloud-example-c":"1.0;1.2"}</version>
            
            
            <region>{"discovery-springcloud-example-a":"qa;dev", "discovery-springcloud-example-b":"dev", "discovery-springcloud-example-c":"qa"}</region>
            
            
            <address>{"discovery-springcloud-example-a":"192.168.43.101:1100", "discovery-springcloud-example-b":"192.168.43.101:1201", "discovery-springcloud-example-c":"192.168.43.101:1300"}</address>
            
            
            <version-weight>{"discovery-springcloud-example-a":"1.0=90;1.1=10", "discovery-springcloud-example-b":"1.0=90;1.1=10", "discovery-springcloud-example-c":"1.0=90;1.1=10"}</version-weight>
            
            
            <region-weight>{"discovery-springcloud-example-a":"dev=85;qa=15", "discovery-springcloud-example-b":"dev=85;qa=15", "discovery-springcloud-example-c":"dev=85;qa=15"}</region-weight>
            
        </strategy>
    
        
        <strategy-customization>
            
            
            
            
            
            
    
            
            
            <conditions type="blue-green">
                <condition id="1" header="#H['a'] == '1' && #H['b'] == '2'" version-id="a-1" region-id="b-1" address-id="c-1" version-weight-id="d-1" region-weight-id="e-1"/>
                <condition id="2" header="#H['c'] == '3'" version-id="a-2" region-id="b-2" address-id="c-2" version-weight-id="d-2" region-weight-id="e-2"/>
            </conditions>
    
            
            
            <conditions type="gray">
                <condition id="1" header="#H['a'] == '1' && #H['b'] == '2'" version-id="a-1=10;a-2=90" region-id="b-1=20;b-2=80" address-id="c-1=30;c-2=70"/>
                <condition id="2" header="#H['c'] == '3'" version-id="a-1=90;a-2=10" region-id="b-1=80;b-2=20" address-id="c-1=70;c-2=30"/>
                <condition id="3" version-id="a-1=5;a-2=95" region-id="b-1=5;b-2=95" address-id="c-1=5;c-2=95"/>
            </conditions>
    
            <routes>
                <route id="a-1" type="version">{"discovery-springcloud-example-a":"1.0", "discovery-springcloud-example-b":"1.0", "discovery-springcloud-example-c":"1.0;1.2"}</route>
                <route id="a-2" type="version">{"discovery-springcloud-example-a":"1.1", "discovery-springcloud-example-b":"1.1", "discovery-springcloud-example-c":"1.2"}</route>
                <route id="b-1" type="region">{"discovery-springcloud-example-a":"qa;dev", "discovery-springcloud-example-b":"dev", "discovery-springcloud-example-c":"qa"}</route>
                <route id="b-2" type="region">{"discovery-springcloud-example-a":"qa", "discovery-springcloud-example-b":"qa", "discovery-springcloud-example-c":"qa"}</route>
                <route id="c-1" type="address">{"discovery-springcloud-example-a":"192.168.43.101:1100", "discovery-springcloud-example-b":"192.168.43.101:1201", "discovery-springcloud-example-c":"192.168.43.101:1300"}</route>
                <route id="c-2" type="address">{"discovery-springcloud-example-a":"192.168.43.101:1101", "discovery-springcloud-example-b":"192.168.43.101:1201", "discovery-springcloud-example-c":"192.168.43.101:1301"}</route>
                <route id="d-1" type="version-weight">{"discovery-springcloud-example-a":"1.0=90;1.1=10", "discovery-springcloud-example-b":"1.0=90;1.1=10", "discovery-springcloud-example-c":"1.0=90;1.1=10"}</route>
                <route id="d-2" type="version-weight">{"discovery-springcloud-example-a":"1.0=10;1.1=90", "discovery-springcloud-example-b":"1.0=10;1.1=90", "discovery-springcloud-example-c":"1.0=10;1.1=90"}</route>
                <route id="e-1" type="region-weight">{"discovery-springcloud-example-a":"dev=85;qa=15", "discovery-springcloud-example-b":"dev=85;qa=15", "discovery-springcloud-example-c":"dev=85;qa=15"}</route>
                <route id="e-2" type="region-weight">{"discovery-springcloud-example-a":"dev=15;qa=85", "discovery-springcloud-example-b":"dev=15;qa=85", "discovery-springcloud-example-c":"dev=15;qa=85"}</route>
            </routes>
    
            
            <headers>
                <header key="a" value="1"/>
            </headers>
        </strategy-customization>
    
    	...
    
    <rule>

相信大家根据上面的代码已经配置文件里面的说明就可以很清楚的知道，第一优先级是`<strategy-customization>` 标签下类型 `<conditions type="blue-green">` 的蓝绿发布配置。第二优先级是`<strategy-customization>` 标签下类型 `<conditions type="gray">` 的灰度发布配置，`<routes>` 标签中的 `<route>`是用来对具体路由的声明。

**在蓝绿发布配置和灰度发布配置都支持条件式：**

*  通过Spring Spel的条件表达式支持等于=、不等于!=、大于>、小于<、与&&、或||、匹配matches，以及加减乘除取模等全部标准表达式用法
 *  通过Spring Matcher的通配表达式支持多个通配\*、单个通配?等全部标准表达式用法

最低优先级全局缺省路由不支持条件表达式。对于具体的配置信息大家可以到 [Nepxion/Discover 官网][Nepxion_Discover]，上面有更加具体的描述。

## 3、外置规则策略驱动 ##

上面已经提到在配置中心配置规则的时候蓝绿发布配置以及灰度发布配置它们都是支持条件表达式的。下面我们来看一下灰度参数解析的调用时序图。  
![在这里插入图片描述][watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L3UwMTI0MTA3MzM_size_16_color_FFFFFF_t_70 4]  
从上面我们可以看到其实就是从 `RuleCache` 这个缓存里面去获取远程或者本地配置的灰度策略。`RuleCache` 这个对象其实就是我们上一篇博客分析过了，在服务启动时会去加载远程配置中心或者在监听到远程配置中心发生变更时通知服务实例变更 `RuleCache` 这个使用 `Caffeine` 本地缓存作为缓存的缓存。

最终条件判断和核心处理逻辑是在 `HeaderExpressionStrategyCondition` 这个类里面。

> HeaderExpressionStrategyCondition.java

public class HeaderExpressionStrategyCondition extends AbstractStrategyCondition { 
        private Pattern pattern = Pattern.compile(DiscoveryConstant.EXPRESSION_REGEX);
    
        @Autowired
        private StrategyWrapper strategyWrapper;
    
        @Override
        public boolean isTriggered(StrategyConditionEntity strategyConditionEntity) { 
            Map<String, String> headerMap = createHeaderMap(strategyConditionEntity);
    
            return isTriggered(strategyConditionEntity, headerMap);
        }
    
        private Map<String, String> createHeaderMap(StrategyConditionEntity strategyConditionEntity) { 
            String conditionHeader = strategyConditionEntity.getConditionHeader();
    
            Map<String, String> headerMap = new HashMap<String, String>();
    
            Matcher matcher = pattern.matcher(conditionHeader);
            while (matcher.find()) { 
                String group = matcher.group();
                String headerName = StringUtils.substringBetween(group, DiscoveryConstant.EXPRESSION_SUB_PREFIX, DiscoveryConstant.EXPRESSION_SUB_SUFFIX);
                String headerValue = null;
    
                // 从外置Header获取
                if (StringUtils.isBlank(headerValue)) { 
                    headerValue = strategyContextHolder.getHeader(headerName);
                }
    
                // 从内置Header获取
                if (StringUtils.isBlank(headerValue)) { 
                    headerValue = strategyWrapper.getHeader(headerName);
                }
    
                // 从外置Parameter获取
                if (StringUtils.isBlank(headerValue)) { 
                    headerValue = strategyContextHolder.getParameter(headerName);
                }
    
                // 从外置Cookie获取
                if (StringUtils.isBlank(headerValue)) { 
                    headerValue = strategyContextHolder.getCookie(headerName);
                }
    
                if (StringUtils.isNotBlank(headerValue)) { 
                    headerMap.put(headerName, headerValue);
                }
            }
    
            return headerMap;
        }
    
        @Override
        public boolean isTriggered(StrategyConditionEntity strategyConditionEntity, Map<String, String> headerMap) { 
            String conditionHeader = strategyConditionEntity.getConditionHeader();
    
            return DiscoveryExpressionResolver.eval(conditionHeader, DiscoveryConstant.EXPRESSION_PREFIX, headerMap, strategyTypeComparator);
        }
    }

*  首先从 RuleCache 里面拿到远程蓝绿发布或者灰度发布配置信息
 *  然后 `<strategy-customization>` 标签中的中的蓝绿灰度配置 `<conditions type="blue-green">` 或者 `<conditions type="gray">`它们的标签下的标签 `<condition>` 中的 `header` 属性支持条件表达式。就从 `<condition>` 中的 `header` 属性获取到这个表达式
 *  从 `<condition>` 中的 `header` 属性表达式中获取到这个属性。格式为：`#H['a']`，就表式从参数里面获取 `a` 这个 key 的值
 *  然后，首先从外置Header获取获取值；接着从内置Header获取如果有值就覆盖；然后从外置Parameter获取，如果有值就覆盖；最后从外置Cookie获取，如果有值就覆盖。所以它们的优先级是：`外置Header > 内置Header(配置中心) > 外置Parameter > 外置Cookie`
 *  最近获取到的值通过 `DiscoveryExpressionResolver.eval` 进行条件计算，如果满足条件。则该 `<strategy-customization>`/ `</conditions>`/`<condition>` 下的灰度配置条件就生效。

## 4、规则策略示例 ##

XML最全的示例如下，Json示例见源码 `discovery-springcloud-example-service` 工程下的rule.json

<?xml version="1.0" encoding="UTF-8"?>
    <rule>
        
        <register>
            
            
            
            
            
            <blacklist filter-value="10.10;11.11">
                
                <service service-name="discovery-springcloud-example-a" filter-value="172.16"/>
            </blacklist>
    
            
    
            
            
            
            
            <count filter-value="10000">
                
                <service service-name="discovery-springcloud-example-a" filter-value="5000"/>
            </count>
        </register>
    
        <discovery>
            
            
            <blacklist filter-value="10.10;11.11">
                
                <service service-name="discovery-springcloud-example-b" filter-value="172.16"/>
            </blacklist>
    
            
            
            
            
            
            
            
            
            
            
            
            
            
            
            
            
            
            
            <version>
                
                <service consumer-service-name="discovery-springcloud-example-gateway" provider-service-name="discovery-springcloud-example-a" consumer-version-value="1.0" provider-version-value="1.0"/>
                
                <service consumer-service-name="discovery-springcloud-example-gateway" provider-service-name="discovery-springcloud-example-a" consumer-version-value="1.1" provider-version-value="1.1"/>
                
                <service consumer-service-name="discovery-springcloud-example-zuul" provider-service-name="discovery-springcloud-example-a" consumer-version-value="1.0" provider-version-value="1.0"/>
                
                <service consumer-service-name="discovery-springcloud-example-zuul" provider-service-name="discovery-springcloud-example-a" consumer-version-value="1.1" provider-version-value="1.1"/>
                
                <service consumer-service-name="discovery-springcloud-example-a" provider-service-name="discovery-springcloud-example-b" consumer-version-value="1.0" provider-version-value="1.0"/>
                
                <service consumer-service-name="discovery-springcloud-example-a" provider-service-name="discovery-springcloud-example-b" consumer-version-value="1.1" provider-version-value="1.1"/>
                
                <service consumer-service-name="discovery-springcloud-example-b" provider-service-name="discovery-springcloud-example-c" consumer-version-value="1.0" provider-version-value="1.0;1.1"/>
                
                <service consumer-service-name="discovery-springcloud-example-b" provider-service-name="discovery-springcloud-example-c" consumer-version-value="1.1" provider-version-value="1.2"/>
            </version>
    
            
            
            
            
            
            
            
            
            
            
            
            
            
            
            
            
            
            
            <region>
                
                <service consumer-service-name="discovery-springcloud-example-a" provider-service-name="discovery-springcloud-example-b" consumer-region-value="dev" provider-region-value="dev"/>
                
                <service consumer-service-name="discovery-springcloud-example-a" provider-service-name="discovery-springcloud-example-b" consumer-region-value="qa" provider-region-value="qa"/>
                
                <service consumer-service-name="discovery-springcloud-example-b" provider-service-name="discovery-springcloud-example-c" consumer-region-value="dev" provider-region-value="dev"/>
                
                <service consumer-service-name="discovery-springcloud-example-b" provider-service-name="discovery-springcloud-example-c" consumer-region-value="qa" provider-region-value="qa"/>
            </region>
    
            
            
            
            
            
            
            
            
            
            
            
            
            
            
    
            
            
            
            
            
            
            
            
            
            
            
            <weight>
                
                
                <service consumer-service-name="discovery-springcloud-example-b" provider-service-name="discovery-springcloud-example-c" provider-weight-value="1.0=90;1.1=10" type="version"/>
                
                <service provider-service-name="discovery-springcloud-example-c" provider-weight-value="1.0=90;1.1=10" type="version"/>
                
                <version provider-weight-value="1.0=90;1.1=10"/>
    
                
                <service consumer-service-name="discovery-springcloud-example-b" provider-service-name="discovery-springcloud-example-c" provider-weight-value="dev=85;qa=15" type="region"/>
                
                <service provider-service-name="discovery-springcloud-example-c" provider-weight-value="dev=85;qa=15" type="region"/>
                
                <region provider-weight-value="dev=85;qa=15"/>
            </weight>
        </discovery>
    
        
        <strategy>
            
            <version>{ "discovery-springcloud-example-a":"1.0", "discovery-springcloud-example-b":"1.0", "discovery-springcloud-example-c":"1.0;1.2"}</version>
            
            
            <region>{ "discovery-springcloud-example-a":"qa;dev", "discovery-springcloud-example-b":"dev", "discovery-springcloud-example-c":"qa"}</region>
            
            
            <address>{ "discovery-springcloud-example-a":"192.168.43.101:1100", "discovery-springcloud-example-b":"192.168.43.101:1201", "discovery-springcloud-example-c":"192.168.43.101:1300"}</address>
            
            
            <version-weight>{ "discovery-springcloud-example-a":"1.0=90;1.1=10", "discovery-springcloud-example-b":"1.0=90;1.1=10", "discovery-springcloud-example-c":"1.0=90;1.1=10"}</version-weight>
            
            
            <region-weight>{ "discovery-springcloud-example-a":"dev=85;qa=15", "discovery-springcloud-example-b":"dev=85;qa=15", "discovery-springcloud-example-c":"dev=85;qa=15"}</region-weight>
            
        </strategy>
    
        
        <strategy-customization>
            
            
            
            
            
            
    
            
            
            <conditions type="blue-green">
                <condition id="1" header="#H['a'] == '1' && #H['b'] == '2'" version-id="a-1" region-id="b-1" address-id="c-1" version-weight-id="d-1" region-weight-id="e-1"/>
                <condition id="2" header="#H['c'] == '3'" version-id="a-2" region-id="b-2" address-id="c-2" version-weight-id="d-2" region-weight-id="e-2"/>
            </conditions>
    
            
            
            <conditions type="gray">
                <condition id="1" header="#H['a'] == '1' && #H['b'] == '2'" version-id="a-1=10;a-2=90" region-id="b-1=20;b-2=80" address-id="c-1=30;c-2=70"/>
                <condition id="2" header="#H['c'] == '3'" version-id="a-1=90;a-2=10" region-id="b-1=80;b-2=20" address-id="c-1=70;c-2=30"/>
                <condition id="3" version-id="a-1=5;a-2=95" region-id="b-1=5;b-2=95" address-id="c-1=5;c-2=95"/>
            </conditions>
    
            <routes>
                <route id="a-1" type="version">{ "discovery-springcloud-example-a":"1.0", "discovery-springcloud-example-b":"1.0", "discovery-springcloud-example-c":"1.0;1.2"}</route>
                <route id="a-2" type="version">{ "discovery-springcloud-example-a":"1.1", "discovery-springcloud-example-b":"1.1", "discovery-springcloud-example-c":"1.2"}</route>
                <route id="b-1" type="region">{ "discovery-springcloud-example-a":"qa;dev", "discovery-springcloud-example-b":"dev", "discovery-springcloud-example-c":"qa"}</route>
                <route id="b-2" type="region">{ "discovery-springcloud-example-a":"qa", "discovery-springcloud-example-b":"qa", "discovery-springcloud-example-c":"qa"}</route>
                <route id="c-1" type="address">{ "discovery-springcloud-example-a":"192.168.43.101:1100", "discovery-springcloud-example-b":"192.168.43.101:1201", "discovery-springcloud-example-c":"192.168.43.101:1300"}</route>
                <route id="c-2" type="address">{ "discovery-springcloud-example-a":"192.168.43.101:1101", "discovery-springcloud-example-b":"192.168.43.101:1201", "discovery-springcloud-example-c":"192.168.43.101:1301"}</route>
                <route id="d-1" type="version-weight">{ "discovery-springcloud-example-a":"1.0=90;1.1=10", "discovery-springcloud-example-b":"1.0=90;1.1=10", "discovery-springcloud-example-c":"1.0=90;1.1=10"}</route>
                <route id="d-2" type="version-weight">{ "discovery-springcloud-example-a":"1.0=10;1.1=90", "discovery-springcloud-example-b":"1.0=10;1.1=90", "discovery-springcloud-example-c":"1.0=10;1.1=90"}</route>
                <route id="e-1" type="region-weight">{ "discovery-springcloud-example-a":"dev=85;qa=15", "discovery-springcloud-example-b":"dev=85;qa=15", "discovery-springcloud-example-c":"dev=85;qa=15"}</route>
                <route id="e-2" type="region-weight">{ "discovery-springcloud-example-a":"dev=15;qa=85", "discovery-springcloud-example-b":"dev=15;qa=85", "discovery-springcloud-example-c":"dev=15;qa=85"}</route>
            </routes>
    
            
            <headers>
                <header key="a" value="1"/>
            </headers>
        </strategy-customization>
    
        
        <strategy-blacklist>
            
            
            <id value="e92edde5-0153-4ec8-9cbb-b4d3f415aa33;af043384-c8a5-451e-88f4-457914e8e3bc"/>
    
            
            
    
            
            
            <address value="192.168.43.101:1201;192.168.*.102;1301"/>
    
            
            
        </strategy-blacklist>
    
        
        <parameter>
            
            
            
            
            
            <service service-name="discovery-springcloud-example-a" tag-key="version" tag-value="1.0" key="ShardingSphere" value="db1"/>
            <service service-name="discovery-springcloud-example-a" tag-key="version" tag-value="1.1" key="ShardingSphere" value="db2"/>
            <service service-name="discovery-springcloud-example-b" tag-key="region" tag-value="dev" key="RocketMQ" value="queue1"/>
            <service service-name="discovery-springcloud-example-b" tag-key="region" tag-value="qa" key="RocketMQ" value="queue2"/>
            <service service-name="discovery-springcloud-example-c" tag-key="env" tag-value="env1" key="ShardingSphere" value="db1"/>
            <service service-name="discovery-springcloud-example-c" tag-key="env" tag-value="env2" key="ShardingSphere" value="db2"/>
            <service service-name="discovery-springcloud-example-d" tag-key="zone" tag-value="zone1" key="RocketMQ" value="queue1"/>
            <service service-name="discovery-springcloud-example-d" tag-key="zone" tag-value="zone2" key="RocketMQ" value="queue2"/>
            <service service-name="discovery-springcloud-example-e" tag-key="address" tag-value="192.168.43.101:1201" key="ShardingSphere" value="db1"/>
            <service service-name="discovery-springcloud-example-e" tag-key="address" tag-value="192.168.43.102:1201" key="ShardingSphere" value="db2"/>
        </parameter>
    </rule>

[8_Nepxion Discovery]: https://carlzone.blog.csdn.net/article/details/110913399
[watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L3UwMTI0MTA3MzM_size_16_color_FFFFFF_t_70]: /images/20221120/96304c10afa94a7da64640a5139de046.png
[watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L3UwMTI0MTA3MzM_size_16_color_FFFFFF_t_70 1]: /images/20221120/30a90102070941808082486d9382c08e.png
[watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L3UwMTI0MTA3MzM_size_16_color_FFFFFF_t_70 2]: /images/20221120/b165a1cfd94e446399588ed5ad015d6f.png
[watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L3UwMTI0MTA3MzM_size_16_color_FFFFFF_t_70 3]: https://img-blog.csdnimg.cn/20201210130416702.png?x-oss-process=image/watermark,type_ZmFuZ3poZW5naGVpdGk,shadow_10,text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L3UwMTI0MTA3MzM=,size_16,color_FFFFFF,t_70
[Nepxion_Discover]: https://github.com/Nepxion/Discovery
[watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L3UwMTI0MTA3MzM_size_16_color_FFFFFF_t_70 4]: https://img-blog.csdnimg.cn/20201210232627677.png?x-oss-process=image/watermark,type_ZmFuZ3poZW5naGVpdGk,shadow_10,text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L3UwMTI0MTA3MzM=,size_16,color_FFFFFF,t_70