CN109787830B - Gray scale distribution control method, device, system, electronic device and storage medium - Google Patents
Gray scale distribution control method, device, system, electronic device and storage medium Download PDFInfo
- Publication number
- CN109787830B CN109787830B CN201910055325.2A CN201910055325A CN109787830B CN 109787830 B CN109787830 B CN 109787830B CN 201910055325 A CN201910055325 A CN 201910055325A CN 109787830 B CN109787830 B CN 109787830B
- Authority
- CN
- China
- Prior art keywords
- version
- gray
- access request
- alternative version
- web service
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Landscapes
- Information Transfer Between Computers (AREA)
Abstract
The invention discloses a gray scale release control method, device and system, electronic equipment and a storage medium. The Web service has an original version and at least one alternative version, and the gray release control method comprises the following steps: receiving an access request of a client, wherein the access request is used for requesting to access the Web service; acquiring a gray level strategy matched with the Web service, wherein the gray level strategy comprises a gray level control logic, and the gray level control logic is used for configuring at least one alternative version of specified access distinguished by the Web service according to preset information; judging whether an alternative version corresponding to the value of the client on the preset information exists or not according to the gray control logic; if so, forwarding the access request to the corresponding alternative version; and if not, forwarding the access request to the original version. The invention supports gray release of various information and multiple alternative versions and supports complex gray logic.
Description
Technical Field
The present invention relates to the field of internet, and in particular, to a method, an apparatus, a system, an electronic device, and a storage medium for controlling gray release.
Background
For website applications, it is usually required to provide 7 × 24 hours of uninterrupted service, and even if the service is upgraded, the normal access of the website by the user is not affected. Generally, the server is released through gray scale, namely, a new version is released to one of the servers first, whether the server reports the abnormal information or not is checked, a website is accessed to check whether the service is normal or not, after no problem is confirmed, half of the servers are released again, and finally, the server is released in full quantity after no problem is confirmed.
The existing gray release is generally finished by an automatic deployment system, the gray release can only be supported to carry out gray according to a small amount of information, the support of more complex gray logic is not good, and the flexible application of the gray release is influenced.
Disclosure of Invention
The technical problem to be solved by the embodiments of the present invention is to provide a method, an apparatus, a system, an electronic device, and a storage medium for controlling gray scale publishing, so as to overcome the defects that gray scale publishing can only support gray scale according to a small amount of information, and the flexible application of gray scale publishing is affected due to the poor support of more complicated gray scale logic.
The embodiment of the invention solves the technical problems through the following technical scheme:
the embodiment of the invention provides a Web (global wide area network) service gray release control method, wherein a Web service has an original version and at least one alternative version, and the method comprises the following steps:
receiving an access request of a client, wherein the access request is used for requesting to access the Web service;
acquiring a gray level strategy matched with the Web service, wherein the gray level strategy comprises a gray level control logic, and the gray level control logic is used for configuring at least one alternative version of specified access distinguished by the Web service according to preset information;
judging whether an alternative version corresponding to the value of the client on the preset information exists or not according to the gray control logic;
if yes, forwarding the access request to the corresponding alternative version;
and if not, forwarding the access request to the original version.
Preferably, the access request includes a request URL (uniform resource locator), and the grayscale control logic is configured with an alternate version of the URL and the original version of the URL that the Web service specifies to access;
forwarding the access request to the corresponding alternate version comprises: forwarding the access request to the URL of the corresponding alternative version;
the step of forwarding the access request to the original version comprises: forwarding the access request to the original version of the URL.
Preferably, the preset information includes at least one of an IP (internet protocol address), a uid (User identification), a User-Agent (User Agent), and a third party service caller.
Preferably, the gray control logic is configured with at least one alternative version appointed to be accessed by the Web service and control logic of each alternative version;
according to the gray control logic, the step of judging whether the alternative version corresponding to the value of the client on the preset information exists or not comprises the following steps:
judging whether the alternative version of the gray control logic configuration is empty or not;
if the version is empty, forwarding the access request to the original version;
if not, then:
executing the control logic of the alternative versions one by one until finding out the alternative version hit by the value of the client on the preset information, taking the hit alternative version as the corresponding alternative version, and forwarding the access request to the corresponding alternative version;
if the value of the client on the preset information does not hit any alternative version, forwarding the access request to the original version;
and/or the gray control logic is also configured with a request distribution strategy of each alternative version;
when the access request is forwarded to the corresponding alternative version, the method distributes the request according to the request distribution strategy;
and/or the gray control logic is also configured with whether each alternative version is executed in the background;
when the access request is forwarded to the corresponding alternative version, if the corresponding alternative version is configured to be executed in the background, the access request is forwarded to the corresponding alternative version in the background.
Preferably, the gray control logic is further configured with an exception handling rule of each alternative version, and the exception handling rule is used for configuring at least one exception logic and a corresponding solution when the exception logic occurs;
the method also comprises the steps of judging whether any abnormal logic appears after the access request is forwarded to the corresponding alternative version, and if so, executing a corresponding solution;
wherein the exception logic preferably includes at least one of the following conditions:
generating an error response status code;
an access timeout;
accessing a current limit;
the solution preferably comprises: forwarding the access request to the original version.
Preferably, the grayscale policy further includes a verification logic, and the verification logic is configured to verify whether the contents of the alternative version are correct;
the method further comprises the following steps: after the access request is forwarded to the corresponding alternative version, verifying whether the response result of the alternative version is correct or not according to the verification logic;
and if the access request is wrong, forwarding the access request to the original version.
The embodiment of the invention provides a gray control method, which comprises the following steps:
and configuring a gray level strategy, wherein the gray level strategy comprises gray level control logic, and the gray level control logic is used for configuring at least one alternative version of specified access distinguished by the Web service according to preset information.
Preferably, the preset information includes at least one of IP, uid, user-Agent, and third party service caller.
Preferably, the gray scale control logic is configured with at least one alternate version of the specified access by the Web service, and at least one of:
a URL of an original version of the Web service;
the URL of each alternative version;
control logic for each alternate version;
a request distribution strategy of each alternative version;
whether each alternative version is executed in the background;
exception handling rules for each alternate version, the exception handling rules being used to configure at least one exception logic and a corresponding solution when the exception logic occurs, wherein the exception logic preferably includes at least one of the following conditions:
generating an error response status code;
an access timeout;
accessing a current limit;
the solution preferably comprises: forwarding the access request to the original version.
Preferably, the grayscale strategy further includes a verification logic for verifying whether the contents of the alternative version are correct.
The embodiment of the invention provides a Web service gray release control device, wherein the Web service has an original version and at least one alternative version, and the device comprises: the device comprises a receiving module, an obtaining module, a judging module and a forwarding module;
the receiving module is used for receiving an access request of a client, and the access request is used for requesting to access the Web service;
the acquisition module is used for acquiring a gray strategy matched with the Web service, the gray strategy comprises a gray control logic, and the gray control logic is used for configuring at least one alternative version of specified access distinguished by the Web service according to preset information;
the judging module is used for judging whether an alternative version corresponding to the value of the client on the preset information exists according to the gray control logic, if so, the forwarding module is called to forward the access request to the corresponding alternative version, and if not, the forwarding module is called to forward the access request to the original version.
Preferably, the access request includes a request URL, and the grayscale control logic is configured with a URL of an alternative version and a URL of the original version that the Web service specifies to access;
forwarding the access request to the corresponding alternate version comprises: forwarding the access request to the URL of the corresponding alternative version;
forwarding the access request to the original version comprises: forwarding the access request to the original version of the URL.
Preferably, the preset information includes at least one of IP, uid, user-Agent, and third party service caller.
Preferably, the gray control logic is configured with at least one alternative version that the Web service is appointed to access and control logic of each alternative version;
the judging module is used for judging whether the alternative versions configured by the gray control logic are empty or not, if so, the forwarding module is called to forward the access request to the original version, if not, the control logic of each alternative version is executed one by one until the alternative version hit by the value of the client on the preset information is found, then the hit alternative version is used as the corresponding alternative version, the forwarding module is called to forward the access request to the corresponding alternative version, and if the value of the client on the preset information does not hit any alternative version, the forwarding module is called to forward the access request to the original version;
and/or the gray control logic is also configured with a request distribution strategy of each alternative version;
when the forwarding module forwards the access request to the corresponding alternative version, request distribution is carried out according to the request distribution strategy;
and/or the gray control logic is also configured with whether each alternative version is executed in the background;
when the forwarding module forwards the access request to the corresponding alternative version, if the corresponding alternative version is configured to be executed in a background, the forwarding module forwards the access request to the corresponding alternative version in the background.
Preferably, the gray control logic is further configured with an exception handling rule of each alternative version, and the exception handling rule is used for configuring at least one exception logic and a corresponding solution when the exception logic occurs;
the device further comprises:
an exception handling module, configured to determine whether any one of the exception logics occurs after the access request is forwarded to the corresponding alternative version, and if so, execute a corresponding solution;
wherein the exception logic preferably includes at least one of the following conditions:
generating an erroneous response status code;
an access timeout;
accessing a current limit;
the solution preferably comprises: and calling the forwarding module to forward the access request to the original version.
Preferably, the grayscale policy further includes a verification logic, and the verification logic is configured to verify whether the contents of the alternative version are correct;
the device further comprises:
and the verification module is used for verifying whether the response result of the alternative version is correct or not according to the verification logic after the access request is forwarded to the corresponding alternative version, and calling the forwarding module to forward the access request to the original version if the response result of the alternative version is wrong.
An embodiment of the present invention provides a gray scale control system, including:
the system comprises a configuration module and a management module, wherein the configuration module is used for configuring a gray strategy, the gray strategy comprises gray control logic, and the gray control logic is used for configuring at least one alternative version of specified access which is distinguished by Web services according to preset information.
Preferably, the preset information includes at least one of IP, uid, user-Agent, and third party service caller.
Preferably, the grayscale control logic is configured with at least one alternate version of the specified access of the Web service, and at least one of:
a URL of an original version of the Web service;
the URL of each alternative version;
control logic for each alternate version;
request distribution strategy of each alternative version;
whether each alternative version is executed in the background;
exception handling rules for each alternate version for configuring at least one exception logic and corresponding solutions in the presence of the exception logic, wherein the exception logic preferably includes at least one of the following conditions:
generating an erroneous response status code;
an access timeout;
accessing a current limit;
the solution preferably comprises: forwarding the access request to the original version.
Preferably, the grayscale strategy further includes a verification logic for verifying whether the contents of the alternative version are correct.
The embodiment of the invention provides a Web service system, which comprises the Web service gray level release control device and the gray level control system;
and the Web service gray level release control device calls the gray level control system after receiving the access request of the client, and the gray level control system returns the gray level strategy matched with the Web service to the Web service gray level release control device.
The embodiment of the invention provides electronic equipment, which comprises a memory, a processor and a computer program which is stored on the memory and can run on the processor, wherein when the processor executes the program, the Web service gray scale release control method is realized.
An embodiment of the present invention provides a computer-readable storage medium, on which a computer program is stored, where the computer program is executed by a processor to implement the steps of the Web service gray scale distribution control method as described above.
An embodiment of the present invention provides an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the gray scale control method as described above when executing the program.
An embodiment of the present invention provides a computer-readable storage medium, on which a computer program is stored, where the computer program is executed by a processor to implement the steps of the gray scale control method as described above.
On the basis of the common general knowledge in the field, the above preferred conditions can be combined randomly to obtain the preferred embodiments of the invention.
The embodiment of the invention has the positive improvement effects that: the method realizes the gray release supporting various information and multiple alternative versions by distinguishing the alternative versions appointed to be accessed by the Web service according to the preset information; through the configuration of a gray strategy, particularly a gray control logic and a verification logic, the complex gray logic is supported, and the gray release can be carried out more flexibly; through the adaptive processing under the abnormal condition, the normal availability and good user experience of the service are ensured.
Drawings
Fig. 1 is a flowchart of a Web service gray scale publishing control method according to embodiment 1 of the present invention.
Fig. 2 is a flowchart of a Web service gray scale publishing control method according to embodiment 2 of the present invention.
Fig. 3 is a flowchart of a gray scale control method according to embodiment 3 of the present invention.
Fig. 4 is a schematic block diagram of a Web service grayscale distribution control apparatus according to embodiment 4 of the present invention.
Fig. 5 is a schematic block diagram of a Web service grayscale distribution control apparatus according to embodiment 5 of the present invention.
Fig. 6 is a schematic block diagram of a gray scale control system according to embodiment 6 of the present invention.
Fig. 7 is a schematic block diagram of a Web service system according to embodiment 6 of the present invention.
Fig. 8 is a schematic structural diagram of an electronic device in embodiment 7 of the present invention.
Detailed Description
The invention is further illustrated by the following examples, which are not intended to limit the scope of the invention.
Example 1
Fig. 1 shows a Web service gradation issuance control method of the present embodiment. The Web service has an original version and at least one alternate version. The Web service gray release control method comprises the following steps:
step 11: and receiving an access request of a client. The access request is used for requesting to access the Web service.
Step 12: and acquiring the gray strategy matched with the Web service. The grayscale strategy includes grayscale control logic. The gray control logic is used for configuring at least one alternative version of the designated access distinguished by the Web service according to the preset information.
Step 13: and judging whether an alternative version corresponding to the value of the client on the preset information exists or not according to the gray control logic, if so, executing the step 14, and if not, executing the step 15.
Step 14: forwarding the access request to the corresponding alternate version.
Step 15: forwarding the access request to the original version.
The Web service gray scale release control method of the embodiment can be applied to, but not limited to, scenes such as updating of Web service versions and testing of different versions. The original version may be an old version of the Web service with stable functions, and the alternative version may be a new version of the Web service newly developed with functions requiring further tests or without determining whether the functions are stable. The number of the alternative versions that a Web service can have may be determined according to various factors such as actual development conditions and release conditions, and the embodiment is not particularly limited.
The gray control logic of this embodiment indicates that the client has different values in the preset information, and the alternative versions of the Web service designated for access may be different. In this embodiment, the preset information may include at least one of an IP, a uid, a User-Agent, and a third-party service caller, and is more than information that can support gray scale in the conventional gray scale distribution, so that the entire gray scale distribution is more flexible. Through the configuration of the gray control logic, the method of the embodiment can realize that the used versions are different when different users access the same Web service, and supports multi-version gray release.
Example 2
The Web service gray scale release control method provided by this embodiment is further refined on the basis of embodiment 1, and is mainly embodied in that:
the grayscale strategy of the present embodiment includes grayscale control logic and verification logic. The gray scale strategy can be specifically configured with a plurality of configuration items, and is favorable for realizing more complex gray scale control and version verification. The configuration items for implementing the gray scale control logic may include, but are not limited to, configurations:
KEY (KEY, e.g., KEY = request URL) for matching of the grayscale policy;
URL (old _ version _ URL) of the original version;
the Web service specifies at least one alternate version of access (version, such as version = version N, N being a positive integer);
URL of each alternative version (version N _ URL, which may be a relative path such as/tem/v 1, or an absolute path such as server internal forwarding address http:// a.local/item/v1, redirection address http:// a.com/item/v 1);
control logic for each alternate version (version _ control _ logic, e.g., version _ control _ logic = lua code);
a request distribution policy (version n _ dispatch, e.g., version n _ dispatch = redirect/forward) for each alternate version, the request distribution policy being used to indicate whether a server internally forwards to the url of the version n or redirects to the url of the version n when distributing a request;
whether each alternative version is executed in the background (such as version n _ background = 0/1), if so, it means that the traffic is copied to version n without executing the gray logic;
exception handling rules for each alternate version, the exception handling rules for configuring at least one exception logic and corresponding solutions when the exception logic occurs, wherein the exception logic preferably includes, but is not limited to, at least one of the following conditions:
generating an erroneous response status code (versionjerror _ status, such as versionjerror _ status =404,500,502, 503);
an access timeout (version n _ timeout, e.g., version n _ timeout =5 s);
access limit (version _ limit, e.g., version _ limit = 100/s);
the solutions corresponding to the above conditions may be the same or different, and the solutions of the present embodiment preferably include but are not limited to: forwarding the access request to the original version.
The verification logic is configured to verify whether the contents of the alternate version are correct. Configuration items for implementing the verification logic may include, but are not limited to, configuration:
a verification rule (version n _ validity _ rule, for example, version n _ validity _ rule = lua code) is used to verify whether the content of version n is correct, and if 0 is returned, it indicates that the verification fails.
The configuration items of each alternative version may be the same or different according to actual needs. The specific configuration of each configuration item can be the same or different according to actual needs.
Fig. 2 shows a Web service gradation issuance control method of the present embodiment. For the gray scale control logic of the present embodiment, the method for controlling Web service gray scale issuance includes the following steps:
step 21: receiving an access request of a client, wherein the access request comprises a request URL, a source IP, a request parameter and a request header, and the request URL is used for representing a Web service which is requested to be accessed.
Step 22: and using the request URL to acquire a KEY as a gray level strategy of the request URL.
Step 23: and judging whether the alternative version of the gray scale control logic configuration of the gray scale strategy is empty, if so, executing the step 24, and if not, executing the step 25.
Step 24: forwarding the access request to the original version of the URL.
Step 25: executing the control logic of the alternative versions one by one until finding the alternative version hit by the value of the client on the preset information, taking the hit alternative version as the corresponding alternative version, and then executing step 27. For example, assuming that the candidate versions of the Web service designated access are version1 and version2, the control logic of version1 is executed first, where dynamic configuration can be realized by loadstring (one function type) dynamic parsing script using lua (one scripting language) scripting language, the request URL, the source IP, the request parameter and the request header are transmitted to the lua function and executed, assuming that the access request is forwarded to version1 with the preset information uid and the preset uid mantissas 1, 3 and 5, if the executed return value is 1, it indicates that version1 is hit, otherwise it indicates that version1 is not hit, then the control logic of version2 is executed, and it is also determined whether the return value is 1, if return 1, it indicates that version2 is hit, otherwise, it indicates that version2 is not hit.
Step 26: if the value of the client on the preset information does not hit any alternative version, step 24 is executed.
Step 27: forwarding the access request to the corresponding alternate version of the URL. When the access request is forwarded to the corresponding alternative version, request distribution is required to be carried out according to the request distribution strategy, if the access request is forwarded, the request distribution strategy indicates that the access request is internally forwarded to the URL of the corresponding alternative version, and if the access request is redirected, the request distribution strategy indicates that the access request is redirected to the URL of the corresponding alternative version; and if the corresponding alternative version is configured to be executed in the background, the background forwards the access request to the corresponding alternative version, and judges whether the corresponding alternative version is correct or not by observing a log under the condition of not being online.
Step 28: and judging whether any abnormal logic appears or not, wherein the judgment includes whether a response state code is correct after a response is forwarded and returned, whether the response state code is overtime or not and whether the current is limited or not, if any abnormal logic appears, executing the step 24, and if any abnormal logic does not appear, executing the step 29.
Step 29: and verifying whether the response result of the alternative version is correct according to the verification logic, and if the response result of the alternative version is incorrect, executing the step 24.
In this embodiment, the control of the gray release is very flexible, can support multi-version gray, can support the configuration of gray, can support complex gray control and verification logic, can copy the flow to come the gray verification function, can flexibly and adaptively handle abnormal logic, and can be quickly and automatically degraded to the original version for processing when encountering problems without worrying about influencing user experience, thereby realizing flexible multi-version gray.
The Web-gray-scale service publishing control method in embodiment 1 and embodiment 2 can be implemented by using a Nginx (a high-performance HTTP and reverse proxy service, and also an IMAP/POP3/SMTP service) access layer (or by using other technologies similar to the Nginx, such as writing an access layer in go language) + lua.
Example 3
Fig. 3 shows a gradation control method of the present embodiment. The gray control method comprises the following steps:
step 31: and configuring a gray strategy.
In this embodiment, the grayscale strategy includes grayscale control logic. The gray control logic is used for configuring at least one alternative version which is distinguished by the Web service according to the preset information and is appointed to access. The gray control logic of this embodiment indicates that the client has different values in the preset information, and the alternative versions of the Web service designated for access are different.
In this embodiment, the preset information includes at least one of an IP, a uid, a User-Agent, and a third-party service caller, and compared with the conventional gray-scale distribution, the preset information is more information capable of supporting gray-scale, so that the entire gray-scale distribution is more flexible.
The gray scale strategy can be specifically configured with a plurality of configuration items, which is beneficial to realizing more complex gray scale control. The configuration items for implementing the gray scale control logic may include, but are not limited to, configuration items:
KEY (KEY, e.g., KEY = request URL) for matching of the grayscale policy;
URL (old _ version _ URL) of the original version;
the Web service specifies at least one alternative version of access (version, such as version = version N, N is a positive integer);
URL of each alternative version (version N _ URL, which may be a relative path such as/tem/v 1, or an absolute path such as server internal forwarding address http:// a. Local/item/v1, redirection address http:// a. Com/item/v 1);
control logic for each alternate version (version n _ control _ logic, e.g., version n _ control _ logic = lua code);
a request distribution policy (versionjdispatch, such as versionjdispatch = redirect/forward) for each alternate version, the request distribution policy being used to indicate whether a server internally forwards to the url of versionN or redirects to the url of versionN when distributing a request;
whether each alternate version is executed in background (such as version n _ background = 0/1), if so, it means that the traffic is copied to version n without performing gray-scale logic;
exception handling rules for each alternate version, the exception handling rules for configuring at least one exception logic and corresponding solutions when the exception logic occurs, wherein the exception logic preferably includes, but is not limited to, at least one of the following conditions:
generating an error response status code (version n _ error _ status, e.g., version n _ error _ status =404,500,502, 503);
an access timeout (version n _ timeout, e.g., version n _ timeout =5 s);
access limit (version _ limit, e.g., version _ limit = 100/s);
the solutions corresponding to the above conditions may be the same or different, and the solutions of the present embodiment preferably include but are not limited to: forwarding the access request to the original version.
In this embodiment, the grayscale strategy may further include a verification logic. The verification logic is configured to verify whether the contents of the alternate version are correct. Configuration items for implementing the verification logic may include, but are not limited to, configuration:
a verification rule (version n _ validity _ rule, for example, version n _ validity _ rule = lua code) is used to verify whether the content of version n is correct, and if 0 is returned, it indicates that the verification fails.
The configuration items of each alternative version may be the same or different according to actual needs. The specific configuration of each configuration item can also be the same or different according to actual needs.
The gray scale control method of this embodiment may be used alone to implement the configuration of the complex gray scale strategy, or may be used in combination with the Web service gray scale distribution control method in embodiment 1 or embodiment 2, for example, to provide the configured gray scale strategy for the Web service gray scale distribution control method to ensure the gray scale control.
Example 4
Fig. 4 shows a Web service gradation issuance control apparatus of the present embodiment. The Web service has an original version and at least one alternate version. The Web service gradation issuance control apparatus 40 includes: a receiving module 41, an obtaining module 42, a judging module 43 and a forwarding module 44.
The receiving module 41 is configured to receive an access request of a client. The access request is used for requesting to access the Web service.
The obtaining module 42 is configured to obtain the grayscale policy matched with the Web service. The grayscale strategy includes grayscale control logic. The gray control logic is used for configuring at least one alternative version which is distinguished by the Web service according to preset information and is appointed to access.
The determining module 43 is configured to determine, according to the gray-scale control logic, whether an alternative version corresponding to the value of the client on the preset information exists, if so, invoke the forwarding module 44 to forward the access request to the corresponding alternative version, and if not, invoke the forwarding module 44 to forward the access request to the original version.
The Web service grayscale release control apparatus 40 of the present embodiment can be applied to, but is not limited to, scenarios such as updating Web service versions, testing different versions, and the like. The original version may be an old version of the Web service with stable functions, and the alternative version may be a new version of the Web service newly developed with functions requiring further tests or without determining whether the functions are stable. The number of the alternative versions that a Web service can have may be determined according to various factors such as actual development conditions and release conditions, and the embodiment is not particularly limited.
The gray control logic of this embodiment indicates that the client has different values in the preset information, and the alternative versions of the Web service designated for access may be different. In this embodiment, the preset information may include at least one of an IP, a uid, a User-Agent, and a third-party service caller, and is more than information that can support gray scale in the conventional gray scale distribution, so that the entire gray scale distribution is more flexible. Through the configuration of the gray scale control logic, the device of the embodiment can realize that different versions are different when different users access the same Web service, and supports multi-version gray scale distribution.
Example 5
The Web service gray scale distribution control device provided in this embodiment is further refined on the basis of embodiment 4, and is mainly embodied in that:
the grayscale strategy of the present embodiment includes grayscale control logic and verification logic. The gray scale strategy can be specifically configured with a plurality of configuration items, and is favorable for realizing more complex gray scale control and version verification. The configuration items for implementing the gray scale control logic may include, but are not limited to, configuration items:
KEY (KEY, e.g., KEY = request URL) for matching of the grayscale policy;
URL (old _ version _ URL) of the original version;
the Web service specifies at least one alternative version of access (version, such as version = version N, N is a positive integer);
URL of each alternative version (version N _ URL, which may be a relative path such as/tem/v 1, or an absolute path such as server internal forwarding address http:// a.local/item/v1, redirection address http:// a.com/item/v 1);
control logic for each alternate version (version n _ control _ logic, e.g., version n _ control _ logic = lua code);
a request distribution policy (version n _ dispatch, e.g., version n _ dispatch = redirect/forward) for each alternate version, the request distribution policy being used to indicate whether a server internally forwards to the url of the version n or redirects to the url of the version n when distributing a request;
whether each alternate version is executed in background (such as version n _ background = 0/1), if so, it means that the traffic is copied to version n without performing gray-scale logic;
exception handling rules for each alternate version for configuring at least one exception logic and corresponding solutions in the presence of the exception logic, wherein the exception logic preferably includes, but is not limited to, at least one of the following conditions:
generating an erroneous response status code (versionjerror _ status, such as versionjerror _ status =404,500,502, 503);
an access timeout (version n _ timeout, e.g., version n _ timeout =5 s);
access current limit (version n _ limit, e.g., version n _ limit = 100/s);
the solutions corresponding to the above conditions may be the same or different, and the solutions of the present embodiment preferably include but are not limited to: forwarding the access request to the original version.
The verification logic is to verify whether the contents of the alternate version are correct. Configuration items for implementing the verification logic may include, but are not limited to, configuration:
a verification rule (version n _ validity _ rule, for example, version n _ validity _ rule = lua code) is used to verify whether the content of version n is correct, and if 0 is returned, it indicates that the verification fails.
The configuration items of each alternative version can be the same or different according to actual requirements. The specific configuration of each configuration item can be the same or different according to actual needs.
Fig. 5 shows a Web service gradation distribution control apparatus of the present embodiment. For the gray scale control logic of the present embodiment, the Web service gray scale distribution control apparatus 50 includes a receiving module 51, an obtaining module 52, a judging module 53, a forwarding module 54, an exception handling module 55, and a verifying module 56.
The receiving module 51 is configured to receive an access request of a client, where the access request includes a request URL, a source IP, a request parameter, and a request header, where the request URL is used to indicate a Web service that is requested to be accessed.
The obtaining module 52 is configured to obtain the KEY as the grayscale policy of the request URL by using the request URL.
The determining module 53 is configured to determine whether the candidate version configured by the grayscale control logic is empty, if so, invoke the forwarding module 54 to forward the access request to the URL of the original version, if not, execute the control logic of each candidate version one by one until finding the candidate version hit by the value of the client on the preset information, then regard the hit candidate version as the corresponding candidate version, invoke the forwarding module 54 to forward the access request to the URL of the corresponding candidate version, and if not, invoke the forwarding module 54 to forward the access request to the URL of the original version.
When the forwarding module 54 forwards the access request to the URL of the corresponding alternative version, it needs to perform request distribution according to the request distribution policy, if the access request is forwarded, it indicates that the access request is forwarded to the URL of the corresponding alternative version inside the server, and if the access request is redirected, it indicates that the access request is redirected to the URL of the corresponding alternative version; and if the corresponding alternative version is configured to be executed in the background, the background forwards the access request to the corresponding alternative version, and judges whether the corresponding alternative version is correct or not by observing a log under the condition of not being online.
The exception handling module 55 is configured to, after forwarding the access request to the URL of the corresponding candidate version, determine whether any exception logic occurs, including whether a response status code is correct after forwarding a return response, whether timeout occurs, and whether current limiting occurs, and if any exception logic occurs, invoke the forwarding module 54 to forward the access request to the URL of the original version.
The verification module 56 is configured to, after forwarding the access request to the URL of the corresponding alternative version, verify whether the response result of the alternative version is correct according to the verification logic, and if the verification is incorrect, invoke the forwarding module 54 to forward the access request to the URL of the original version.
In the embodiment, the control of gray release is very flexible, multi-version gray can be supported, the configuration of gray can be supported, complex gray control and verification logic can be supported, the function of gray verification by flow can be copied, abnormal logic can be flexibly and adaptively processed, the gray can be quickly and automatically degraded to the original version for processing when problems occur, user experience is not influenced, and therefore flexible multi-version gray is achieved.
The Web grayscale service distribution control apparatuses 40 and 50 in embodiments 4 and 5 can be implemented by using a nginnx access layer (or by using other techniques similar to the nginnx, such as writing an access layer in the go language) + lua.
Example 6
Fig. 6 shows a gradation control system of the present embodiment. The gradation control system 60 includes: the module 61 is configured. The configuration module 61 is configured to configure a grayscale policy.
In this embodiment, the grayscale strategy includes grayscale control logic. The gray control logic is used for configuring at least one alternative version which is distinguished by the Web service according to the preset information and is appointed to access. The gray control logic of this embodiment indicates that the client has different values in the preset information, and the alternative versions of the Web service designated for access are different.
In this embodiment, the preset information includes at least one of an IP, a uid, a User-Agent, and a third-party service caller, and compared with the conventional gray-scale distribution, the preset information is more information capable of supporting gray-scale, so that the entire gray-scale distribution is more flexible.
The gray scale strategy can be specifically configured with a plurality of configuration items, which is beneficial to realizing more complex gray scale control. The configuration items for implementing the gray scale control logic may include, but are not limited to, configuration items:
KEY (KEY, e.g., KEY = request URL) for matching of grayscale policy;
URL of the original version (old _ version _ URL);
the Web service specifies at least one alternative version of access (version, such as version = version N, N is a positive integer);
URL of each alternative version (version N _ URL, which may be a relative path such as/tem/v 1, or an absolute path such as server internal forwarding address http:// a.local/item/v1, redirection address http:// a.com/item/v 1);
control logic for each alternate version (version n _ control _ logic, e.g., version n _ control _ logic = lua code);
a request distribution policy (versionjdispatch, such as versionjdispatch = redirect/forward) for each alternate version, the request distribution policy being used to indicate whether a server internally forwards to the url of versionN or redirects to the url of versionN when distributing a request;
whether each alternative version is executed in the background (such as version n _ background = 0/1), if so, it means that the traffic is copied to version n without executing the gray logic;
exception handling rules for each alternate version, the exception handling rules for configuring at least one exception logic and corresponding solutions when the exception logic occurs, wherein the exception logic preferably includes, but is not limited to, at least one of the following conditions:
generating an error response status code (version n _ error _ status, e.g., version n _ error _ status =404,500,502, 503);
an access timeout (version n _ timeout, e.g., version n _ timeout =5 s);
access limit (version _ limit, e.g., version _ limit = 100/s);
the solutions for the above conditions may be the same or different, and the solutions of the present embodiment preferably include but are not limited to: forwarding the access request to the original version.
In this embodiment, the grayscale policy may further include a verification logic. The verification logic is to verify whether the contents of the alternate version are correct. Configuration items for implementing the verification logic may include, but are not limited to, configuration:
a verification rule (version n _ validity _ rule, for example, version n _ validity _ rule = lua code) is used to verify whether the content of version n is correct, and if 0 is returned, it indicates that the verification fails.
The configuration items of each alternative version may be the same or different according to actual needs. The specific configuration of each configuration item can be the same or different according to actual needs.
The gray scale control system 60 of the present embodiment may be used alone to implement the configuration of the complex gray scale policy, or may be used in conjunction with the Web service gray scale distribution control apparatus 40 or 50 in embodiment 4 or embodiment 5, for example:
a Web service system as shown in fig. 7 includes a Web service gradation issuance control apparatus 40 or 50 and a gradation control system 60. The Web service gray scale release control device 40 or 50 calls the gray scale control system 60 after receiving the access request of the client, and the gray scale control system 60 returns the gray scale strategy matched with the Web service to the Web service gray scale release control device 40 or 50 to ensure the gray scale control. The Web service system may further include a Web server 70 that publishes the original version and a Web server 80 that publishes the alternative version.
Example 7
Fig. 8 is a schematic structural diagram of an electronic device according to embodiment 7 of the present invention. The electronic device comprises a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor executes the program to implement the method of any one of embodiments 1-3. The electronic device 90 shown in fig. 8 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiment of the present invention.
As shown in fig. 8, the electronic device 90 may take the form of a general purpose computing device, which may be a server device, for example. The components of the electronic device 90 may include, but are not limited to: the at least one processor 91, the at least one memory 92, and a bus 93 that connects the various system components (including the memory 92 and the processor 91).
The bus 93 includes a data bus, an address bus, and a control bus.
The processor 91 executes various functional applications and data processing, such as any one of the methods provided in embodiments 1-3 of the present invention, by running a computer program stored in the memory 92.
The electronic device 90 may also communicate with one or more external devices 94 (e.g., keyboard, pointing device, etc.). Such communication may be through an input/output (I/O) interface 95. Also, the model-generating device 90 may also communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the Internet) via a network adapter 96. As shown, the network adapter 96 communicates with the other modules of the model-generating device 90 via a bus 93. It should be understood that although not shown in the figures, other hardware and/or software modules may be used in conjunction with the model-generating device 90, including but not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID (disk array) systems, tape drives, and data backup storage systems, etc.
It should be noted that although in the above detailed description several units/modules or sub-units/modules of the electronic device are mentioned, such a division is merely exemplary and not mandatory. Indeed, the features and functions of two or more of the units/modules described above may be embodied in one unit/module according to embodiments of the invention. Conversely, the features and functions of one unit/module described above may be further divided into embodiments by a plurality of units/modules.
Example 9
The present embodiment provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of any one of the methods provided in embodiments 1-3.
More specific examples, among others, that the readable storage medium may employ may include, but are not limited to: a portable disk, a hard disk, random access memory, read only memory, erasable programmable read only memory, optical storage device, magnetic storage device, or any suitable combination of the foregoing.
In a possible implementation, the invention can also be implemented in the form of a program product comprising program code means for causing a terminal device to carry out the steps of implementing any of the methods according to embodiments 1-3 when said program product is run on said terminal device.
Where program code for carrying out the invention is written in any combination of one or more programming languages, the program code may be executed entirely on the user device, partly on the user device, as a stand-alone software package, partly on the user device and partly on a remote device or entirely on the remote device.
While specific embodiments of the invention have been described above, it will be appreciated by those skilled in the art that these are by way of example only, and that the scope of the invention is defined by the appended claims. Various changes and modifications to these embodiments may be made by those skilled in the art without departing from the spirit and scope of the invention, and these changes and modifications are within the scope of the invention.
Claims (23)
1. A gray release control method for Web services is characterized in that the Web services have an original version and at least one alternative version, and the method comprises the following steps:
receiving an access request of a client, wherein the access request is used for requesting to access the Web service;
acquiring a gray level strategy matched with the Web service, wherein the gray level strategy comprises a gray level control logic, and the gray level control logic is used for configuring at least one alternative version of specified access distinguished by the Web service according to preset information;
judging whether an alternative version corresponding to the value of the client on the preset information exists or not according to the gray control logic;
if so, forwarding the access request to the corresponding alternative version;
if not, forwarding the access request to the original version;
the gray control logic is configured with at least one alternative version appointed to be accessed by the Web service and control logic of each alternative version;
according to the gray control logic, the step of judging whether the alternative version corresponding to the value of the client on the preset information exists or not comprises the following steps:
judging whether the alternative version of the gray control logic configuration is empty or not;
if the version is empty, forwarding the access request to the original version;
if not, then:
executing the control logic of the alternative versions one by one until finding out the alternative version hit by the value of the client on the preset information, taking the hit alternative version as the corresponding alternative version, and forwarding the access request to the corresponding alternative version;
if the value of the client on the preset information does not hit any alternative version, forwarding the access request to the original version;
the gray control logic is also configured with a request distribution strategy of each alternative version;
when the access request is forwarded to the corresponding alternative version, the method distributes the request according to the request distribution strategy;
wherein the request distribution policy indicates whether a server internally forwards a URL of the alternative version or redirects the URL of the alternative version when distributing the access request;
the gray control logic is also configured with whether each alternative version is executed in the background;
when the access request is forwarded to the corresponding alternative version, if the corresponding alternative version is configured to be executed in a background, the access request is forwarded to the corresponding alternative version in the background;
when the method is executed in the background, the flow corresponding to the access request is copied to the corresponding alternative version, and the gray control logic is not executed at the moment.
2. The Web service gray scale release control method of claim 1, wherein the access request includes a request URL, the gray scale control logic is configured with a URL of an alternate version and a URL of the original version that the Web service specifies to access;
forwarding the access request to the corresponding alternate version comprises: forwarding the access request to the URL of the corresponding alternative version;
forwarding the access request to the original version comprises: forwarding the access request to the original version of the URL.
3. The Web service gray scale release control method of claim 1, wherein the preset information comprises at least one of IP, uid, user-Agent, and third party service caller.
4. The Web service gray scale release control method according to claim 1, wherein the gray scale control logic is further configured with an exception handling rule for each alternative version, the exception handling rule is used for configuring at least one exception logic and a corresponding solution when the exception logic occurs;
the method also comprises the steps of judging whether any one abnormal logic occurs after the access request is forwarded to the corresponding alternative version, and executing a corresponding solution if the abnormal logic occurs;
wherein the exception logic includes at least one of the following conditions:
generating an erroneous response status code;
an access timeout;
accessing a current limit;
the solution comprises the following steps: forwarding the access request to the original version.
5. The Web service gray scale release control method of claim 1, wherein the gray scale policy further comprises a verification logic for verifying whether the content of the alternative version is correct;
the method further comprises the following steps: after the access request is forwarded to the corresponding alternative version, verifying whether the response result of the alternative version is correct or not according to the verification logic;
and if the access request is wrong, forwarding the access request to the original version.
6. A method of gray scale control, the method comprising:
configuring a gray level strategy, wherein the gray level strategy comprises a gray level control logic, and the gray level control logic is used for configuring at least one alternative version of specified access distinguished by the Web service according to preset information;
the gray control logic is configured with at least one alternate version of the specified access of the Web service, and the following:
control logic for each alternate version;
a request distribution strategy of each alternative version;
whether each alternate version is executing in the background.
7. The method of claim 6, wherein the predetermined information comprises at least one of IP, uid, user-Agent, and third party service caller.
8. The method of claim 6, wherein the gray scale control logic is configured with at least one of:
a URL of an original version of the Web service;
the URL of each alternative version;
exception handling rules for each alternate version, the exception handling rules configured to configure at least one exception logic and a corresponding solution when the exception logic occurs, wherein the exception logic includes at least one of the following conditions:
generating an error response status code;
an access timeout;
accessing a current limit;
the solution comprises: an access request is forwarded to the original version.
9. The gray scale control method of claim 6, wherein said gray scale strategy further comprises a verification logic for verifying whether the contents of said alternate version are correct.
10. A Web service gray scale release control device is characterized in that the Web service has an original version and at least one alternative version, and the device comprises: the device comprises a receiving module, an obtaining module, a judging module and a forwarding module;
the receiving module is used for receiving an access request of a client, and the access request is used for requesting to access the Web service;
the acquisition module is used for acquiring a gray strategy matched with the Web service, the gray strategy comprises a gray control logic, and the gray control logic is used for configuring at least one alternative version of specified access distinguished by the Web service according to preset information;
the judging module is used for judging whether an alternative version corresponding to the value of the client on the preset information exists or not according to the gray control logic, if so, the forwarding module is called to forward the access request to the corresponding alternative version, and if not, the forwarding module is called to forward the access request to the original version;
the gray control logic is configured with at least one alternative version appointed to be accessed by the Web service and control logic of each alternative version;
the judging module is used for judging whether the alternative versions configured by the gray control logic are empty or not, if so, the forwarding module is called to forward the access request to the original version, if not, the control logic of each alternative version is executed one by one until the alternative version hit by the value of the client on the preset information is found, then the hit alternative version is used as the corresponding alternative version, the forwarding module is called to forward the access request to the corresponding alternative version, and if the value of the client on the preset information does not hit any alternative version, the forwarding module is called to forward the access request to the original version;
the gray control logic is also configured with a request distribution strategy of each alternative version;
when the forwarding module forwards the access request to the corresponding alternative version, request distribution is carried out according to the request distribution strategy;
the gray control logic is also configured to determine whether each alternative version is executed in the background;
when the forwarding module forwards the access request to the corresponding alternative version, if the corresponding alternative version is configured to be executed in a background, the forwarding module forwards the access request to the corresponding alternative version in the background.
11. The Web service grayscale publication control of claim 10 wherein the access request includes a request URL, the grayscale control logic being configured with a URL of an alternate version and a URL of the original version that the Web service specifies to access;
forwarding the access request to the corresponding alternate version comprises: forwarding the access request to the URL of the corresponding alternative version;
forwarding the access request to the original version comprises: forwarding the access request to the original version of the URL.
12. The apparatus as claimed in claim 10, wherein the predetermined information includes at least one of IP, uid, user-Agent and third party service caller.
13. The Web service gray scale release control apparatus according to claim 10, wherein the gray scale control logic is further configured with an exception handling rule for each alternative version, the exception handling rule is used for configuring at least one exception logic and a corresponding solution when the exception logic occurs;
the device further comprises:
an exception handling module, configured to determine whether any one of the exception logics occurs after the access request is forwarded to the corresponding alternative version, and if so, execute a corresponding solution;
wherein the exception logic includes at least one of the following conditions:
generating an erroneous response status code;
an access timeout;
accessing a current limit;
the solution comprises the following steps: and calling the forwarding module to forward the access request to the original version.
14. The Web service grayscale release control of claim 10 wherein the grayscale policy further includes verification logic to verify whether the alternate version of content is correct;
the device further comprises:
and the verification module is used for verifying whether the response result of the alternative version is correct or not according to the verification logic after the access request is forwarded to the corresponding alternative version, and calling the forwarding module to forward the access request to the original version if the response result of the alternative version is wrong.
15. A gray scale control system, the system comprising:
the system comprises a configuration module, a storage module and a management module, wherein the configuration module is used for configuring a gray policy, the gray policy comprises a gray control logic, and the gray control logic is used for configuring at least one alternative version of specified access distinguished by Web service according to preset information;
the gray control logic is configured with at least one alternate version of the specified access of the Web service, and the following:
control logic for each alternate version;
request distribution strategy of each alternative version;
whether each alternate version is executing in the background.
16. The system of claim 15, wherein the predetermined information comprises at least one of IP, uid, user-Agent, and third party service caller.
17. The gamma control system of claim 15, wherein the gamma control logic is configured with at least one of:
a URL of an original version of the Web service;
the URL of each alternative version;
exception handling rules for each alternate version, the exception handling rules for configuring at least one exception logic and a corresponding solution upon occurrence of the exception logic, wherein the exception logic includes at least one of the following conditions:
generating an error response status code;
an access timeout;
accessing a current limit;
the solution comprises the following steps: an access request is forwarded to the original version.
18. The grayscale control system of claim 15 wherein said grayscale policy further includes verification logic for verifying whether the contents of said alternate version are correct.
19. A Web service system, characterized in that the Web service system comprises the Web service gray scale distribution control device of any one of claims 10 to 14 and the gray scale control system of any one of claims 15 to 18;
and the Web service gray level release control device calls the gray level control system after receiving the access request of the client, and the gray level control system returns the gray level strategy matched with the Web service to the Web service gray level release control device.
20. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the Web service gray scale distribution control method according to any one of claims 1 to 5 when executing the program.
21. A computer-readable storage medium on which a computer program is stored, characterized in that the program, when executed by a processor, implements the steps of the Web service gray scale issuance control method according to any one of claims 1 to 5.
22. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the method of gray scale control of any one of claims 6 to 9 when executing the program.
23. A computer-readable storage medium, on which a computer program is stored, characterized in that the program, when being executed by a processor, carries out the steps of the gray-scale control method according to any one of claims 6 to 9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910055325.2A CN109787830B (en) | 2019-01-21 | 2019-01-21 | Gray scale distribution control method, device, system, electronic device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910055325.2A CN109787830B (en) | 2019-01-21 | 2019-01-21 | Gray scale distribution control method, device, system, electronic device and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109787830A CN109787830A (en) | 2019-05-21 |
| CN109787830B true CN109787830B (en) | 2023-03-07 |
Family
ID=66501038
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910055325.2A Active CN109787830B (en) | 2019-01-21 | 2019-01-21 | Gray scale distribution control method, device, system, electronic device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109787830B (en) |
Families Citing this family (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110311989B (en) * | 2019-08-02 | 2022-01-28 | 中国工商银行股份有限公司 | Gray scale publishing method, device, storage medium, equipment and system |
| CN110471712A (en) * | 2019-08-12 | 2019-11-19 | 广州华多网络科技有限公司 | Switching method, device, server and the storage medium of cross-system service |
| CN110457223B (en) * | 2019-08-13 | 2023-08-22 | 中国联合网络通信集团有限公司 | Gray test drainage method, device, proxy server and readable storage medium |
| CN110532024A (en) * | 2019-08-28 | 2019-12-03 | 维沃移动通信有限公司 | A kind of version optimization method, device, server and the storage medium of application program |
| CN110798502B (en) * | 2019-09-18 | 2022-06-17 | 平安科技（深圳）有限公司 | Grayscale publishing method and device based on micro-service framework and computer equipment |
| CN110912734B (en) * | 2019-10-31 | 2022-07-22 | 北京浪潮数据技术有限公司 | Method and device for realizing multi-dimensional gray scale release of container application by cloud management platform |
| CN112838936B (en) * | 2019-11-22 | 2023-05-26 | 北京金山云网络技术有限公司 | Resource speed limiting method, device, user terminal and server |
| CN111488159A (en) * | 2019-12-20 | 2020-08-04 | 杭州当虹科技股份有限公司 | Gray scale publishing method capable of being dynamically configured |
| CN113050978B (en) * | 2019-12-26 | 2024-03-19 | 中国移动通信集团北京有限公司 | Gray release control method, device and equipment for application and computer storage medium |
| CN112532602A (en) * | 2020-11-20 | 2021-03-19 | 中国联合网络通信集团有限公司 | Gray scale publishing method, equipment and server |
| CN112653579B (en) * | 2020-12-16 | 2023-05-23 | 中国人寿保险股份有限公司 | Gray release method based on OpenResity and related equipment |
| CN114125067A (en) * | 2021-02-10 | 2022-03-01 | 北京沃东天骏信息技术有限公司 | Front-end and back-end separated gray scale publishing method, front-end server and configuration server |
| CN113452622A (en) * | 2021-06-29 | 2021-09-28 | 上海通联金融服务有限公司 | Gray level shunting method based on client |
| CN113568655A (en) * | 2021-07-26 | 2021-10-29 | 河北幸福消费金融股份有限公司 | Gray scale distribution system, method and storage medium |
| CN113905246B (en) * | 2021-09-10 | 2023-12-15 | 微梦创科网络科技（中国）有限公司 | Live broadcasting room implementation method and device |
| CN114615135B (en) * | 2022-02-18 | 2024-03-22 | 佐朋数科(深圳)信息技术有限责任公司 | Front-end gray level publishing method, system and storage medium |
| CN114710550A (en) * | 2022-03-18 | 2022-07-05 | 中国建设银行股份有限公司 | Request response method, device, equipment and computer storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104378304A (en) * | 2013-08-14 | 2015-02-25 | 腾讯科技（深圳）有限公司 | Gray scale issuing control method, device and system |
| CN104993946A (en) * | 2015-06-01 | 2015-10-21 | 华为技术有限公司 | Evaluation method, device and system for gated launch |
| CN105099988A (en) * | 2014-04-24 | 2015-11-25 | 阿里巴巴集团控股有限公司 | Method used for supporting gray releasing, access method, devices and system |
| CN106648562A (en) * | 2015-10-29 | 2017-05-10 | 腾讯科技（深圳）有限公司 | Version updating method and device |
| CN106998369A (en) * | 2017-05-26 | 2017-08-01 | 努比亚技术有限公司 | Gray scale dissemination method, gateway blocker and computer-readable recording medium |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2017174233A (en) * | 2016-03-24 | 2017-09-28 | キヤノン株式会社 | Information processing apparatus, method, and program |
| CN108632374B (en) * | 2018-05-09 | 2021-06-18 | 恒大智慧科技有限公司 | Software gray level release method and device |
-
2019
- 2019-01-21 CN CN201910055325.2A patent/CN109787830B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104378304A (en) * | 2013-08-14 | 2015-02-25 | 腾讯科技（深圳）有限公司 | Gray scale issuing control method, device and system |
| CN105099988A (en) * | 2014-04-24 | 2015-11-25 | 阿里巴巴集团控股有限公司 | Method used for supporting gray releasing, access method, devices and system |
| CN104993946A (en) * | 2015-06-01 | 2015-10-21 | 华为技术有限公司 | Evaluation method, device and system for gated launch |
| CN106648562A (en) * | 2015-10-29 | 2017-05-10 | 腾讯科技（深圳）有限公司 | Version updating method and device |
| CN106998369A (en) * | 2017-05-26 | 2017-08-01 | 努比亚技术有限公司 | Gray scale dissemination method, gateway blocker and computer-readable recording medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109787830A (en) | 2019-05-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109787830B (en) | Gray scale distribution control method, device, system, electronic device and storage medium | |
| US11144439B2 (en) | Emulation-based testing of a microservices architecture | |
| JP6445222B2 (en) | System, method, and computer-readable storage medium for customizable event-triggered calculations at edge positions | |
| US7493518B2 (en) | System and method of managing events on multiple problem ticketing system | |
| US7949999B1 (en) | Providing support for multiple interface access to software services | |
| US9665465B1 (en) | Automated determination of application permissions | |
| US9497096B2 (en) | Dynamic control over tracing of messages received by a message broker | |
| US11726800B2 (en) | Remote component loader | |
| CN105743945B (en) | Document down loading method and system based on switching loading source | |
| WO2012010583A1 (en) | On-demand translation of application text | |
| CN112131504B (en) | Webpage editing and displaying method, device, equipment and storage medium | |
| CN110324209B (en) | Micro-service system monitoring method and device, electronic equipment and computer readable medium | |
| WO2023207146A1 (en) | Service simulation method and apparatus for esop system, and device and storage medium | |
| CN108664343B (en) | State calling method and device for micro-service | |
| CN111510330B (en) | Interface management device, method and storage medium | |
| US9374417B1 (en) | Dynamic specification auditing for a distributed system | |
| US9823999B2 (en) | Program lifecycle testing | |
| US7721278B2 (en) | Modular server architecture for multi-environment HTTP request processing | |
| CN111913738A (en) | Access request processing method, device, computing equipment and medium | |
| US7853956B2 (en) | Message system and method | |
| CN110716730B (en) | Gray release method, device, equipment and computer readable storage medium | |
| US20200382447A1 (en) | Chatbot information processing | |
| CN110704777A (en) | Method and system for implementing gray scale publishing | |
| CN113946376B (en) | Load adjustment method and device, electronic equipment and storage medium | |
| CN115250233A (en) | Gray scale routing control method, gray scale routing assembly and computer equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |