WO2022252856A1 - 一种全链路的灰度发布方法及灰度发布*** - Google Patents
一种全链路的灰度发布方法及灰度发布*** Download PDFInfo
- Publication number
- WO2022252856A1 WO2022252856A1 PCT/CN2022/087858 CN2022087858W WO2022252856A1 WO 2022252856 A1 WO2022252856 A1 WO 2022252856A1 CN 2022087858 W CN2022087858 W CN 2022087858W WO 2022252856 A1 WO2022252856 A1 WO 2022252856A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- service request
- grayscale
- service
- gray
- policy
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 56
- 238000007781 pre-processing Methods 0.000 claims description 9
- 238000012216 screening Methods 0.000 abstract 1
- 235000014510 cooky Nutrition 0.000 description 7
- 238000012795 verification Methods 0.000 description 7
- 238000010586 diagram Methods 0.000 description 5
- 238000004040 coloring Methods 0.000 description 4
- 238000004519 manufacturing process Methods 0.000 description 4
- 241000287219 Serinus canaria Species 0.000 description 1
- 241000529895 Stercorarius Species 0.000 description 1
- 230000005856 abnormality Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000010186 staining Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/20—Natural language analysis
- G06F40/279—Recognition of textual entities
- G06F40/289—Phrasal analysis, e.g. finite state techniques or chunking
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/04—Processing captured monitoring data, e.g. for logfile generation
- H04L43/045—Processing captured monitoring data, e.g. for logfile generation for graphical visualisation of monitoring data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1031—Controlling of the operation of servers by a load balancer, e.g. adding or removing servers that serve requests
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
Definitions
- the present application relates to the technical field of gray scale release, and in particular to a full-link gray scale release method and gray scale release system.
- the current grayscale release is mainly aimed at a single service, deploying a small-scale grayscale service in addition to the existing stable service. Then through traffic control, part of the traffic is directed to the grayscale service for grayscale verification before full release. If the verification fails, all traffic can be switched to stable services immediately, canceling the canary publishing process. If the verification is successful, the new version will be fully released, upgraded to a stable cluster in the production environment, and the grayscale release process will be completed.
- the present application provides a full-link gray scale release method and gray scale release system to solve the problem that the prior art only supports gray scale online of a single service.
- the first aspect of the present application provides a full-link grayscale publishing method, which is applied to a grayscale publishing system, wherein the grayscale publishing system includes at least a microservice gateway and a sidecar load balancing component, and the full-link Gray release methods, including:
- the microservice gateway receives a service request initiated by a user
- the microservice gateway matches the service request with the grayscale policy in the grayscale configuration file
- the microservice gateway marks the service request with a color
- the microservice gateway issues the service request
- the sidecar load balancing component intercepts the delivered service request, and judges whether there is a color mark in the service request;
- the sidecar load balancing component determines that there is a color mark in the service request, it will filter out instances of the requested service in the current grayscale release version, and forward the service request.
- the grayscale policy includes multiple grayscale sub-strategies
- the microservice gateway matches the service request with the grayscale policy in the grayscale configuration file ,include:
- the micro-service gateway matches a plurality of information in the service request with corresponding gray-scale sub-strategies in the gray-scale configuration file, and obtains a matching result corresponding to each gray-scale sub-strategy;
- the microservice gateway marks the service request with color, including:
- the microservice gateway adds a color mark corresponding to the grayscale policy to the header of the service request.
- the microservice gateway after the microservice gateway receives the service request initiated by the user, it further includes:
- the micro-service gateway pre-processes the service request; wherein, the pre-processing includes at least user authentication and user authentication;
- the service request passes the user authentication and user authentication, for the preprocessed service request, perform the matching of the service request with the grayscale policy in the grayscale configuration file.
- full-link grayscale release method it also includes:
- the sidecar load balancing component determines that there is a color mark on the service request, or the instance version of the requested service is not filtered out in the current grayscale release, it will randomly select an instance from the instance list in the registration center for all forwarding of service requests.
- the second aspect of the present application provides a grayscale release system, including:
- the microservice gateway is configured to receive a service request initiated by a user, and match the service request with the grayscale policy in the grayscale configuration file, and is used to match the service request with the grayscale policy successfully, as The service request is marked with a color, and the service request is issued;
- the sidecar load balancing component is used to intercept the delivered service request, and judge whether there is a color mark on the service request, and to filter out the requested service in the current gray area when it is judged that the service request has a color mark.
- An instance of the released version is used to forward the service request.
- the grayscale policy includes a plurality of grayscale sub-policies
- the microservice gateway executes the process of matching the service request with the grayscale policy in the grayscale configuration file.
- the microservice gateway executes the color marking of the service request, it is used to:
- the microservice gateway is also used for:
- the microservice gateway will For a service request, perform the matching of the service request with the grayscale policy in the grayscale configuration file.
- the sidecar load balancing component is also used for:
- an instance is randomly selected from the instance list of the registration center to forward the service request.
- the grayscale publishing system includes at least a microservice gateway and a sidecar load balancing component, which receives service requests initiated by users through the microservice gateway, and matches the service requests with the grayscale policies in the grayscale configuration file. If the service request matches the grayscale policy successfully, the service request is marked with a color, and finally the service request is issued.
- the sidecar load balancing component intercepts the delivered service request, and judges whether there is a color mark on the service request. If it is determined that there is a color mark in the service request, the instance of the requested service in the current grayscale release version is screened out, and the service request is forwarded. Therefore, multiple grayscale policies can be satisfied, and the process of grayscale release can be effectively controlled, so that multiple services can be simultaneously released in grayscale, and full-link grayscale release can be realized.
- FIG. 1 is a flow chart of a full-link grayscale publishing method provided by an embodiment of the present application
- FIG. 2 is a flowchart of a method for matching a grayscale strategy provided by another embodiment of the present application
- FIG. 3 is a topology diagram of traffic flow when the service works normally in an example
- Fig. 4 is a topological diagram of the traffic of the service under the existing grayscale release in an example
- Fig. 5 is a topological diagram of the traffic of a gray scale publishing service using the method provided by this application in an example
- FIG. 6 is a flow chart for publishing the method provided by the present application provided by another embodiment of the present application.
- FIG. 7 is a flow chart of another full-link grayscale release method provided by another embodiment of the present application.
- Fig. 8 is a schematic structural diagram of a grayscale release system provided by another embodiment of the present application.
- relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any relationship between these entities or operations. an actual relationship or order.
- the term “comprises”, “comprises” or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article or apparatus comprising a set of elements includes not only those elements but also items not expressly listed other elements, or also include elements inherent in such a process, method, article, or apparatus.
- an element defined by the phrase “comprising a " does not exclude the presence of additional identical elements in the process, method, article or apparatus comprising said element.
- an embodiment of the present application provides a full-link gray scale publishing method, which is applied to a gray scale publishing system.
- the gray release system includes at least a microservice gateway and a sidecar load balancing component.
- a full-link gray scale release method provided by the embodiment of this application specifically includes the following steps:
- the microservice gateway receives a service request initiated by a user.
- the microservice gateway serves as the same entry in the microservice embodiment.
- the microservice system includes multiple microservices.
- the traffic will first enter the microservice gateway, and the service request will be processed uniformly through the gateway service.
- the microservice gateway wants to forward the service request to the downstream system, step S102 is performed first.
- step S101 after step S101 is executed, it may further be executed first: the microservice gateway preprocesses the service request.
- the preprocessing includes at least user authentication and user authentication. Certainly, processing such as routing and forwarding of the service request may also be included.
- step S102 is executed for the preprocessed service request.
- the microservice gateway matches the service request with the grayscale policy in the grayscale configuration file.
- grayscale release in addition to the production environment stable cluster, an additional small-scale grayscale cluster is deployed, and through traffic control, part of the traffic is introduced into the grayscale cluster for full-scale production release. Gray scale verification. If the verification fails, all traffic can be immediately switched back to the original stable cluster, canceling the gray release process. If the verification is successful, the new version will be fully released and upgraded to a stable cluster in the production environment, that is, all traffic will be introduced into the new version to complete the grayscale release process.
- the grayscale configuration file is pre-created.
- the grayscale publishing system may also include a configuration center. Therefore, grayscale configuration files can be pre-created in the configuration center.
- the grayscale configuration file can be as follows:
- grayName grayscale release name
- plans grayscale release plan
- id unique identifier of grayscale plan
- color color mark
- relationship grayscale strategy execution relationship, supporting or, and, not
- strategies grayscale strategy collection
- key grayscale type, including header, cookie, param, path, weight
- value policy value
- planServices grayscale publishing service collection
- planId grayscale plan unique identifier
- services grayscale service collection
- service service name
- version number version number
- the grayscale strategy is mainly formulated according to the characteristics of the service request, and the grayscale strategy type can support header, cookie, param, path, and weight.
- the grayscale strategy type can support header, cookie, param, path, and weight.
- the policy type is Header
- the corresponding header name and header value can be set in the grayscale policy to match the service request.
- the grayscale strategy includes multiple grayscale sub-strategies.
- a specific implementation of step S102, as shown in FIG. 2 includes the following steps:
- the micro-service gateway matches multiple pieces of information in the service request with corresponding gray-scale sub-policies in the gray-scale configuration file, and obtains a matching result corresponding to each gray-scale sub-strategy.
- a grayscale strategy may be set with multiple grayscale sub-strategies at the same time.
- each grayscale sub-strategy corresponds to a different strategy type, such as header, cookie, param, path, and weight.
- the corresponding information in the service request is matched with the corresponding gray-scale sub-strategy, and the matching result corresponding to each gray-scale sub-strategy is obtained.
- the execution relationship includes or relationship, and relationship and non-relationship, that is, or, and, not three kinds of relationships.
- each gray-scale sub-strategy has a corresponding matching result, and finally a matching result needs to be obtained, that is, whether the service request is successfully matched. Therefore, in the embodiment of the present application, the matching result corresponding to each gray-scale sub-strategy can determine the final matching result between the service request and the gray-scale policy according to the execution relationship between each gray-scale sub-strategy.
- the execution relationship of the grayscale sub-policy when matching according to the header and cookie at the same time, when the execution relationship of the grayscale sub-policy is set to or relationship, then there is a grayscale sub-policy hit in the header and cookie, that is, it matches the service request, and the final matching result is The match was successful. If the execution relationship of the grayscale policy is set to AND relationship, then the two grayscale sub-policies of header and cookie must all hit before the final matching result can be determined as a successful match. If the execution relationship of the grayscale policy is set to non-relationship, the final matching result can be determined as a successful match only if the two policies of the header and the cookie do not match.
- the microservice gateway judges whether the service request matches the grayscale policy in the grayscale configuration file successfully.
- step S104 if the service request matches the grayscale policy successfully, step S104 is performed. What needs to be said is that if the service request matches the grayscale policy successfully, it will be processed as a normal service request, that is, step S105 can be directly executed.
- the microservice gateway marks the service request with a color.
- the microservice gateway sends a service request.
- the microservice gateway will send the processed service request to the downstream microservice project to obtain the requested service.
- the sidecar load balancing component intercepts the delivered service request, and determines whether the service request has a color mark.
- the service request issued by the microservice gateway is intercepted and processed by the sidecar load balancing component.
- the microservice request can be preprocessed first, such as generating link information, performing security verification on the service request, and then judging whether there is a color mark on the service request.
- step S107 is executed.
- the sidecar load balancing component screens out instances of the requested service in the current grayscale release version, and forwards the service request.
- the sidecar load balancing component forwards the service request, if there is a dye mark in the service request, it will filter the instance list in the registration center according to the grayscale instance won in the grayscale configuration file and the current grayscale release version. Find an example that matches the current grayscale release version, and forward the service request.
- the microservice gateway provided by the embodiment of this application performs grayscale policy matching on service requests, and when the matching is successful, the service request is dyed, and then it is determined whether the server request needs to be introduced into the grayscale release version according to the coloring of the service request In the service, so as to realize the flow control of simultaneous gray scale release of multiple services.
- FIG. 3 shows the traffic topology of the four services when grayscale publishing is not performed: the gateway calls service A; service A calls services B and C; service B calls services C and D; service C calls service D .
- the gateway calls service A v1.0.0; service A v1.0.0 calls services B and C respectively Versions v1.0.0 and v1.1.0 of B service; v1.0.0 and v1.1.0 of B service call C service v1.0.0 and v1.1.0, and D service respectively; C service v1.0.0 and v1.1.0 call respectively D service.
- the gateway calls the A service v1.0.0; the A service v v1.0.0 will be based on the grayscale configuration file, for the traffic Matching of the grayscale publishing strategy.
- the gateway calls the A service v1.0.0; the A service v v1.0.0 will be based on the grayscale configuration file, for the traffic Matching of the grayscale publishing strategy.
- the traffic identified by staining will only call the v1.0.0 version of B and C services; B service v1.0.0 and v1.1.0 will call C and D services; C service v1.0.0 and v1.1.0 will call C and D services.
- grayscale service refers to the service version released by grayscale.
- the grayscale configuration file can be cleared or deleted directly, and no traffic will enter the newly released service version at this time middle.
- the embodiment of the present application provides a full-link gray scale release method, which is applied to a gray scale release system.
- the grayscale publishing system includes at least a microservice gateway and a sidecar load balancing component, which receives service requests initiated by users through the microservice gateway, and matches the service requests with the grayscale policies in the grayscale configuration file. If the service request matches the grayscale policy successfully, the service request is marked with a color, and finally the service request is issued.
- the sidecar load balancing component intercepts the delivered service request, and judges whether there is a color mark on the service request. If it is determined that there is a color mark in the service request, the instance of the requested service in the current grayscale release version is screened out, and the service request is forwarded. Therefore, multiple grayscale policies can be satisfied, and the process of grayscale release can be effectively controlled, so that multiple services can be simultaneously released in grayscale, and full-link grayscale release can be realized.
- the gray release system includes at least a microservice gateway and a sidecar load balancing component.
- the full-link grayscale release method provided by the embodiment of the present application includes the following steps:
- the microservice gateway receives a service request initiated by a user.
- the microservice gateway may further preprocess the service request.
- the preprocessing includes at least user authentication and user authentication. And if the service request passes the user authentication and user authentication, step S702 is executed for the preprocessed service request.
- the microservice gateway matches the service request with the grayscale policy in the grayscale configuration file.
- step S702 reference may be made to the specific implementation process of step S102 accordingly, which will not be repeated here.
- the microservice gateway judges whether the service request matches the grayscale policy in the grayscale configuration file successfully.
- step S704 if it is judged that the service request matches the grayscale policy in the grayscale configuration file successfully, then execute step S704; if it is judged that the service request does not match successfully with the grayscale strategy in the grayscale configuration file, then execute step S705.
- the microservice gateway adds a color mark corresponding to the grayscale policy in the header of the service request.
- coloring of the service request is realized by adding a color mark to the header of the service request. Moreover, if it matches with different grayscale policies, the color mark corresponding to the grayscale policy is used to indicate the grayscale policy matched by the service request.
- the microservice gateway sends a service request.
- the sidecar load balancing component intercepts the delivered service request, and judges whether the service request has a color mark.
- step S707 is performed; if it is determined that the service request does not have a coloring mark, then the service request is processed normally, so step S710 is performed at this time.
- step S707 refers to step S107 accordingly, which will not be repeated here.
- the sidecar load balancing component determines whether an instance of the requested service in the current gray release version is filtered out.
- step S709 is executed. If it is determined that no instance of the requested service in the current gray-scale release version is found, the service request can only be processed normally, so step S710 is executed at this time.
- FIG. 8 Another embodiment of the present application provides a grayscale release system, as shown in Figure 8, including:
- the microservice gateway 801 is used to receive the service request initiated by the user, match the service request with the grayscale policy in the grayscale configuration file, and mark the service request with a color when the service request matches the grayscale policy successfully , and send a service request.
- the sidecar load balancing component 802 is used to intercept the issued service request, and judge whether the service request has a color mark, and is used to filter out the instance of the requested service in the current grayscale release version when it is judged that the service request has a color mark , to forward the service request.
- the grayscale policy includes multiple grayscale sub-strategies, and the microservice gateway executes matching the service request with the grayscale policy in the grayscale configuration file , for:
- the execution relationship includes an OR relationship, an AND relationship, and a non-relationship.
- microservice gateway executes color-marking service requests, it is used to:
- the microservice gateway is also used for:
- the preprocessing includes at least user authentication and user authentication. And if the service request passes the user authentication and user authentication, the microservice gateway will match the service request with the grayscale policy in the grayscale configuration file for the preprocessed service request.
- the sidecar load balancing component is also used for:
- an instance is randomly selected from the instance list in the registration center to forward the service request.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Mining & Analysis (AREA)
- Theoretical Computer Science (AREA)
- Computational Linguistics (AREA)
- Audiology, Speech & Language Pathology (AREA)
- General Health & Medical Sciences (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Artificial Intelligence (AREA)
- Health & Medical Sciences (AREA)
- Computer And Data Communications (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
本申请提供了一种全链路的灰度发布方法及灰度发布***,所述灰度发布***至少包括微服务网关以及边车负载均衡组件,所述方法应用于所述灰度发布***,包括:所述微服务网关接收用户发起的服务请求;所述微服务网关将所述服务请求与灰度配置文件中的灰度策略进行匹配;若所述服务请求与所述灰度策略匹配成功,则所述微服务网关为所述服务请求打上颜色标记;所述微服务网关下发所述服务请求;所述边车负载均衡组件拦截下发的所述服务请求,并判断所述服务请求是否存在颜色标记;所述边车负载均衡组件若判断出所述服务请求存在颜色标记,则筛选出所请求的服务在当前灰度发布版本的实例,进行所述服务请求的转发。从而可以同时实现全链路的灰度发布。
Description
本申请要求于2021年06月01日提交中国专利局、申请号为202110610163.1、发明名称为“一种全链路的灰度发布方法及灰度发布***”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
本申请涉及灰度发布技术领域,特别涉及一种全链路的灰度发布方法及灰度发布***。
近几年,随着用户的迅速增长和业务的快速发展,对开发人员要求越来越高,一方面要求为用户提供稳定的服务,一方面要求进行快速业务迭代。所以,基于***稳定性和快速业务迭代的综合考虑,现在一般采用灰度发布的凡是,发布新的版本。
目前的灰度发布主要是针对单个服务,在已存在的稳定服务之外,额外部署一个小规模的灰度服务。然后通过流量控制,将部分流量引导到灰度服务中,进行全量发布前的灰度验证。如果验证失败,可立刻将所有流量切换至稳定服务中,取消灰度发布过程。如果验证成功,则将新版本进行全量发布,升级至生产环境稳定集群,完成灰度发布过程。
但是现今单个业务功能设计的微服务接口数、服务化调用链路长度都在迅速增加,所以经常出现多个服务同时需要发布新版本的情况,而现有的方式都是针对单个服务进行灰度发布,无法实现多个服务同时进行灰度发布,无法很好地满足快速业务迭代的要求。
发明内容
基于上述现有技术的不足,本申请提供了一种全链路的灰度发布方法及灰度发布***,以解决现有技术仅支持单一服务灰度上线的问题。
为了实现上述目的,本申请提供了以下技术方案:
本申请第一方面提供了一种全链路的灰度发布方法,应用于灰度发布***,其中,所述灰度发布***至少包括微服务网关以及边车负载均衡组件,所述全链路的灰度发布方法,包括:
所述微服务网关接收用户发起的服务请求;
所述微服务网关将所述服务请求与灰度配置文件中的灰度策略进行匹配;
若所述服务请求与所述灰度策略匹配成功,则所述微服务网关为所述服务请求打上颜色标记;
所述微服务网关下发所述服务请求;
所述边车负载均衡组件拦截下发的所述服务请求,并判断所述服务请求是否存在颜色标记;
所述边车负载均衡组件若判断出所述服务请求存在颜色标记,则筛选出所请求的服务在当前灰度发布版本的实例,进行所述服务请求的转发。
可选地,在上述的全链路的灰度发布方法中,灰度策略包括多个灰度子策略,所述微服务网关将所述服务请求与灰度配置文件中的灰度策略进行匹配,包括:
所述微服务网关将所述服务请求中的多个信息,分别与所述灰度配置文件中的对应的灰度子策略进行匹配,得到每个所述灰度子策略对应的匹配结果;
基于各个所述灰度子策略间的执行关系,以及每个所述灰度子策略对应的匹配结果,确定所述服务请求与所述灰度策略的最终匹配结果;其中,所述执行关系包括或关系、与关系以及非关系。
可选地,在上述的全链路的灰度发布方法中,所述微服务网关为所述服务请求打上颜色标记,包括:
所述微服务网关在所述服务请求的头部中添加与所述灰度策略对应的颜色标记。
可选地,在上述的全链路的灰度发布方法中,所述微服务网关接收用户发起的服务请求之后,还包括:
所述微服务网关对所述服务请求进行预处理;其中,所述预处理至少包括用户认证以及用户鉴权;
若所述服务请求通过用户认证以及用户鉴权,则针对预处理后的所述服务请求,执行所述将所述服务请求与灰度配置文件中的灰度策略进行匹 配。
可选地,在上述的全链路的灰度发布方法中,还包括:
所述边车负载均衡组件若判断出所述服务请求存在颜色标记,或未筛选到所请求的服务在当前灰度发布的实例版本,则随机从注册中心的实例列表中挑选出一个实例进行所述服务请求的转发。
本申请第二方面提供了一种灰度发布***,包括:
微服务网关,用于接收用户发起的服务请求,并将所述服务请求与灰度配置文件中的灰度策略进行匹配,以及用于在所述服务请求与所述灰度策略匹配成功,为所述服务请求打上颜色标记,并下发所述服务请求;
边车负载均衡组件,用于拦截下发的所述服务请求,并判断所述服务请求是否存在颜色标记,以及用于判断出所述服务请求存在颜色标记时,筛选出所请求的服务在当前灰度发布版本的实例,进行所述服务请求的转发。
可选地,在上述的灰度发布***中,所述灰度策略包括多个灰度子策略,所述微服务网关执行所述将所述服务请求与灰度配置文件中的灰度策略进行匹配时,用于:
将所述服务请求中的多个信息,分别与所述灰度配置文件中的对应的灰度子策略进行匹配,得到每个所述灰度子策略对应的匹配结果,并基于各个所述灰度子策略间的执行关系,以及每个所述灰度子策略对应的匹配结果,确定所述服务请求与所述灰度策略的最终匹配结果;其中,所述执行关系包括或关系、与关系以及非关系。
可选地,在上述的灰度发布***中,所述微服务网关执行所述为所述服务请求打上颜色标记时,用于:
在所述服务请求的头部中添加与所述灰度策略对应的颜色标记。
可选地,在上述的灰度发布***中,所述微服务网关,还用于:
对所述服务请求进行预处理;其中,所述预处理至少包括用户认证以及用户鉴权;若所述服务请求通过用户认证以及用户鉴权,则所述微服务网关针对预处理后的所述服务请求,执行所述将所述服务请求与灰度配置文件中的灰度策略进行匹配。
可选地,在上述的灰度发布***中,所述边车负载均衡组件,还用于:
在判断出所述服务请求存在颜色标记,或未筛选到所请求的服务在当前灰度发布的实例版本时,随机从注册中心的实例列表中挑选出一个实例进行所述服务请求的转发。
本申请提供的一种全链路的灰度发布方法,应用于灰度发布***。其中,灰度发布***至少包括微服务网关以及边车负载均衡组件,该通过微服务网关接收用户发起的服务请求,并将所述服务请求与灰度配置文件中的灰度策略进行匹配。若服务请求与所述灰度策略匹配成功,则为服务请求打上颜色标记,最后将服务请求下发。由边车负载均衡组件拦截下发的服务请求,并判断所述服务请求是否存在颜色标记。若判断出服务请求存在颜色标记,则筛选出所请求的服务在当前灰度发布版本的实例,进行服务请求的转发。所以可以满足多条灰度策略,并且实现了对灰度发布的流程的有效控制,从而可以支持多个服务同时进行灰度发布,实现全链路灰度发布。
为了更清楚地说明本发明实施例或现有技术中的技术方案,下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍,显而易见地,下面描述中的附图仅仅是本发明的实施例,对于本领域普通技术人员来讲,在不付出创造性劳动的前提下,还可以根据提供的附图获得其他的附图。
图1为本申请实施例提供的一种全链路的灰度发布方法的流程图;
图2为本申请另一实施例提供的一种匹配灰度策略的方法的流程图;
图3为一示例中服务正常工作时的流量的拓扑图;
图4为一示例中现有灰度发布下服务的流量的拓扑图;
图5为一示例中使用本申请提供的方法进行灰度发布的服务的流量的拓扑图;
图6为本申请另一实施例提供的实现本申请提供的方法进行发布的流程图;
图7为本申请另一实施例提供的另一种全链路的灰度发布方法的流程图;
图8为本申请另一实施例提供的一种灰度发布***的结构示意图。
下面将结合本申请实施例中的附图,对本申请实施例中的技术方案进行清楚、完整地描述,显然,所描述的实施例仅仅是本申请一部分实施例,而不是全部的实施例。基于本申请中的实施例,本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例,都属于本申请保护的范围。
在本申请中,诸如第一和第二等之类的关系术语仅仅用来将一个实体或者操作与另一个实体或操作区分开来,而不一定要求或者暗示这些实体或操作之间存在任何这种实际的关系或者顺序。而且术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含,从而使得包括一系列要素的过程、方法、物品或者设备不仅包括那些要素,而且还包括没有明确列出的其他要素,或者是还包括为这种过程、方法、物品或者设备所固有的要素。在没有更多限制的情况下,由语句“包括一个……”限定的要素,并不排除在包括所述要素的过程、方法、物品或者设备中还存在另外的相同要素。
本申请实施例提供了一种全链路的灰度发布方法,应用于灰度发布***。其中,灰度发布***至少包括微服务网关以及边车负载均衡组件。如图1所示,本申请实施例提供的一种全链路的灰度发布方法,具体包括以下步骤:
S101、微服务网关接收用户发起的服务请求。
需要说明的是,本申请实施例中微服务网关作为微服务体现中的同一入口。微服务体系中包括有多个微服务,当用户发送某个微服务的服务请求时,流量首先会进入微服务网关中,通过网关服务对服务请求进行统一处理。当微服务网关要将服务请求转发到下游***中时,则先执行步骤S102。
可选地,在本申请另一实施例中,在执行步骤S101之后,还可以进一步先执行:微服务网关对所述服务请求进行预处理。
其中,预处理至少包括用户认证以及用户鉴权。当然还可以包括对服务请求进行路由转发等处理。
需要说明的是,在本申请实施例中若服务请求通过用户认证以及用户鉴权,则针对预处理后的服务请求,执行步骤S102。
S102、微服务网关将服务请求与灰度配置文件中的灰度策略进行匹配。
需要说明的是,灰度发布大致原理为:在生产环境稳定集群之外,额外部署一个小规模的灰度集群,并通过流量控制,将部分流量引入到灰度集群,进行生产全量发布前的灰度验证。如果验证失败,可立刻将所有流量切回原本存在的稳定集群,取消灰度发布过程。如果验证成功,则将新版本进行全量发布升级至生产环境稳定集群,即将所有流量引入新版本中,完成灰度发布过程。
本申请实施例中,支持多个服务同时进行灰度发布,所以本申请通过将服务请求与灰度配置文件进行匹配的方式,确定服务请求是否需要引入到新版本中。
需要说明的是,灰度配置文件为预先创建的。可选地,灰度发布***还可以包括配置中心。所以可以在配置中心中预先创建灰度配置文件。可选地,灰度配置文件,具体可以如下:
其中,grayName:灰度发布名称、plans:灰度发布计划;id:灰度计划唯一标识;color:颜色标记;relationship:灰度策略执行关系,支持or,and,not;strategys:灰度策略集合;key:灰度类型,包括header,cookie,param,path,weight;value:策略值;planServices:灰度发布服务集合;planId:灰度计划唯一标识;services:灰度服务集合;service:服务名;version:版本号。
其中,灰度策略主要是针对服务请求的特征进行制定,灰度策略类型可以支持header,cookie,param,path,weight。例如策略类型是Header时,则可以灰度策略可以设定相应的header name以及header value对服务请求进行匹配。
可选地,本申请另一实施例中,灰度策略包括多个灰度子策略,在本申请实施例中,步骤S102的一种具体实施方式,如图2所示,包括以下步骤:
S201、微服务网关将服务请求中的多个信息,分别与灰度配置文件中的对应的灰度子策略进行匹配,得到每个灰度子策略对应的匹配结果。
需要说明的是,在本申请实施例中,灰度策略可以同时设定有多个灰度子策略。并且,每个灰度子策略对应不同的策略类型,如header,cookie,param,path,weight。
所以在匹配过程中,将服务请求中相应的信息与对应的灰度子策略进行匹配,得到每个灰度子策略对应的匹配结果。
S202、基于各个灰度子策略间的执行关系,以及每个灰度子策略对应的匹配结果,确定服务请求与灰度策略的最终匹配结果。
其中,执行关系包括或关系、与关系以及非关系,即or、and、not三种关系。
由于存在多个灰度子策略,每个灰度子策略有对应的匹配结果,而最终需要得到一个匹配结果,即得到服务请求是否匹配成功。所以,在本申请实施例中,每个灰度子策略对应的匹配结果,可以按照各个灰度子策略间的执行关系,确定服务请求与灰度策略的最终匹配结果。
例如,当同时按照header以及cookie进行匹配,当灰度子策略的执行关 系设置为或关系时,那么header和cookie中有一条灰度子策略命中,即与服务请求相匹配,则最终匹配结果为匹配成功。如果灰度策略执行关系设置为与关系时,那么header和cookie两条灰度子策略需全部命中才可以将最终匹配结果确定为匹配成功。如果灰度策略执行关系设置为非关系时,那么header和cookie两条策略都不命中才可以将最终匹配结果确定为匹配成功。
S103、微服务网关判断服务请求与灰度配置文件中的灰度策略是否匹配成功。
其中,若服务请求与灰度策略匹配成功,则执行步骤S104。需要说的是,若服务请求与灰度策略匹配成功,则按正常的服务请求进行处理,即可以直接执行步骤S105。
S104、微服务网关为服务请求打上颜色标记。
S105、微服务网关下发服务请求。
需要说明的是,无论服务请求是否成功匹配,并进行染色。微服务网关都会将处理后的服务请求下发至下游的微服务项目中,以能获得所请求的服务。
S106、边车负载均衡组件拦截下发的服务请求,并判断服务请求是否存在颜色标记。
需要说明的是,本申请实施例中,通过边车负载均衡组件拦截微服务网关下发的服务请求,并对其处理。
可选的,在截下发的服务请求,可以先对微服务请求进行预处理后,例如生成链路信息、对服务请求进行安全校验等处理,再判断服务请求是否存在颜色标记。
其中,若判断出服务请求存在颜色标记,则执行步骤S107。
S107、边车负载均衡组件筛选出所请求的服务在当前灰度发布版本的实例,进行服务请求的转发。
需要说明的是,在本申请实施例中,支持多个服务同时进行灰度发布,但每次同一个服务只可以灰度上线一个版本。边车负载均衡组件在就行服务请求转发时,若服务请求存在染色标记,则根据灰度配置文件中赌赢的灰度实例以及当前灰度发布版本,对注册中心的实例列表进行实例的过滤,找到符合当前灰度发布版本的示例,进行服务请求的转发。
因此,本申请实施例提供的通过微服务网关对服务请求进行灰度策略 的匹配,并在匹配成功时对服务请求进行染色,后续根据服务请求染色确定是否需要将该服务器请求引入灰度发布版本的服务中,从而很好地实现对多服务同时灰度发布时的流量控制。
例如,存在A、B、C、D四个服务,其中,A服务为网关服务。在不进行灰度发布时,四个服务的流量的拓扑图如图3所示:网关调用A服务;A服务调用B、C两个服务;B服务调用C、D服务;C服务调用D服务。
未使用本申请实施例提供的方式进行版本上限时,四个服务的流量的拓扑图如图4所示:网关调用A服务v1.0.0版本;A服务v1.0.0版本会分别调用B、C服务的v1.0.0版本和v1.1.0版本;B服务v1.0.0以及v1.1.0版本分别调用C服务v1.0.0版本和v1.1.0、以及D服务;C服务v1.0.0以及v1.1.0版本分别调用D服务。
在使用本申请实施例提供的方法时,四个服务的流量的拓扑图,如图5所示:网关调用A服务v1.0.0;A服务v v1.0.0会根据灰度配置文件,针对流量进行灰度发布策略的匹配。对于染色成功的流量怎只会调用B、C服务v1.1.0版本。染色识别的流量则只会调用B、C服务的v1.0.0版本;B服务v1.0.0以及v1.1.0版本调用C,D服务;C服务v1.0.0以及v1.1.0版本调用C,D服务。
可选地,在采用本申请实施例提供的全链路的灰度发布方法进行发布上线时,大致的步骤如图6所示,包括以下步骤:
S601、在配置中心中创建灰度配置文件。
S602、配置灰度策略以及灰度服务。
其中,灰度服务指代灰度发布的服务版本。
S603、在配置中心编辑完成后,点击发布按钮,灰度计划开始生效。
S604、灰度发布配置文件生效期间,动态调配灰度策略和策略值灰度,并使用Jaeger或zipkin观察灰度服务是否正常。
需要说明的是,当启动灰度发布后,当观察到新发布的业务***出现异常时,可以直接将灰度配置文件清空或删除,此时将不会有任何流量进入到新发布的服务版本中。
S605、当灰度发布计划执行一段时间后,观察灰度的服务业务是否正常,如果都确认正常后,首先将灰度权重比例切换到100%,并且将其他灰度策略删除。
本申请实施例提供的一种全链路的灰度发布方法,应用于灰度发布***。其中,灰度发布***至少包括微服务网关以及边车负载均衡组件,该通过微服务网关接收用户发起的服务请求,并将所述服务请求与灰度配置文件中的灰度策略进行匹配。若服务请求与所述灰度策略匹配成功,则为服务请求打上颜色标记,最后将服务请求下发。由边车负载均衡组件拦截下发的服务请求,并判断所述服务请求是否存在颜色标记。若判断出服务请求存在颜色标记,则筛选出所请求的服务在当前灰度发布版本的实例,进行服务请求的转发。所以可以满足多条灰度策略,并且实现了对灰度发布的流程的有效控制,从而可以支持多个服务同时进行灰度发布,实现全链路灰度发布。
本申请另一实施例提供了另一种全链路的灰度发布方法,同样应用于灰度发布***。其中,灰度发布***至少包括微服务网关以及边车负载均衡组件。如图7所示,本申请实施例提供的全链路的灰度发布方法,包括以下步骤:
S701、微服务网关接收用户发起的服务请求。
同样,在执行步骤S701之后,微服务网关还可以进一步对服务请求进行预处理。
其中,所述预处理至少包括用户认证以及用户鉴权。并且若服务请求通过用户认证以及用户鉴权,则针对预处理后的服务请求,执行所步骤S702。
S702、微服务网关将服务请求与灰度配置文件中的灰度策略进行匹配。
需要说明的是,步骤S702的具体实施过程可相应地参考步骤S102的具体实施过程,此处不再赘述。
S703、微服务网关判断服务请求与灰度配置文件中的灰度策略是否匹配成功。
其中,若判断出服务请求与灰度配置文件中的灰度策略匹配成功,则执行步骤S704,若判断出服务请求与灰度配置文件中的灰度策略未匹配成功,则执行步骤S705。
S704、微服务网关在服务请求的头部中添加与灰度策略对应的颜色标记。
在本申请实施例中,采用在服务请求的头部中添加颜色标记的方式实现对服务请的染色。并且,与不同的灰度策略相匹配,则采用灰度策略对应的颜色标记,以能表示出服务请求所匹配的灰度策略。
S705、微服务网关下发服务请求。
S706、边车负载均衡组件拦截下发的所述服务请求,并判断服务请求是否存在颜色标记。
其中,若判读出服务请求存在染色标记,则执行步骤S707;若判读出服务请求不存在染色标记,则对服务请求进行正常的处理,所以此时执行步骤S710。
S707、筛选出所请求的服务在当前灰度发布版本的实例。
需要说明的是,步骤S707的具体实施方式相应地参考步骤S107,此处不再赘述。
S708、边车负载均衡组件判断是否筛选到所请求的服务在当前灰度发布版本的实例。
其中,若判断出筛选到所请求的服务在当前灰度发布版本的实例,则执行步骤S709。若判断出未筛选到所请求的服务在当前灰度发布版本的实例,则只能对服务请求进行正常的处理,所以此时执行步骤S710。
S709、针对筛选出的所请求的服务在当前灰度发布版本的实例,转发服务请求。
S710、随机从注册中心的实例列表中挑选出一个实例进行服务请求的转发。
本申请另一实施例提供了一种灰度发布***,如图8所示,包括:
微服务网关801,用于接收用户发起的服务请求,并将服务请求与灰度配置文件中的灰度策略进行匹配,以及用于在服务请求与灰度策略匹配成功,为服务请求打上颜色标记,并下发服务请求。
边车负载均衡组件802,用于拦截下发的服务请求,并判断服务请求是否存在颜色标记,以及用于判断出服务请求存在颜色标记时,筛选出所请求的服务在当前灰度发布版本的实例,进行服务请求的转发。
可选地,本申请另一实施例提供的一种灰度发布***中,灰度策略包括多个灰度子策略,微服务网关执行将服务请求与灰度配置文件中的灰度策略进行匹配时,用于:
将服务请求中的多个信息,分别与灰度配置文件中的对应的灰度子策略进行匹配,得到每个灰度子策略对应的匹配结果,并基于各个灰度子策略间的执行关系,以及每个灰度子策略对应的匹配结果,确定服务请求与灰度策略的最终匹配结果。
其中,执行关系包括或关系、与关系以及非关系。
可选地,本申请另一实施例提供的一种灰度发布***中,微服务网关执行为服务请求打上颜色标记时,用于:
在服务请求的头部中添加与灰度策略对应的颜色标记。
可选地,本申请另一实施例提供的一种灰度发布***中,微服务网关,还用于:
对服务请求进行预处。
其中,预处理至少包括用户认证以及用户鉴权。并且若服务请求通过用户认证以及用户鉴权,则微服务网关针对预处理后的服务请求,执行将服务请求与灰度配置文件中的灰度策略进行匹配。
可选地,本申请另一实施例提供的一种灰度发布***中,边车负载均衡组件,还用于:
在判断出服务请求存在颜色标记,或未筛选到所请求的服务在当前灰度发布的实例版本时,随机从注册中心的实例列表中挑选出一个实例进行服务请求的转发。
需要说明的是,本申请上述实施例提供的微服务网关和边车负载均衡组件实现各个功能时的具体工作过程,可相应地参考上述方法实施例中的相应的步骤,此处不再赘述。
专业人员还可以进一步意识到,结合本文中所公开的实施例描述的各示例的单元及算法步骤,能够以电子硬件、计算机软件或者二者的结合来实现,为了清楚地说明硬件和软件的可互换性,在上述说明中已经按照功能一般性地描述了各示例的组成及步骤。这些功能究竟以硬件还是软件方式来执行,取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能,但是这种实现不应认为超出本申请的范围。
对所公开的实施例的上述说明,使本领域专业技术人员能够实现或使用本申请。对这些实施例的多种修改对本领域的专业技术人员来说将是显 而易见的,本文中所定义的一般原理可以在不脱离本申请的精神或范围的情况下,在其它实施例中实现。因此,本申请将不会被限制于本文所示的这些实施例,而是要符合与本文所公开的原理和新颖特点相一致的最宽的范围。
Claims (10)
- 一种全链路的灰度发布方法,其特征在于,应用于灰度发布***,其中,所述灰度发布***至少包括微服务网关以及边车负载均衡组件,所述全链路的灰度发布方法,包括:所述微服务网关接收用户发起的服务请求;所述微服务网关将所述服务请求与灰度配置文件中的灰度策略进行匹配;若所述服务请求与所述灰度策略匹配成功,则所述微服务网关为所述服务请求打上颜色标记;所述微服务网关下发所述服务请求;所述边车负载均衡组件拦截下发的所述服务请求,并判断所述服务请求是否存在颜色标记;所述边车负载均衡组件若判断出所述服务请求存在颜色标记,则筛选出所请求的服务在当前灰度发布版本的实例,进行所述服务请求的转发。
- 根据权利要求1所述的方法,其特征在于,所述灰度策略包括多个灰度子策略,所述微服务网关将所述服务请求与灰度配置文件中的灰度策略进行匹配,包括:所述微服务网关将所述服务请求中的多个信息,分别与所述灰度配置文件中的对应的灰度子策略进行匹配,得到每个所述灰度子策略对应的匹配结果;基于各个所述灰度子策略间的执行关系,以及每个所述灰度子策略对应的匹配结果,确定所述服务请求与所述灰度策略的最终匹配结果;其中,所述执行关系包括或关系、与关系以及非关系。
- 根据权利要求1所述的方法,其特征在于,所述微服务网关为所述服务请求打上颜色标记,包括:所述微服务网关在所述服务请求的头部中添加与所述灰度策略对应的颜色标记。
- 根据权利要求1所述的方法,其特征在于,所述微服务网关接收用户发起的服务请求之后,还包括:所述微服务网关对所述服务请求进行预处理;其中,所述预处理至少 包括用户认证以及用户鉴权;若所述服务请求通过用户认证以及用户鉴权,则针对预处理后的所述服务请求,执行所述将所述服务请求与灰度配置文件中的灰度策略进行匹配。
- 根据权利要求1所述的方法,其特征在于,还包括:所述边车负载均衡组件若判断出所述服务请求存在颜色标记,或未筛选到所请求的服务在当前灰度发布的实例版本,则随机从注册中心的实例列表中挑选出一个实例进行所述服务请求的转发。
- 一种灰度发布***,其特征在于,包括:微服务网关,用于接收用户发起的服务请求,并将所述服务请求与灰度配置文件中的灰度策略进行匹配,以及用于在所述服务请求与所述灰度策略匹配成功,为所述服务请求打上颜色标记,并下发所述服务请求;边车负载均衡组件,用于拦截下发的所述服务请求,并判断所述服务请求是否存在颜色标记,以及用于判断出所述服务请求存在颜色标记时,筛选出所请求的服务在当前灰度发布版本的实例,进行所述服务请求的转发。
- 根据权利要求6所述的***,其特征在于,所述灰度策略包括多个灰度子策略,所述微服务网关执行所述将所述服务请求与灰度配置文件中的灰度策略进行匹配时,用于:将所述服务请求中的多个信息,分别与所述灰度配置文件中的对应的灰度子策略进行匹配,得到每个所述灰度子策略对应的匹配结果,并基于各个所述灰度子策略间的执行关系,以及每个所述灰度子策略对应的匹配结果,确定所述服务请求与所述灰度策略的最终匹配结果;其中,所述执行关系包括或关系、与关系以及非关系。
- 根据权利要求6所述的***,其特征在于,所述微服务网关执行所述为所述服务请求打上颜色标记时,用于:在所述服务请求的头部中添加与所述灰度策略对应的颜色标记。
- 根据权利要求6所述的***,其特征在于,所述微服务网关,还用于:对所述服务请求进行预处理;其中,所述预处理至少包括用户认证以及用户鉴权;若所述服务请求通过用户认证以及用户鉴权,则所述微服务网关针对预处理后的所述服务请求,执行所述将所述服务请求与灰度配置文件中的灰度策略进行匹配。
- 根据权利要求6所述的***,其特征在于,所述边车负载均衡组件,还用于:在判断出所述服务请求存在颜色标记,或未筛选到所请求的服务在当前灰度发布的实例版本时,随机从注册中心的实例列表中挑选出一个实例进行所述服务请求的转发。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202110610163.1A CN113382051A (zh) | 2021-06-01 | 2021-06-01 | 一种全链路的灰度发布方法及灰度发布*** |
CN202110610163.1 | 2021-06-01 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022252856A1 true WO2022252856A1 (zh) | 2022-12-08 |
Family
ID=77575460
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2022/087858 WO2022252856A1 (zh) | 2021-06-01 | 2022-04-20 | 一种全链路的灰度发布方法及灰度发布*** |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN113382051A (zh) |
WO (1) | WO2022252856A1 (zh) |
Families Citing this family (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN113382051A (zh) * | 2021-06-01 | 2021-09-10 | 中国民航信息网络股份有限公司 | 一种全链路的灰度发布方法及灰度发布*** |
CN113965510B (zh) * | 2021-09-23 | 2023-04-18 | 唯品会(广州)软件有限公司 | 一种流量染色方法和*** |
CN113923081A (zh) * | 2021-10-15 | 2022-01-11 | 北京同城必应科技有限公司 | 分布式环境下灰度发布的业务网关解决方案 |
CN114064062B (zh) * | 2022-01-17 | 2022-05-13 | 北京快成科技有限公司 | 基于Kubernetes平台和负载均衡组件的缺省灰度发布方法和装置 |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109194760A (zh) * | 2018-09-14 | 2019-01-11 | 深圳市佰仟金融服务有限公司 | 业务处理方法、网络***及服务器 |
CN109788029A (zh) * | 2018-12-14 | 2019-05-21 | 平安信托有限责任公司 | 微服务的灰度调用方法、装置、终端及可读存储介质 |
WO2019203909A1 (en) * | 2018-04-16 | 2019-10-24 | Citrix Systems, Inc. | Policy based service routing |
CN111580846A (zh) * | 2020-05-15 | 2020-08-25 | 厦门靠谱云股份有限公司 | 一种基于混合框架的微服务灰度发布方法 |
CN111736872A (zh) * | 2020-06-22 | 2020-10-02 | 平安健康保险股份有限公司 | 灰度发布升级方法、装置、计算机***及可读存储介质 |
CN112181458A (zh) * | 2020-09-25 | 2021-01-05 | 中国建设银行股份有限公司 | 灰度规则的配置、灰度路由方法、装置、设备及存储介质 |
CN113382051A (zh) * | 2021-06-01 | 2021-09-10 | 中国民航信息网络股份有限公司 | 一种全链路的灰度发布方法及灰度发布*** |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104966206A (zh) * | 2015-05-12 | 2015-10-07 | 百度在线网络技术(北京)有限公司 | 对移动应用进行灰度发布的方法、装置和*** |
CN108632374B (zh) * | 2018-05-09 | 2021-06-18 | 恒大智慧科技有限公司 | 软件灰度发布方法及装置 |
CN112579319B (zh) * | 2020-12-07 | 2023-09-08 | 中国民航信息网络股份有限公司 | 一种基于LRU Cache优化的服务调用方法及装置 |
-
2021
- 2021-06-01 CN CN202110610163.1A patent/CN113382051A/zh active Pending
-
2022
- 2022-04-20 WO PCT/CN2022/087858 patent/WO2022252856A1/zh active Application Filing
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2019203909A1 (en) * | 2018-04-16 | 2019-10-24 | Citrix Systems, Inc. | Policy based service routing |
CN109194760A (zh) * | 2018-09-14 | 2019-01-11 | 深圳市佰仟金融服务有限公司 | 业务处理方法、网络***及服务器 |
CN109788029A (zh) * | 2018-12-14 | 2019-05-21 | 平安信托有限责任公司 | 微服务的灰度调用方法、装置、终端及可读存储介质 |
CN111580846A (zh) * | 2020-05-15 | 2020-08-25 | 厦门靠谱云股份有限公司 | 一种基于混合框架的微服务灰度发布方法 |
CN111736872A (zh) * | 2020-06-22 | 2020-10-02 | 平安健康保险股份有限公司 | 灰度发布升级方法、装置、计算机***及可读存储介质 |
CN112181458A (zh) * | 2020-09-25 | 2021-01-05 | 中国建设银行股份有限公司 | 灰度规则的配置、灰度路由方法、装置、设备及存储介质 |
CN113382051A (zh) * | 2021-06-01 | 2021-09-10 | 中国民航信息网络股份有限公司 | 一种全链路的灰度发布方法及灰度发布*** |
Also Published As
Publication number | Publication date |
---|---|
CN113382051A (zh) | 2021-09-10 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2022252856A1 (zh) | 一种全链路的灰度发布方法及灰度发布*** | |
US8656161B2 (en) | Information sharing system, information sharing method, group management program and compartment management program | |
US20040073903A1 (en) | Providing access to software over a network via keys | |
US20080243856A1 (en) | Methods and Apparatus for Scoped Role-Based Access Control | |
US20140324872A1 (en) | Address book maintenance method and group address book management platform | |
CN106775713B (zh) | 文件审核方法、装置及文件提交控制*** | |
US11374970B2 (en) | Phishing attempt categorization/aggregation interface | |
US20110016156A1 (en) | Network management system | |
CN107832613A (zh) | 一种计算机病毒处理方法 | |
US7716678B2 (en) | Processing messages in a message queueing system | |
US20060288401A1 (en) | System and method for generating a Java policy file for Eclipse plug-ins | |
US8738513B2 (en) | Apparatus and method for managing account information | |
US7861242B2 (en) | Mobile application morphing system and method | |
JP7052370B2 (ja) | 評価プログラム、評価方法及び情報処理装置 | |
KR20000054362A (ko) | 인터넷을 이용한 회계 서비스 방법 및 그 시스템 | |
US8977691B2 (en) | Implementation of an extranet server from within an intranet | |
CN108494809A (zh) | 一种基于服务器封包镜像的反爬*** | |
JP2000339156A (ja) | ライセンス管理システム | |
US11983580B2 (en) | Real-time modification of application programming interface behavior | |
WO2023241678A1 (zh) | 一种基于云服务的微服务版本管理方法及云管理平台 | |
JP2002041506A (ja) | 共同編集システム及びサーバ並びに方法 | |
US20240243931A1 (en) | Edge blockchain authentication | |
JP4067784B2 (ja) | ルールベースを配信するためのプログラム | |
JPH0844800A (ja) | 情報処理システム | |
JP2003150355A (ja) | 印刷システム |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 22814903 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 22814903 Country of ref document: EP Kind code of ref document: A1 |