CN114615135B - Front-end gray level publishing method, system and storage medium - Google Patents
Front-end gray level publishing method, system and storage medium Download PDFInfo
- Publication number
- CN114615135B CN114615135B CN202210149835.8A CN202210149835A CN114615135B CN 114615135 B CN114615135 B CN 114615135B CN 202210149835 A CN202210149835 A CN 202210149835A CN 114615135 B CN114615135 B CN 114615135B
- Authority
- CN
- China
- Prior art keywords
- gray
- rule
- gray scale
- gray level
- request
- 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
- 238000000034 method Methods 0.000 title claims abstract description 38
- 238000003860 storage Methods 0.000 title claims abstract description 15
- 238000012545 processing Methods 0.000 claims abstract description 37
- 238000004806 packaging method and process Methods 0.000 claims abstract description 12
- 230000004044 response Effects 0.000 claims abstract description 8
- 230000003068 static effect Effects 0.000 claims description 14
- 238000009826 distribution Methods 0.000 claims description 12
- 235000014510 cooky Nutrition 0.000 claims description 6
- 238000012856 packing Methods 0.000 claims description 5
- 230000002085 persistent effect Effects 0.000 claims description 4
- 238000010276 construction Methods 0.000 description 6
- 230000006870 function Effects 0.000 description 6
- 238000004519 manufacturing process Methods 0.000 description 3
- 241001270131 Agaricus moelleri Species 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000002441 reversible effect Effects 0.000 description 2
- 238000012163 sequencing technique Methods 0.000 description 2
- 230000005856 abnormality Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000005316 response function Methods 0.000 description 1
- 238000000926 separation method Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 238000010200 validation analysis Methods 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Stored Programmes (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention discloses a front-end gray level publishing method, a system and a storage medium, wherein the method comprises the following steps: after the coding of the codes is completed, packaging the gray level version defaults, and deploying and releasing gray level codes to gray level catalogues, wherein the gray level catalogue names adopt the form of normal catalogue names and gray level version numbers; when a client request is received, the client request is forwarded to a lua gray level processing module through an openness nginx according to the request resource type; acquiring a gray rule from a preset gray rule list through the lua gray processing module, and executing the gray rule to obtain a gray resource path; notifying the nginx gray scale resource path and continuing to execute the response. Compared with the prior art, the invention realizes that the gray processing logic is extracted, uniformly configured and deployed by utilizing the existing machine resources on the premise of not changing the URL path identification, realizes one-key gray switching of gray, and flexibly defines the gray rule.
Description
Technical Field
The present invention relates to the field of information technologies, and in particular, to a front end gray level publishing method, system, and storage medium.
Background
Under the great background of current front-end and back-end technology separation, the traditional forms of depending on the back-end application to distinguish judging versions and dynamically responding to web pages are not feasible, and the current front-end gray level schemes mainly comprise the following steps:
1. in the front-end project code, different contents are dynamically judged and displayed according to the information of the current login user, the role, the userAgents, other equipment and the like, the code is difficult to maintain, when a plurality of versions coexist, the code maintenance amount is multiplied, and when the gray is finished, related gray logic is required to be deleted, so that the work is repeated;
2. different versions are marked through different URLs, and different gray links are issued for users needing gray versions, but the links are used as application identifiers and can be widely spread, so that the users can be misunderstood to a certain extent, and when gray ends, the links are compatible to point to stable versions, and the later workload is increased;
3. the grey scale items are deployed on separate machines, and traffic is directed to the grey scale machines by distinguishing the identification of IP, proxy, etc., but this causes additional waste of resources and cannot be distinguished according to the identity of the user, and at the same time, special treatment is required for the use of cdn.
Disclosure of Invention
The invention mainly aims to provide a front-end gray level publishing method, a system and a storage medium, which aim to solve the problems that on the premise of not changing URL path identification, existing machine resources are utilized to extract gray level processing logic, the gray level processing logic is uniformly configured and deployed, one-key gray level switching of gray level is realized, and gray level rules are flexibly defined.
In order to achieve the above object, the present invention provides a front-end gray level distribution method, which includes the following steps:
step S10, after the coding of the codes is completed, packaging the gray level version devots and deploying and releasing gray level codes to a gray level directory, wherein the gray level directory name adopts the form of normal directory name plus gray level version number;
step S20, when a client request is received, the client request is forwarded to a lua gray level processing module through openrestynginx according to the request resource type;
step S30, acquiring gray rules from a preset gray rule list through the lua gray processing module, and executing the gray rules to obtain a gray resource path;
step S40, notifying the nginx gray scale resource path, and continuing to execute response.
The further technical scheme of the present invention is that step S10, after the encoding of the code is completed, includes the steps of packaging the gray scale version devops and deploying the release gray scale code to the gray scale catalog:
pre-drawing a gray version number;
step S10, after the encoding of the code is completed, the step of packaging the gray scale version devops and deploying the release gray scale code to the gray scale directory includes:
after the coding of the codes is finished, the grayscale version number is automatically added in front of the static resource path in the page through a weback construction system, and then the independent packing mode is adopted, and the codes are automatically packed and deployed to the grayscale catalog by using a release system.
The further technical scheme of the present invention is that, when receiving a client request, the step S20 of forwarding the client request to the lua gray scale processing module through the openness ginx according to the request resource type includes:
when a client request is received, distinguishing the request resource type;
determining a processing mode according to the request resource type, uniformly forwarding a request of an html file to a lua gray level module for processing, and setting a spam policy, and responding to a normal version by adopting the spam policy when the gray level module is unavailable and errors are caused or gray level versions are not matched; when cdn back source processing is needed for the static resource part, a gray resource path is determined according to whether gray version identification exists in the matched static resource url.
The further technical scheme of the present invention is that the step S30, the step of obtaining the gray scale rule from the preset gray scale rule list by the lua gray scale processing module, and executing, the step of obtaining the gray scale resource path includes:
after the lua gray processing module receives the forwarded client request, extracting information carried by the client request, pulling a preset gray rule list, executing according to the rule sequence, determining a gray resource path according to a gray version number corresponding to any rule once the rule is matched, and returning to the nginx for continuous execution.
The invention further adopts the technical scheme that the information carried by the client request at least comprises one or more of userAgent, IP, cookie, header and request body information of a user.
The further technical solution of the present invention is that, the step S40 of notifying the nginx gray scale resource path and continuously executing the response includes:
and finding out a target file according to the gray resource path and responding.
The further technical scheme of the present invention is that the step S30, by which the lua gray scale processing module obtains gray scale rules from a preset gray scale rule list and executes, includes, before the step of obtaining a gray scale resource path:
and dynamically managing and setting gray rules and gray versions, and establishing a gray rule table of association relation between the gray rules and the gray versions.
In the step of dynamically managing and setting the gray rule and the gray version and establishing the gray rule table of the association relation between the gray rule and the gray version, each gray rule supports the input of a custom lua script, the priority of gray matching is realized through rule sequencing, one-key switching is carried out on the rule under each version number, and the finally effective rule list is synchronously written into the cache service while persistent storage is carried out for each operation.
To achieve the above object, the present invention also proposes a front-end tone distribution system comprising a memory, a processor, and a front-end tone distribution program stored on the processor, which when executed by the processor performs the steps of the method as described above.
To achieve the above object, the present invention also proposes a computer-readable storage medium having stored thereon a front-end tone distribution program which, when executed by a processor, performs the steps of the method as described above.
The front-end gray level publishing method, the front-end gray level publishing system and the storage medium have the beneficial effects that: according to the technical scheme, after the coding of the codes is completed, the gray scale version devots is packaged and distributed to release gray scale codes to the gray scale catalogue, wherein the gray scale catalogue name adopts the form of normal catalogue name plus gray scale version number; when a client request is received, the client request is forwarded to a lua gray level processing module through an openness nginx according to the request resource type; acquiring a gray rule from a preset gray rule list through the lua gray processing module, and executing the gray rule to obtain a gray resource path; the method includes the steps of notifying a nginx gray scale resource path, and continuously executing response, so that gray scale processing logic is extracted by using the existing machine resources on the premise of not changing URL path identification, and is uniformly configured and deployed, one-key gray scale switching of gray scales is realized, and gray scale rules are flexibly defined.
Drawings
FIG. 1 is a schematic overall flow chart of a front-end gray level distribution method according to a preferred embodiment of the present invention;
FIG. 2 is a system architecture diagram of a front-end gray scale distribution system;
FIG. 3 is a flow chart of a gray code packaging and publishing system;
FIG. 4 is a flow chart of a gray association rule system;
fig. 5 is a flowchart of a gray matching execution system.
Detailed Description
It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention.
The achievement of the objects, functional features and advantages of the present invention will be further described with reference to the accompanying drawings, in conjunction with the embodiments.
Referring to fig. 1 to 5, in order to solve the problem that the gray scale processing logic is extracted, uniformly configured and deployed by using the existing machine resources on the premise of not changing the URL path identifier, and the gray scale rule is flexibly defined by implementing one-key gray scale switch of gray scale, the present invention provides a front-end gray scale publishing method, and a preferred embodiment of the front-end gray scale publishing method includes the following steps:
step S10, after the coding of the codes is completed, packaging and deploying release gray codes to gray catalogues by gray version devots, wherein the gray catalogue names are in the form of normal catalogue names and gray version numbers.
In the invention, in the normal packing deployment process, a gray scale process is introduced, and a construction server automatically processes a gray scale compatible path according to the gray scale version number, and the compatible process cdn returns to the source access.
And step S20, when a client request is received, the client request is forwarded to the lua gray level processing module through openrestynginx according to the request resource type.
Step S30, obtaining gray scale rules from a preset gray scale rule list through the lua gray scale processing module, and executing the gray scale rules to obtain a gray scale resource path.
Step S40, notifying the nginx gray scale resource path, and continuing to execute response.
Specifically, in this embodiment, the step S10, after the encoding of the code is completed, includes, before the step of packaging and deploying the release of the gray code to the gray directory, the steps of:
the version number of the gray scale is drawn up in advance.
Step S10, after the encoding of the code is completed, the step of packaging the gray scale version devops and deploying the release gray scale code to the gray scale directory includes:
after the coding of the codes is finished, the grayscale version number is automatically added in front of the static resource path in the page through a weback construction system, and then the independent packing mode is adopted, and the codes are automatically packed and deployed to the grayscale catalog by using a release system.
In this embodiment, the step S20, when receiving a client request, transfers the client request to the lua gray scale processing module through the openness nginx according to the request resource type, includes:
when a client request is received, distinguishing the request resource type;
determining a processing mode according to the request resource type, uniformly forwarding a request of an html file to a lua gray level module for processing, and setting a spam policy, and responding to a normal version by adopting the spam policy when the gray level module is unavailable and errors are caused or gray level versions are not matched; when cdn back source processing is needed for the static resource part, a gray resource path is determined according to whether gray version identification exists in the matched static resource url.
In this embodiment, the step of obtaining the gray scale resource path by the lua gray scale processing module obtaining the gray scale rule from the preset gray scale rule list and executing the gray scale rule comprises:
after the lua gray processing module receives the forwarded client request, extracting information carried by the client request, pulling a preset gray rule list, executing according to the rule sequence, determining a gray resource path according to a gray version number corresponding to any rule once the rule is matched, and returning to the nginx for continuous execution.
The information carried by the client request at least comprises one or more of userAgent, IP, cookie, header, a request body and the like of a user.
In this embodiment, the step S40 of notifying the nginx gray resource path and continuing to execute the response includes:
and finding out a target file according to the gray resource path and responding.
In this embodiment, the step S30, by the lua gray scale processing module, obtains a gray scale rule from a preset gray scale rule list, and executes the gray scale rule, and before the step of obtaining a gray scale resource path, includes:
and dynamically managing and setting gray rules and gray versions, and establishing a gray rule table of association relation between the gray rules and the gray versions.
Specifically, in the step of dynamically managing and setting the gray rule and the gray version, and establishing the gray rule table of the association relationship between the gray rule and the gray version, each gray rule supports the input of a custom lua script, realizes the priority of gray matching through rule sequencing, performs one-key switching on the rule under each version number, and synchronously writes the rule list which is finally effective into cache services such as redis while performing persistent storage in each operation.
The front-end gray level distribution method of the present invention is further described in detail below.
The front-end gray level release method can be applied to a front-end gray level release system, wherein the front-end gray level release system provides a gray level code automatic packaging deployment system, a gray level rule management system and a gray level matching execution system.
1. Gray code automatic packaging deployment system
In the normal packing deployment flow, a gray scale flow is introduced, and the construction server automatically processes the gray scale resource path according to the gray scale version number, and compatible processing cdn returns source access.
And (3) automatically deploying the project, connecting the construction server with the production server in a scp mode and the like, and deploying the construction server into a gray scale catalog of the production server according to the gray scale version number.
2. Gray scale rule management system
The system comprises an employee identity authority management function, logs in through employee identity authentication, and determines project configuration authorities according to employee roles.
The system comprises a rule configuration function, allows a user to input a rule script in the form of lua grammar through online editing capability, the rule script is logically written strictly according to rule variables provided by a gray level matching execution system, and the script grammar is checked when the rule is stored so as to avoid error rules.
The system comprises a function of associating the rule with the gray version number, and firstly, we should determine the relation between the gray rule and the gray version number. The method of AB test is extended, the number of versions is not limited in theory, and multiple sets of versions of 1, 2, 3, 4 and the like exist at the same time, each version has unique version number identification, and each version number identification corresponds to multiple rules. For example, if we wish to use the gray version of the user in Shenzhen city or the user belonging to the VIP level first, two rules can be configured, the first rule locates the geographic position of the user according to the client IP, and the second rule determines whether the user identity is the VIP client according to the user login state, and any one of the two rules is met. Therefore, rule subdivision is helpful for understanding, the rule reuse of different subsequent gray level versions is facilitated, and most gray level configuration scenes can be met theoretically only by formulating a small number of common rules.
The system comprises a function of enabling a disabling strategy by one key for each gray level version and rule, and persistent storage is carried out for each operation, so that the rule is obtained as efficiently as possible, and finally enabled rules are synchronized into redis cache middleware when each storage is carried out.
3. Gray scale matching execution system
The system comprises a matching forwarding function of a client request, when the client initiates the request, the client is forwarded to a final ecs server after SLB load balancing, each ecs server is deployed with an openness, the request is forwarded to a gray scale module by utilizing the location capability provided by an nginx module, and after a gray scale version number is obtained, a background service IP of a version number corresponding to the version number can be requested according to the reverse proxy capability provided by the nginx.
The system includes a gray scale rule execution matching function that uses information carried by the request to resolve rule variables, including but not limited to userAgent, network, os, osVersion, IP, header, cookie, etc. After the rule list is obtained from the rule management system, the rule list is sequentially executed, and once a certain rule is successfully matched, the gray version number corresponding to the rule is obtained and transferred to the nginx module.
The system comprises a resource response function, wherein the nginx receives the gray version number returned by the gray module, then splices a project static resource path and a proxy_pass reverse proxy background gateway path, finally responds to the corresponding resource to the client, and when the gray module fails to execute or does not find the gray version, executes a spam strategy and returns to the normal resource.
The front-end gray level publishing method of the invention relates to the following flow.
Step one: automated packaging and publishing of gray code
As shown in fig. 3, the gray release needs to draw the version number of the gray release in advance, which is mainly because when a server runs the gray release and the normal release at the same time, in order to distinguish between them, the directories where they are deployed need to be marked down by the version number, and at the same time, since the gray and the normal versions can only be distinguished by URL when cdn is returned, the cdn link needs to be marked with the version number in advance when the code is packed.
Normal release is based on a gitflow model, a process from feature branching to develop, master branching is needed in the release process, but a gray version is separated from the model, the gray version adopts feature branching all the time, when the release system of the devops releases, only the branching and the version number are required to be designated, the system can automatically deploy codes to a production server according to a certain rule, and meanwhile, each release can be used as a resource backup, and when the version has a problem, one-key rollback is convenient.
Step two: gray scale rule configuration
The gray rule configuration module is used as a gray control center, the operation is as simple and reusable as possible, and accidents caused by rule unavailability due to negligence of manually inputting the rule are reduced. As shown in fig. 4:
1. according to the proposed version number in the step one, a configuration record is created in the gray rule configuration system, and one or more rules can be created in the configuration record according to actual requirements.
2. The entry of the rules takes the form of a lua code, and preset variables that can be used in the lua code include cookie, userId, header, ip, userAgent, etc.
The preset variables refer to some variables which are declared in the memory in advance before the gray code is executed in the gray matching module, and the variables generally comprise all available information currently requested by the client.
3. When the gradation rule configuration is completed, the real-time validation is achieved by the enabling/disabling operation of the system configuration. In order to meet the performance problem that may exist in the acquisition of gray scale rules under high concurrence scenarios.
Here, the data is cached down through the distributed redis at each key operation such as enabling/disabling.
Step three: gray rule matching
The core of gray rule matching is that the information carried in the client request is matched with the gray rule, the corresponding version is responded according to the matched result, and the normal version is returned by default. The openness is used as a high performance platform based on the nginx and lua, and it is assumed that the application servers have installed openness, as shown in fig. 5:
1. when the nginx module receives the client request, whether the gray item is enabled or not is matched through location, if yes, the request is forwarded to the lua gray module, and meanwhile, the nginx can bring the request information of the URL, the header and the like of the client request into the past and store the request information in the global variable. Where the header generally refers to the header portion of the http protocol, some information of the client and browser may be marked by a userAgent in the header, and the cookie identifies the session state of the client.
2. After receiving the request, the lua gray scale module analyzes request information such as URL, and pulls gray scale rules from the gray scale configuration system after necessary information is prepared, because in the step two, the rule list is obtained directly through connection with redis, each rule is executed sequentially after the rule list is obtained, when the rule execution is successful, the rule is matched with the gray scale version, and the version number corresponding to the gray scale rule is obtained. When all rules fail to execute or information such as system abnormality occurs, no gray level version is considered. And splicing the obtained version numbers to obtain a static path and returning the static path to the nginx.
3. And after the nginx acquires the static resource path, searching the corresponding resource file and responding to the 200http state code.
4. In addition, if the request received by the nginx is a source-returning request of cdn, the gray version number of the cdn link set in the first step is regularly matched to the corresponding nginx location, the path of the static resource is spliced according to the matched version number, and the corresponding resource file is searched and responded to the 200http state code.
The front-end gray level release method has the beneficial effects that: according to the technical scheme, after the coding of the codes is completed, the gray scale version devots is packaged and distributed to release gray scale codes to the gray scale catalogue, wherein the gray scale catalogue name adopts the form of normal catalogue name plus gray scale version number; when a client request is received, the client request is forwarded to a lua gray level processing module through an openness nginx according to the request resource type; acquiring a gray rule from a preset gray rule list through the lua gray processing module, and executing the gray rule to obtain a gray resource path; the method includes the steps of notifying a nginx gray scale resource path, and continuously executing response, so that gray scale processing logic is extracted by using the existing machine resources on the premise of not changing URL path identification, and is uniformly configured and deployed, one-key gray scale switching of gray scales is realized, and gray scale rules are flexibly defined.
In order to achieve the above objective, the present invention further provides a front-end gray scale distribution system, where the system includes a memory, a processor, and a front-end gray scale distribution program stored on the processor, and the front-end gray scale distribution program executes the steps of the method described in the above embodiments when executed by the processor, which is not repeated herein.
In order to achieve the above object, the present invention further provides a computer readable storage medium, where a front-end gray scale distribution program is stored, and the front-end gray scale distribution program executes the steps of the method described above when being executed by a processor, which is not described herein again.
The foregoing description is only of the preferred embodiments of the present invention, and is not intended to limit the scope of the invention, but rather is intended to cover any equivalents of the structures or equivalent processes disclosed herein or in the alternative, which may be employed directly or indirectly in other related arts.
Claims (7)
1. A front-end gray scale distribution method, characterized in that the method comprises the following steps:
step S10, after the coding of the codes is completed, packaging the gray level version devots and deploying and releasing gray level codes to a gray level directory, wherein the gray level directory name adopts the form of normal directory name plus gray level version number;
step S20, when a client request is received, the client request is forwarded to a lua gray level processing module through an openness nginx according to the request resource type;
step S30, acquiring gray rules from a preset gray rule list through the lua gray processing module, and executing the gray rules to obtain a gray resource path;
step S40, notifying the nginx gray scale resource path, and continuing to execute response;
the step S10 includes:
pre-drawing a gray version number;
the step S10 includes:
after the coding of the codes is finished, a weback constructing system automatically adds a gray scale version number in front of a static resource path in a page, and then an independent packing mode is adopted, and the codes are automatically packed and deployed to a gray scale catalog by using a release system;
the step S20 includes:
when a client request is received, distinguishing the request resource type;
determining a processing mode according to the request resource type, uniformly forwarding a request of an html file to a lua gray level module for processing, and setting a spam policy at the same time, and responding to a normal version by adopting the spam policy when the gray level module is not available and errors are caused or gray level versions are not matched; when cdn back source processing is needed for the static resource part, determining a gray resource path according to whether gray version identifiers exist in the matched static resource url;
the step S30 includes:
after the lua gray processing module receives the forwarded client request, extracting information carried by the client request, pulling a preset gray rule list, executing according to the rule sequence, determining a gray resource path according to a gray version number corresponding to any rule once the rule is matched, and returning to the nginx for continuous execution.
2. The front-end gray scale distribution method according to claim 1, wherein the information carried by the client request at least comprises one or more of userAgent, IP, cookie, header and request body information of the user.
3. The front-end gray scale distribution method according to claim 1, wherein said step S40 comprises:
and finding out a target file according to the gray resource path and responding.
4. A front-end tone distribution method according to any one of claims 1 to 3, wherein before step S30, it includes:
and dynamically managing and setting gray rules and gray versions, and establishing a gray rule table of association relation between the gray rules and the gray versions.
5. The front-end gray scale distribution method according to claim 4, wherein in the step of dynamically managing and setting gray scale rules and gray scale versions and establishing a gray scale rule table of association relation between gray scale rules and gray scale versions, each gray scale rule supports inputting a custom lua script, and realizes priority of gray scale matching through rule ordering, one-key switching is performed for rules under each version number, and a rule list which is finally effective is synchronously written into a cache service while persistent storage is performed for each operation.
6. A front-end grey scale distribution system, characterized in that the system comprises a memory, a processor, and a front-end grey scale distribution program stored on the processor, which front-end grey scale distribution program, when executed by the processor, performs the steps of the method according to any of claims 1 to 5.
7. A computer readable storage medium, characterized in that the computer readable storage medium has stored thereon a front-end grey scale distribution program, which when executed by a processor performs the steps of the method according to any of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210149835.8A CN114615135B (en) | 2022-02-18 | 2022-02-18 | Front-end gray level publishing method, system and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210149835.8A CN114615135B (en) | 2022-02-18 | 2022-02-18 | Front-end gray level publishing method, system and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114615135A CN114615135A (en) | 2022-06-10 |
| CN114615135B true CN114615135B (en) | 2024-03-22 |
Family
ID=81859743
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210149835.8A Active CN114615135B (en) | 2022-02-18 | 2022-02-18 | Front-end gray level publishing method, system and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114615135B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114968274B (en) * | 2022-07-29 | 2022-11-08 | 之江实验室 | Method and system for automatically and rapidly deploying front-end processor based on gray release |
| CN115250233B (en) * | 2022-09-22 | 2022-12-16 | 中邮消费金融有限公司 | Gray scale routing control method, gray scale routing assembly and computer equipment |
| CN116755764B (en) * | 2023-08-22 | 2023-11-17 | 山东浪潮数字商业科技有限公司 | Automatic telescopic non-invasive gray level release system |
| CN117032991B (en) * | 2023-10-08 | 2024-01-26 | 宁波银行股份有限公司 | Gray scale publishing method, device and system |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108319468A (en) * | 2017-01-16 | 2018-07-24 | 北京京东尚科信息技术有限公司 | Gray scale dissemination method, device, system and electronic equipment |
| CN108874409A (en) * | 2017-05-09 | 2018-11-23 | 腾讯科技（深圳）有限公司 | A kind of information updating method, device, server and system |
| CN109376322A (en) * | 2018-09-07 | 2019-02-22 | 平安科技（深圳）有限公司 | A kind of grayscale version page access method, apparatus, computer equipment and computer storage medium |
| CN109787830A (en) * | 2019-01-21 | 2019-05-21 | 北京京东尚科信息技术有限公司 | Gray scale distribution control method, device, system, electronic equipment and storage medium |
| CN110704777A (en) * | 2019-09-20 | 2020-01-17 | 阿里巴巴集团控股有限公司 | Method and system for implementing gray scale publishing |
| CN110912734A (en) * | 2019-10-31 | 2020-03-24 | 北京浪潮数据技术有限公司 | Method and device for realizing multi-dimensional gray scale release of container application by cloud management platform |
| CN112363751A (en) * | 2020-11-10 | 2021-02-12 | 平安普惠企业管理有限公司 | Software product gray level release method, device, equipment and medium |
| CN112486550A (en) * | 2020-11-25 | 2021-03-12 | 上海中通吉网络技术有限公司 | Method, device and system for publishing gray scale of WEB terminal |
| CN113010405A (en) * | 2019-12-20 | 2021-06-22 | 北京沃东天骏信息技术有限公司 | Application program testing method and device |
| CN113422732A (en) * | 2021-06-22 | 2021-09-21 | 康键信息技术（深圳）有限公司 | Version updating method, device, equipment and storage medium based on total station gray scale |
| WO2022001209A1 (en) * | 2020-06-30 | 2022-01-06 | 深圳前海微众银行股份有限公司 | Job execution method, apparatus and system, and computer-readable storage medium |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104516738A (en) * | 2014-12-15 | 2015-04-15 | 北京金和软件股份有限公司 | Integrated implementing method for development and release of APP |
| US10785122B2 (en) * | 2018-10-05 | 2020-09-22 | Cisco Technology, Inc. | Canary release validation mechanisms for a containerized application or service mesh |
-
2022
- 2022-02-18 CN CN202210149835.8A patent/CN114615135B/en active Active
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108319468A (en) * | 2017-01-16 | 2018-07-24 | 北京京东尚科信息技术有限公司 | Gray scale dissemination method, device, system and electronic equipment |
| CN108874409A (en) * | 2017-05-09 | 2018-11-23 | 腾讯科技（深圳）有限公司 | A kind of information updating method, device, server and system |
| CN109376322A (en) * | 2018-09-07 | 2019-02-22 | 平安科技（深圳）有限公司 | A kind of grayscale version page access method, apparatus, computer equipment and computer storage medium |
| CN109787830A (en) * | 2019-01-21 | 2019-05-21 | 北京京东尚科信息技术有限公司 | Gray scale distribution control method, device, system, electronic equipment and storage medium |
| CN110704777A (en) * | 2019-09-20 | 2020-01-17 | 阿里巴巴集团控股有限公司 | Method and system for implementing gray scale publishing |
| CN110912734A (en) * | 2019-10-31 | 2020-03-24 | 北京浪潮数据技术有限公司 | Method and device for realizing multi-dimensional gray scale release of container application by cloud management platform |
| CN113010405A (en) * | 2019-12-20 | 2021-06-22 | 北京沃东天骏信息技术有限公司 | Application program testing method and device |
| WO2022001209A1 (en) * | 2020-06-30 | 2022-01-06 | 深圳前海微众银行股份有限公司 | Job execution method, apparatus and system, and computer-readable storage medium |
| CN112363751A (en) * | 2020-11-10 | 2021-02-12 | 平安普惠企业管理有限公司 | Software product gray level release method, device, equipment and medium |
| CN112486550A (en) * | 2020-11-25 | 2021-03-12 | 上海中通吉网络技术有限公司 | Method, device and system for publishing gray scale of WEB terminal |
| CN113422732A (en) * | 2021-06-22 | 2021-09-21 | 康键信息技术（深圳）有限公司 | Version updating method, device, equipment and storage medium based on total station gray scale |
Non-Patent Citations (3)
| Title |
|---|
| Design and Implementation of Gray Publishing System under Distributed Application Microservice;Hui Chen等;2021 11th International Conference on Power and Energy Systems (ICPES);20220126;全文 * |
| 基于携程旅行APP特卖汇项目的前端优化设计与实现;郭慧敏;万方;20190603;全文 * |
| 富亚军.《企业互联网架构原理与实践》.机械工业出版社,2021,第71页倒数第11行至第72页第8行以及图4-16. * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114615135A (en) | 2022-06-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN114615135B (en) | Front-end gray level publishing method, system and storage medium | |
| CN112118565B (en) | Multi-tenant service gray level publishing method, device, computer equipment and storage medium | |
| US8024740B2 (en) | Acquisition system for distributed computing resources | |
| CN111506367B (en) | Multi-cluster type artificial intelligence online service method and system | |
| CN111200523B (en) | Method, device, equipment and storage medium for configuring middle platform system | |
| CN106487863A (en) | A kind of based on the gray scale dissemination method of distributed system, client and platform | |
| CN108540505B (en) | Content updating method and device | |
| CN105897888A (en) | Client connection method and system | |
| US20200382382A1 (en) | Method and system for detecting service quality of cdn system | |
| CN107038050A (en) | A kind of game configuration loading method based on virtual server | |
| CN114422331A (en) | Disaster tolerance switching method, device and system | |
| CN113315754A (en) | Intelligent linkage method, device, equipment and medium for firewall of container visit | |
| CN111459492A (en) | Method, device, storage medium and equipment for detecting compatibility of Dubbo service interface | |
| CN114900449B (en) | Resource information management method, system and device | |
| CN113556407B (en) | Interface calling method and device for identification analysis node and electronic equipment | |
| CN114938396A (en) | Routing method of service call request, method and device for creating service | |
| CN113364892B (en) | Domain name resolution method, related method, device and system for cross-multi-cluster service | |
| CN108322459B (en) | EPaxos-based decentralized network domain name service method and system | |
| CN112231093A (en) | Data acquisition method and system based on code template and coroutine pool and electronic equipment | |
| CN111858083B (en) | Remote service calling method and device, electronic equipment and storage medium | |
| CN104734923B (en) | The execution control method and system of application task, message server | |
| CN110287265B (en) | Login request processing method and device, server and readable storage medium | |
| CN112732530B (en) | LVS operation and maintenance control system, method and device | |
| CN113872785B (en) | Model obtaining method and device and operation maintenance terminal | |
| CN114064797A (en) | Data synchronization method and system |
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 |