Gray release method, system equipment and storage medium
By configuring grayscale version information and policies, using the registration center and proxy module to realize the routing and processing of grayscale versions, the problem of grayscale release in the existing technology is solved, and the operation and maintenance costs are reduced. And improves system stability and reliability.
Patent Information
- Application Number
- CN202411023425.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-29
- Publication Date
- 2024-12-03
AI Technical Summary
In the prior art, grayscale release is likely to cause system paralysis and high operation and maintenance costs, especially when there are many architecture nodes deployed, and the grayscale release method of the service grid has high cost to transform the existing architecture, and the difficulty of use and the threshold for release operation.
By configuring grayscale version information and policies to each service, subscribing to service instance information using the registration center, and parsing and forwarding client requests through the proxy module, the routing and processing of grayscale versions is realized, reducing the risk of system paralysis and operation and maintenance costs. .
This method reduces the risk of single point failure, reduces operation and maintenance costs, simplifies the grayscale release process, and allows seamless introduction of new versions or features in a private cloud environment to ensure system stability and reliability.
Smart Images

Figure CN119065682A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of computer science and technology, in particular to fields related to distributed systems, cloud computing and software publishing, and more particularly to a grayscale publishing method, system equipment and storage medium. Background Art
[0002] With the continuous development of science and technology, the speed of product updates and iterations in the computer industry has also accelerated. In order to ensure that products can be updated and iterated smoothly and to ensure user experience, grayscale release came into being. Grayscale release is a software release and deployment strategy that aims to reduce the risk of upgrading or introducing new features by gradually introducing new versions or features to a small number of users in the system for testing and verification. This strategy allows new versions to be gradually introduced in a production environment, minimizing the impact of potential problems on the entire user group. However, in the prior art, when there are too many nodes in the deployment architecture, grayscale release is prone to cause node failures and system paralysis, and the existing grayscale release method has complex grayscale release information configuration and high operation and maintenance costs. In addition, for general enterprises, although the existing service grid grayscale release method can realize various types of grayscale release, the cost of modifying the existing architecture is high, the service grid is difficult to use, and the release operation of microservices is difficult and has a high threshold.
[0003] To this end, patent application number CN202111363239 provides an application publishing method and traffic routing method based on container cloud and service grid, which utilizes the advantages of container cloud and combines service grid to realize the automation of resource configuration. The first resource configuration of container cloud and the second resource configuration of service grid are generated by application publishing template and parameters to form virtual machine service and target rules, including traffic routing rules and calling relationships between microservices. This scheme realizes the automatic generation of resource configuration of container cloud and service grid, and lowers the threshold of grayscale release. However, the prior art still has technical problems such as grayscale release easily causing system paralysis and high operation and maintenance costs. Summary of the invention
[0004] To this end, in view of the technical problems that the current existing technologies are prone to cause system paralysis and high operation and maintenance costs, the present invention provides a grayscale release method, system equipment and storage medium to solve at least one of the above technical problems.
[0005] To achieve the above objectives, in a first aspect, the present invention provides a grayscale release method, comprising:
[0006] Configure grayscale version information and grayscale strategy for each service, deploy grayscale version application according to the configured grayscale version information and grayscale strategy, and the grayscale version application initiates registration service to the registration center;
[0007] Subscribing to the registration service through the registration center to obtain service instance information, the service instance information includes: formal services and grayscale services;
[0008] When the service instance is updated, the registration center pushes the registration information to the third party, and the third party pulls the registration information from the registration center by polling;
[0009] Receive a service request initiated by a client, parse the service request, and forward the request to a corresponding service based on the parsing result.
[0010] Furthermore, the grayscale version information customizes a grayscale identifier, and the grayscale identifier is used to distinguish between grayscale services and formal services. The grayscale services and formal services include at least one node, and any node included in the grayscale service and formal service is marked with the grayscale identifier.
[0011] Furthermore, the grayscale strategy includes: configuration by a user, the user is a whitelist user, and when different whitelist users initiate requests, different corresponding services are called according to the initiated requests.
[0012] Furthermore, the grayscale strategy includes: configuring by setting different domain names, matching the domain names with the grayscale identifiers, and routing to different services when users call different domain names.
[0013] Furthermore, registration information of one or more service instances is obtained from the registration center, the registration information including the grayscale identification, IP, port and other related information of the service instance, and the one or more service instances include grayscale instances and non-grayscale instances.
[0014] Furthermore, the parsing result is matched with the grayscale strategy, and the service instances that meet the corresponding business request are screened out from the service instances obtained from the registration center according to the matching result, and then the business request is sent to the service instance that meets the business request for processing.
[0015] In a second aspect, the present invention also provides a grayscale publishing system, including: an agent unit and a registration center unit.
[0016] The proxy unit is used to configure grayscale version information and grayscale strategy for each service, deploy grayscale version application according to the configured grayscale version information and grayscale strategy, and the grayscale version application initiates registration service to the registration center;
[0017] The agent unit subscribes to the registration service through the registration center unit to obtain service instance information, and the service instance information includes: formal service and grayscale service.
[0018] When the service instance is started, registration information is obtained and sent to a third party, and the third party obtains the registration information from the registration center by polling.
[0019] The proxy unit is also used to receive a service request initiated by a client, parse the service request, and forward the request to a corresponding service according to the parsing result.
[0020] Further, the proxy unit includes: a load module, a subscription module, a configuration module and a filter module;
[0021] Load module: used for forwarding the service request. The load module is configured with different routing strategies. The routing strategies include traffic proportion and are used to implement gray version routing.
[0022] Subscription module: used to implement subscription of all service instances;
[0023] Configuration module: used for the grayscale strategy configuration;
[0024] Filter module: used to parse and process the business request.
[0025] In a third aspect, the present invention provides a computing device, comprising:
[0026] A memory for storing program instructions;
[0027] The processor is used to call the program instructions stored in the memory and execute the above-mentioned grayscale publishing method according to the obtained program instructions.
[0028] In a fourth aspect, the present invention provides a computer-readable storage medium, including computer-readable instructions. When a computer reads and executes the computer-readable instructions, the grayscale release method described above is implemented. The readable medium may be multiple, and the multiple readable media can operate independently of each other.
[0029] Compared with the existing technology, the beneficial effect of this solution is that the official and grayscale versions are registered to the registration center through multiple services. The agent, as a consumer, subscribes to the service at the registration center. The agent handles the relevant call requests, forwards different requests to the corresponding version service, and adds a configuration module for the agent to configure grayscale policies for complex requirements. Compared with the grayscale policy issued by the configuration center, the risk of single point failure and the resulting system paralysis is reduced. In addition, this technical solution makes it easier to perform grayscale releases of the system in a private cloud environment, allowing the team to seamlessly introduce new versions or functions, ensuring that the system remains up to date and meets changing needs, and reducing operation and maintenance costs. BRIEF DESCRIPTION OF THE DRAWINGS
[0030] In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.
[0031] Figure 1 A schematic diagram of a flow chart of an embodiment of a grayscale publishing method provided by the present invention;
[0032] Figure 2 An overall architecture diagram of an embodiment of the grayscale publishing method provided by the present invention;
[0033] Figure 3 A structural block diagram of an embodiment of the grayscale publishing method provided by the present invention;
[0034] Figure 4 An agent function module diagram of an embodiment of the grayscale publishing method provided by the present invention;
[0035] Figure 5 A method schematic diagram of an embodiment of the grayscale publishing method provided by the present invention;
[0036] Figure 6 A method schematic diagram of an embodiment of the grayscale publishing method provided by the present invention;
[0037] Figure 7 A method schematic diagram of an embodiment of the grayscale publishing method provided by the present invention;
[0038] Figure 8 A method schematic diagram of an embodiment of the grayscale publishing method provided by the present invention. DETAILED DESCRIPTION
[0039] The embodiments of the present application are described in detail below, and examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present application, and cannot be interpreted as limiting the present application.
[0040] It will be understood by those skilled in the art that, unless otherwise stated, the singular forms "a", "an" and "the" used herein may also include plural forms. It should be further understood that the term "comprising" used in the specification of the present application refers to the presence of features, integers, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or groups thereof. The term "and / or" used herein includes all or any unit and all combinations of one or more associated listed items.
[0041] In order to make the objectives, technical solutions and advantages of the present application more clear, the specific implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.
[0042] For the convenience of description, some nouns or terms involved in the embodiments of the present application are explained below:
[0043] Grayscale release: refers to a release strategy in which the functions of a new version are gradually released to a part of users or user groups for testing and verification during the software development and release process. In grayscale version release, new functions are first exposed to a small number of users in grayscale, and then gradually expanded until all users can use the new functions.
[0044] Proxy: refers to a server or application that acts as an intermediary between a client and a server. It receives requests from clients and forwards them to the target server, and then returns the server's response to the client, playing the role of proxy and forwarding.
[0045] The core of the present invention is to provide a grayscale release method, which can conveniently implement grayscale release by using service discovery technology. This method has great advantages in microservice architecture scenarios, such as Figure 1 The figure is a schematic diagram of the process of the grayscale publishing method provided in this embodiment. In order to better understand the method, Figure 1 The technical solution of this embodiment is described in detail:
[0046] Step S101: Configure a grayscale version information for each service, wherein each service may correspond to a grayscale version information, and the grayscale version information may customize a grayscale identifier, which is used to distinguish between grayscale services and formal services. When there are multiple nodes for grayscale services and formal services respectively, any of the multiple nodes carries the grayscale identifier, and the grayscale identifier is simple to configure and does not depend on the configuration center component.
[0047] Step S102: configure a grayscale strategy for each service.
[0048] In one embodiment, grayscale policies of different dimensions can be configured; for example, by configuring for users, by setting whitelist users, when different users initiate requests, different services are called. Secondly, it can also be configured by setting different domain names, by matching the domain name with the grayscale identifier, when users call different domain names, they are routed to different services.
[0049] Step S103: deploy the grayscale version application and the application automatically initiates service registration to the registration center. In a possible implementation, the service registration module is loaded during the application service startup process, and the registration method obtains the configured grayscale identifier and registers the grayscale identifier as metadata to the registration center.
[0050] Step S104: The agent obtains all service instance information from the registration center subscription service, including formal services and grayscale services; specifically, the agent can obtain the registration information of one or more service instances from the registration center, and the registration information includes the grayscale identification, IP, port and other related information of the service instance, and the one or more service instances include grayscale instances and non-grayscale instances. When each service is started, each instance node will initiate registration. The registration center will record and store the registration information of the service instance, and push the registration information to the agent. At the same time, the agent obtains the registration information from the registration center by polling, and polls by establishing a long connection. This push-pull method ensures that the consumer can perceive the latest instance changes in the first place.
[0051] Step S105: The proxy receives the service request initiated by the client. In a possible implementation, the proxy may receive the user request from the user policy device, and the user request includes one or more of the request version, user identifier, and service domain name. After receiving the service request, the proxy first parses the context of the request, and determines whether the request is a grayscale request based on the version, identifier, domain name, and other information in the request context.
[0052] Step S106: The proxy parses the request and forwards the request to the corresponding service based on the parsing result. Specifically, the proxy parses the request and matches it with the grayscale policy, and filters the service instances obtained from the registration center based on the matching results to select the service instances that meet the business request, and then forwards the business request to the service instance that meets the business request for processing to provide services to the client.
[0053] In one embodiment, a microservice architecture is formed by deploying two microservices, a microservice proxy and a registration center. The overall architecture diagram of the grayscale release system is as follows: Figure 2 To facilitate understanding of the various features and advantages of the technical solution of this embodiment, Figure 2 This embodiment is described in detail:
[0054] In this embodiment, multiple services register official and grayscale versions to a registration center; the agent, as a consumer, subscribes to services at the registration center, processes related call requests, and forwards different requests to corresponding version services.
[0055] For example, service A and service B are divided into service A (official) and service A (grayscale) and service B (official) and service B (grayscale), and registered in the registration center; the agent subscribes to the service in the registration center, and the agent performs corresponding processing based on the call request, and forwards the different requests of service A and service B to the corresponding version service, thereby realizing grayscale release.
[0056] The grayscale publishing method in the above embodiment configures grayscale version information and grayscale strategy for each service, deploys grayscale version application according to the configured grayscale version information and grayscale strategy, initiates registration service to the registration center according to the grayscale version application; obtains service instance information by subscribing to the registration service through the registration center; when the service instance is updated, the registration center pushes the registration information to the third party, and the third party pulls the registration information from the registration center by polling; receives the business request initiated by the client, parses the business request, and forwards the request to the corresponding service according to the parsing result. This solution has the advantages of more convenient and controllable introduction of new functions, bug fixes and performance improvements, while maintaining support for old services, minimizing interference to users, and continuously improving new services through monitoring and user feedback to ensure their stability and performance. It helps in seamless upgrade and maintenance of the system and improves the reliability and stability of the overall system.
[0057] To help better understand the specific application and benefits of the technical solution provided in this embodiment, the following specific embodiment of grayscale release is provided for detailed introduction:
[0058] Case: Grayscale release of web system under private cloud microservice architecture
[0059] Background: The Service Mesh project team runs multiple core microservices in a private cloud environment, including multiple web systems. The front end of a web system has been reconstructed. Due to the high sensitivity to financial data and security, no system interruption or error can be tolerated. Grayscale release is required when releasing the reconstructed service to reduce the risk of going online. Therefore, the grayscale release method provided by the present invention realizes the grayscale release of the reconstructed web system. The implementation case is as follows:
[0060] Step S201: configure grayscale version information for each service: the grayscale version is configured through sensor.service.id;
[0061] For example, for the grayscale release of the service dsrconsole, one is the official version and the other is the grayscale version. The specific configuration is as follows:
[0062] smmp-dsrconsole is the official version, and its sensor.service.id is configured as ms;
[0063] smmp-dsrconsole-peek is the grayscale version, and its sensor.service.id is configured as mstest;
[0064] Step S202: Configure the grayscale policy for each service in the proxy. The grayscale policy can be customized. In this embodiment, the grayscale policy is configured by configuring the domain name. Figure 5 As shown, inte ll iproxy is the proxy in this embodiment.
[0065] Step S203: Deploy the gray version application and the application automatically initiates service registration to the registration center:
[0066] After the official service is started, the service is automatically registered with the registration center. Check the registration log to see pubservice:serviceId:ms;
[0067] After the grayscale service is started, it automatically registers the service with the registration center. Check the registration log to see pubservice:serviceId:mstest.
[0068] Step S204: The agent subscribes to the service from the registration center to obtain all service instance information, including official services and dimmed services: View all service instances subscribed by the agent, see Figure 6 shown.
[0069] It can be found that the agent has subscribed to the official version service instance and the gray version service instance, where ms corresponds to the official version instance, and the instance data is:
[0070]
[0071] mstest corresponds to the gray version instance, the instance data is:
[0072]
[0073] It can be seen that in addition to subscribing to the grayscale released service, the agent also subscribes to other service instances, indicating that this grayscale release method supports multi-microservice grayscale release scenarios. When one or more services are added, the current grayscale method can be reused, which has good scalability.
[0074] Step S205: The proxy receives the service request sent by the client user:
[0075] After the user initiates a service request, the proxy receives the service request. From the log, it can be found that the user request is a grayscale request, including mstest.
[0076] After the user initiates a service request, the proxy receives the service request and finds through the log that the user request is a formal request, including ms.
[0077] Step S206: The proxy parses the request and forwards the request to the corresponding service according to the parsing result.
[0078] The user initiates a request, and the proxy parses the request to obtain sensor.service.id. When sensor.service.id is mstest, the request is forwarded to the grayscale service. For details, see Figure 7 shown.
[0079] The user initiates a request, and the proxy parses the request to obtain sensor.service.id. If sensor.service.id is ms, the request is forwarded to the official service. For details, see Figure 8 shown.
[0080] Through the grayscale release method provided in this embodiment, grayscale release of services is achieved without causing interruption or failure to the entire system. The official service and the grayscale service coexist and run in parallel. After verification, the grayscale service can be switched to the official service while maintaining support for the old service. Through monitoring and user feedback, the new service is continuously improved to ensure its stability and performance. This embodiment shows how to effectively use service registration and discovery technology to safely introduce new features and reduce risks, especially in the financial field where sensitive data is processed.
[0081] In one embodiment, the present disclosure provides a grayscale publishing system, see Figure 3 The figure shows a structure block diagram of a grayscale publishing system provided by this embodiment, including: an agent unit and a registration center unit;
[0082] The proxy unit is used to configure grayscale version information and grayscale strategy for each service, deploy grayscale version application according to the configured grayscale version information and grayscale strategy, and the grayscale version application initiates registration service to the registration center;
[0083] The agent unit subscribes to the registration service through the registration center unit to obtain service instance information, and the service instance information includes: formal services and gray services;
[0084] When the service instance is updated, the registration center pushes the registration information to the third party, and the third party pulls the registration information from the registration center by polling; the proxy unit is also used to receive the business request initiated by the client, parse the business request, and forward the request to the corresponding service according to the parsing result.
[0085] In one embodiment, the entire grayscale release architecture, the distribution of requests is mainly completed by the agent. For details of the agent function module diagram, see Figure 4 As shown, the proxy unit includes: a load module 301 , a subscription module 302 , a configuration module 303 and a filter module 304 .
[0086] The basic function of the proxy is to forward requests, among which the load module 301 is responsible for request forwarding. Different routing strategies can be configured in the load module 301. The routing strategies include traffic proportions and can be used to implement gray version routing. Secondly, the proxy is responsible for subscribing to services as a consumer, so the subscription module 302 can be used to implement subscriptions to all service instances. When new services appear, they can be subscribed by the same proxy, thus achieving good scalability. In addition, for complex grayscale requirements, a configuration module 303 is added to the proxy for grayscale strategy configuration for complex requirements. Compared with the grayscale strategy issued by the configuration center, the risk of single point failure is reduced, especially in financial-related fields, where stability and security are the most important. Finally, after the request is received, a filter module 304 needs to be added to parse and process the request. This logic is combined with grayscale and routing strategies to achieve accurate forwarding of requests.
[0087] Compared with the grayscale policy issued by the configuration center, the configuration module added by the proxy service in this embodiment reduces the risk of system paralysis caused by single point failure; and this technical solution makes it easier to perform grayscale releases of the system in a private cloud environment, allowing the team to seamlessly introduce new versions or functions, ensuring that the system remains up-to-date and meets changing needs, reducing operation and maintenance costs.
[0088] The grayscale publishing system of this embodiment is used to implement the grayscale publishing method described above, so the specific implementation of the grayscale publishing system can be seen in the specific implementation of the grayscale publishing method described above. The specific implementation can refer to the description of the corresponding embodiments, which will not be repeated here.
[0089] In one embodiment, a computing device is provided, comprising:
[0090] A memory for storing program instructions;
[0091] A processor is used to implement the steps of the grayscale publishing method described in any of the above when executing the computer program. A grayscale publishing method of the present invention has obvious advantages and beneficial effects compared with the prior art. By configuring grayscale version information and grayscale strategy for each service, grayscale version applications are deployed according to the configured grayscale version information and grayscale strategy, and registration services are initiated to the registration center according to the grayscale version application; the registration service is subscribed to by the registration center to obtain service instance information; when the service instance is updated, the registration center pushes the registration information to a third party, and the third party pulls the registration information from the registration center by polling; receives the service request initiated by the client, parses the service request, and forwards the request to the corresponding service according to the parsing result. This solution has the advantages of more convenient and controllable introduction of new functions, bug fixes and performance improvements, while maintaining support for old services, minimizing interference to users, and continuously improving new services through monitoring and user feedback to ensure their stability and performance. It is helpful for seamless upgrade and maintenance of the system and improves the reliability and stability of the overall system.
[0092] In one embodiment, a computer-readable storage medium is provided, including computer-readable instructions. When a computer reads and executes the computer-readable instructions, the steps of the grayscale publishing method described above are implemented. Compared with the prior art, the grayscale publishing method of the present invention has obvious advantages and beneficial effects. By configuring grayscale version information and grayscale strategy for each service, the grayscale version application is deployed according to the configured grayscale version information and grayscale strategy, and a registration service is initiated to the registration center according to the grayscale version application; the registration service is subscribed to by the registration center to obtain service instance information; when the service instance is updated, the registration center pushes the registration information to a third party, and the third party pulls the registration information from the registration center by polling; receives a business request initiated by a client, parses the business request, and forwards the request to the corresponding service according to the parsing result. This solution has the advantages of more convenient and controllable introduction of new functions, bug fixes and performance improvements, while maintaining support for old services, minimizing interference to users, and continuously improving new services through monitoring and user feedback to ensure their stability and performance. It is helpful for seamless upgrade and maintenance of the system and improves the reliability and stability of the overall system.
[0093] So far, the technical solutions of the present invention have been described in conjunction with the preferred embodiments shown in the accompanying drawings. However, it is easy for those skilled in the art to understand that the protection scope of the present invention is obviously not limited to these specific embodiments. Without departing from the principle of the present invention, those skilled in the art can make equivalent changes or substitutions to the relevant technical features, and the technical solutions after these changes or substitutions will fall within the protection scope of the present invention.
[0094] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.
Claims
1. A grayscale release method, characterized in that: include: Configure grayscale version information and grayscale strategy for each service, deploy grayscale version application according to the configured grayscale version information and grayscale strategy, and the grayscale version application initiates service registration to the registration center; Subscribing to the registration service through the registration center to obtain service instance information, the service instance information includes: formal services and grayscale services; When the service instance is updated, the registration center pushes the registration information to the third party, and the third party pulls the registration information from the registration center by polling; When the service instance is updated, the registration center pushes the registration information to the third party, and the third party pulls the registration information from the registration center by polling; receives the business request initiated by the client, parses the business request, and forwards the request to the corresponding service according to the parsing result.
2. The grayscale release method according to claim 1, characterized in that: The grayscale version information customizes a grayscale identifier, and the grayscale identifier is used to distinguish between grayscale services and formal services. The grayscale services and formal services include at least one node, and any node included in the grayscale service and the formal service is marked with the grayscale identifier.
3. The grayscale release method according to claim 1, characterized in that: The grayscale strategy includes: configuration through users, the users are whitelist users, when different whitelist users initiate requests, different corresponding services are called according to the initiated requests.
4. The grayscale release method according to claim 1, characterized in that: The grayscale strategy includes: configuring by setting different domain names, matching the domain names with the grayscale identifiers, and routing to different services when users call different domain names.
5. The grayscale release method according to claim 1, characterized in that: The registration information of one or more service instances is obtained from the registration center, where the registration information includes the grayscale identifier, IP address, port number and other related information of the service instance, and the one or more service instances include grayscale instances and non-grayscale instances.
6. The grayscale release method according to claim 1, characterized in that: The parsing result is matched with the grayscale strategy, and the service instances that meet the business request are screened out from the service instances obtained from the registration center according to the matching result, and then the business request is sent to the service instance that meets the business request for processing.
7. A grayscale release system, characterized in that: Including, agent unit, registration center unit; The proxy unit is used to configure grayscale version information and grayscale strategy for each service, deploy grayscale version application according to the configured grayscale version information and grayscale strategy, and the grayscale version application initiates registration service to the registration center; The agent unit subscribes to the registration service through the registration center unit to obtain service instance information, and the service instance information includes: formal services and gray services; When the service instance is updated, the registration center pushes the registration information to the third party, and the third party pulls the registration information from the registration center by polling; The proxy unit is also used to receive a service request initiated by a client, parse the service request, and forward the request to a corresponding service according to the parsing result.
8. The grayscale release system according to claim 7, characterized in that: The proxy unit includes: a load module, a subscription module, a configuration module and a filter module; Load module: used for forwarding the service request. The load module is configured with different routing strategies. The routing strategies include traffic proportion and are used to implement gray version routing. Subscription module: used to implement subscription of all service instances; Configuration module: used for the grayscale strategy configuration; Filter module: used to parse and process the business request.
9. A computing device, characterized in that include: A memory for storing program instructions; A processor is used to call the program instructions stored in the memory, and execute the method according to any one of claims 1 to 6 according to the obtained program instructions.
10. A computer-readable storage medium, characterized in that: It includes computer-readable instructions. When a computer reads and executes the computer-readable instructions, it implements the method according to any one of claims 1 to 6. There may be multiple readable media, and the multiple readable media can operate independently of each other.
Citation Information
Cited By
Message queue flow grayscale release method and system based on proxy mode
CN121750726A
Message queue traffic gray release method and system based on proxy mode
CN121750726B
