Shulou(Shulou.com)06/03 Report--

This article mainly introduces "how to realize the grayscale publishing mode under the micro-service mode". In the daily operation, I believe that many people have doubts about how to realize the grayscale publishing mode under the micro-service mode. I have consulted all kinds of materials and sorted out the simple and easy-to-use operation methods. I hope it will be helpful to answer the doubts about "how to realize the grayscale publishing mode under the micro-service mode". Next, please follow the editor to study!

I. basic logic

The request passes through the 8001 service. In the grayscale rule, the list of services for the next request is read, and the routed service is selected according to the version number parameter rule.

Configure the version number to distinguish between the grayscale version and the default normal version; customize the interceptor, manage the version number or other identification parameters to be passed in the request; customize the service selection policy to identify the routing service based on the version; if the grayscale service does not exist, select the default service based on the rule

II. Version configuration

Configure two services on the node12-server cluster: version 7.0.0 on port 8002 and version 7.0.1 on port 8003 to test the grayscale version selection.

8002 Servic

Eureka: metadata-map: version: v7.0.0

8003 Servic

Eureka: metadata-map: version: v7.0.1

Eureka registry, list of services:

III. Parameter transfer

Microservice manages the Feign request interceptor between services by implementing the RequestInterceptor interface. Before the request is routed to the service, it can perform some processing operations on the request, such as passing the version number, user Token and other request first-class attributes.

/ * request interceptor * / @ Componentpublic class GrayReqInterceptor implements RequestInterceptor {private static final String VERSION_KEY = "versionId"; / * handle the problem of carrying request header parameters * / @ Override public void apply (RequestTemplate requestTemplate) {HttpServletRequest request = ((ServletRequestAttributes) RequestContextHolder.getRequestAttributes ()) .getRequest (); String versionId = request.getHeader (VERSION_KEY) If (StringUtils.isNotEmpty (versionId)) {requestTemplate.header (VERSION_KEY,versionId);}

Here, a versionId parameter is passed as the core identity of the next request routing service.

IV. Grayscale rules

Add the version number to be accessed in the Header of the request header, route all requested grayscale services if there is a matching service, and return the default service if not.

@ Configurationpublic class GrayRule extends ZoneAvoidanceRule {@ Bean public GrayReqInterceptor grayReqInterceptor () {return new GrayReqInterceptor ();} private static final String VERSION_KEY = "versionId"; @ Override public Server choose (Object key) {HttpServletRequest request = ((ServletRequestAttributes) RequestContextHolder.getRequestAttributes ()) .getRequest (); String versionId = request.getHeader (VERSION_KEY) / / Service matching List serverList = this.getPredicate (). GetEligibleServers (this.getLoadBalancer (). GetAllServers (), key); Server toServer = getServer (serverList,versionId); if (toServer! = null) {return toServer;} else {return getServer (serverList,GrayConstant.VERSION_DEF);}} private Server getServer (List serverList,String version) {Server toServer = null For (Server server: serverList) {Map metadata = ((DiscoveryEnabledServer) server). GetInstanceInfo (). GetMetadata (); String metaVersion = metadata.get ("version"); if (! StringUtils.isEmpty (metaVersion)) {if (metaVersion.equals (version)) {toServer = server } return toServer;}}

In the actual process, the selection of services is very complex. If there is no grayscale service, it is necessary to make rules for service matching according to the actual situation, such as response time, or default polling.

It is more important to note that once the secondary encapsulation of the underlying API is used, the overall project will be affected by the framework version upgrade and need to pay continuous attention to the framework environment.

Fifth, testing process

1. Start related services and observe the list of registry services

two。 Request the interface of the 8001 service with the version number

3. Observe routing services with different version numbers

4. Do not carry the version number, observe the default service selection

Sixth, source code address GitHub address: know a smile https://github.com/cicadasmile/spring-cloud-baseGitEE address: know a smile https://gitee.com/cicadasmile/spring-cloud-base so far, on the "micro-service mode how to achieve grayscale release mode" learning is over, hope to be able to solve everyone's doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.