How to realize integration of grayscale routing and traffic protection based on Nacos and Sentinel

• Encapsulates the read logic of the remote configuration center and the local rule file. That is, the remote configuration is read first. If the remote configuration does not exist or the rule is incorrect, the local rule file is read. Dynamically implement hot refreshing of rules by remote configuration center
• Package NacosDataSource and ApolloDataSource, support Nacos and Apollo two remote configuration centers, zero code to achieve Sentinel function. For more remote configuration centers, see Sentinel’s official DataSource and integrate them yourself
• Supports native flow control rules, degradation rules, authorization rules, system rules, and hotspot parameter flow control rules
• The LimitApp mechanism is extended. The combined protection mechanism is implemented through dynamic Http Header, including the protection mechanism based on service name, gray level group, gray level version, gray level region, machine address and port. Any combination of service parameters can be customized to achieve this function. According to the incoming micro service gray version number + user name, combine them together for fusing
• In addition, rules can be written in micro-service Actuator, Swagger, and Rest modes
• In the console, users can write rules in batches using microservice name actuators, Swagger, and Rest
• Support switch off this spring. The application. The strategy. The sentinel. Enabled = true, is off by default

Environment setup and dependency introduction

<dependency>
    <groupId>com.nepxion</groupId>
    <artifactId>discovery-plugin-strategy-starter-service-sentinel</artifactId>
    <version>${discovery.version}</version> </dependency> <dependency> <groupId>com.nepxion</groupId> <artifactId>discovery-plugin-strategy-sentinel-starter-nacos</artifactId> <! -- <artifactId>discovery-plugin-strategy-sentinel-starter-apollo</artifactId> --> <version>${discovery.version}</version>
</dependency>Copy the code

Native Sentinel annotation

@RestController
@ConditionalOnProperty(name = DiscoveryConstant.SPRING_APPLICATION_NAME, havingValue = "discovery-guide-service-b")
public class BFeignImpl extends AbstractFeignImpl implements BFeign {
    private static final Logger LOG = LoggerFactory.getLogger(BFeignImpl.class);

    @Override
    @SentinelResource(value = "sentinel-resource", blockHandler = "handleBlock", fallback = "handleFallback")
    public String invoke(@PathVariable(value = "value") String value) {
        value = doInvoke(value);

        LOG.info("Call path: {}", value);

        return value;
    }

    public String handleBlock(String value, BlockException e) {
        return value + "-> B server sentinel block, cause=" + e.getClass().getName() + ", rule=" + e.getRule() + ", limitApp=" + e.getRuleLimitApp();
    }

    public String handleFallback(String value) {
        return value + "-> B server sentinel fallback"; }}Copy the code

Native Sentinel rule

Nacos Key format: Group is [Group name] configured in metadata, Data Id is [service name]-[rule type] 2. Apollo Key format: [Group name]-[service name]-[rule type]Copy the code

Flow control rules

[{"resource": "sentinel-resource"."limitApp": "default"."grade": 1,
        "count": 1,
        "strategy": 0."refResource": null,
        "controlBehavior": 0."warmUpPeriodSec": 10,
        "maxQueueingTimeMs": 500,
        "clusterMode": false."clusterConfig": null
    }
]Copy the code

Drop rules

[{"resource": "sentinel-resource"."limitApp": "default"."count": 2."timeWindow": 10,
        "grade": 0."passCount": 0}]Copy the code

Authorization rules

[{"resource": "sentinel-resource"."limitApp": "discovery-guide-service-a"."strategy": 0}]Copy the code

Rules of the system

[{"resource": null,
        "limitApp": null,
        "highestSystemLoad": 1.0,"highestCpuUsage": 1.0,"qps": 200.0."avgRt": 1,"maxThread"1}] : -Copy the code

Hotspot parameter flow control rule

[{"resource": "sentinel-resource"."limitApp": "default"."grade": 1,
        "paramIdx": 0."count": 1,
        "controlBehavior": 0."maxQueueingTimeMs": 0."burstCount": 0."durationInSec": 1,
        "paramFlowItemList": []."clusterMode": false}]Copy the code

Protection mechanism based on grayscale routing and Sentinel-LimitApp extension

Service name-based protection mechanism

spring.application.strategy.service.sentinel.request.origin.key=n-d-service-idCopy the code

[{"resource": "sentinel-resource"."limitApp": "discovery-guide-service-a"."strategy": 0}]Copy the code

Protection mechanism based on grayscale group

spring.application.strategy.service.sentinel.request.origin.key=n-d-service-groupCopy the code

[{"resource": "sentinel-resource"."limitApp": "my-group"."strategy": 0}]Copy the code

Protection mechanism based on grayscale version

spring.application.strategy.service.sentinel.request.origin.key=n-d-service-versionCopy the code

[{"resource": "sentinel-resource"."limitApp": "1.0"."strategy": 0}]Copy the code

Protection mechanism based on gray area

spring.application.strategy.service.sentinel.request.origin.key=n-d-service-regionCopy the code

[{"resource": "sentinel-resource"."limitApp": "dev"."strategy": 0}]Copy the code

Protection mechanism based on machine address and port

spring.application.strategy.service.sentinel.request.origin.key=n-d-service-addressCopy the code

[{"resource": "sentinel-resource"."limitApp": "192.168.0.88:8081192168 0.88:8082"."strategy": 0}]Copy the code

Combined protection mechanism for user-defined service parameters

// Version number + username, Implement sectional fusing public class MyServiceSentinelRequestOriginAdapter extends DefaultServiceSentinelRequestOriginAdapter { @Override public String parseOrigin(HttpServletRequest request) { String version = request.getHeader(DiscoveryConstant.N_D_SERVICE_VERSION); String user = request.getHeader("user");

        return version + "&"+ user; }}Copy the code

@Bean
public ServiceSentinelRequestOriginAdapter ServiceSentinelRequestOriginAdapter() {
    return new MyServiceSentinelRequestOriginAdapter();
}Copy the code

[{"resource": "sentinel-resource"."limitApp": "1.0 & zhangsan"."strategy": 0}]Copy the code

• When user=zhangsan in the Http Header passed, when the full link call is in progress, API gateway load balancing discovery-guide-service-a service is called after version 1.0, and finally the call succeeds

• When user=lisi is passed in the Http Header, the final call is rejected on the discovery-guide-service-b server

• When user=zhangsan in Http Header is passed, one of the conditions is met. When the full link invocation, API gateway load balance discovery-guide-service-a service to version 1.1 and then call discovery-guide-service-b service. The final call was rejected on the discovery-guide-service-b server because version=1.0 was not met

Sentinel rule push based on Swagger

Sentinel rule push based on a single service instance

Push Sentinel rules based on multiple service instances corresponding to service names