CN118034739A

CN118034739A - Gray scale publishing method, system, equipment and medium based on APP client

Info

Publication number: CN118034739A
Application number: CN202410218619.3A
Authority: CN
Inventors: 魏明丽; 铁锦程; 李虎; 俞秋琳; 孙秋漪; 李小兵
Original assignee: Shanghai Pudong Development Bank Co Ltd
Current assignee: Shanghai Pudong Development Bank Co Ltd
Priority date: 2024-02-28
Filing date: 2024-02-28
Publication date: 2024-05-14

Abstract

The invention relates to a gray level publishing method, a gray level publishing system, gray level publishing equipment and gray level publishing media based on an APP client, wherein the gray level publishing method comprises the following steps: when a user starts an APP client, a gray level updating flow is entered; judging whether the gray level version is larger than the current version of the APP client, if so, inquiring a gray level updating strategy corresponding to the current gray level version, otherwise, ending the gray level updating flow; judging the gray level updating strategy which is currently in effect, judging whether the current user can update according to the strategy which is in effect, if so, putting the updating information of the gray level version into the original updating information, returning to the client, otherwise, ending the gray level updating flow; in the gray level updating process, parameters in the gray level updating strategy are adjusted according to the updating condition so as to realize gradual discharging. Compared with the prior art, the method has the advantages of flexible release of the APP client, flexible support of configuration, switching, stable release and the like of the flexible and configurable API gateway routing strategy.

Description

Gray scale publishing method, system, equipment and medium based on APP client

Technical Field

The invention relates to the technical field of gray level release, in particular to a gray level release method, a gray level release system, gray level release equipment and a gray level release medium based on an APP client.

Background

The conventional release and test of the APP new version is limited in that enough models and test data of more users cannot be collected, and the release and production of the version is risky. At present, the APP server side adopts a bluish green release technology in the release stage, as shown in fig. 1, the external influence in the release process of the version is greatly reduced by a flow switching mode, and the release without perception of a user is realized. However, this technique still has the following drawbacks:

1. In the version updating process, the version updating information is pushed in full quantity, namely only batch external prompt updating is supported, and small-scale updating of configuration strategies is not supported, so that most of user updating time periods are overlapped, the risk of version release and the pressure of service resources are increased, and the influence range is enlarged if a new business function has a BUG.

2. For the multi-version client, the API gateway points to the same function when accessing the function service, and the redundancy judgment of the internal codes of the function increases the development and maintenance cost.

3. The production codes and version iteration codes of the server exist in the same functional interface, business logic redundancy processing is carried out, and the difficulty of function maintenance and upgrading is high.

4. The output redundancy of the new log and the old log is difficult to distinguish between the new version and the old version, and the problem of the new function cannot be found in time.

Therefore, there is a need for an APP client gray level publishing method capable of improving the stability of version update to improve the user experience.

Disclosure of Invention

The invention aims to overcome the defects of the prior art and provide a gray level release method, a system, equipment and a medium based on an APP client, which apply gray level release technology to release scenes of the APP client and realize stable user upgrade through gradual release.

The aim of the invention can be achieved by the following technical scheme:

According to a first aspect of the present invention, there is provided an APP client-based gray scale publishing method, comprising the steps of:

when a user starts an APP client, a gray level updating flow is entered;

Judging whether the gray level version is larger than the current version of the APP client, if so, inquiring a gray level updating strategy corresponding to the current gray level version, otherwise, ending the gray level updating flow;

Judging the gray level updating strategy which is currently in effect, judging whether the current user can update according to the strategy which is in effect, if so, putting the updating information of the gray level version into the original updating information, returning to the client, otherwise, ending the gray level updating flow; in the gray level updating process, parameters in the gray level updating strategy are adjusted according to the updating condition so as to realize gradual discharging.

The gray level updating strategy comprises a list updating strategy, a percentage updating strategy and a combination strategy, wherein the list updating strategy judges whether a user is in a list group or not based on the matching of preconfigured list group information and user tag information, and if the user is in the list group, the current user can update; the percentage updating strategy is used for judging whether the percentage updating rule is met or not by acquiring the preset percentage and calculating the percentage of the current user, and if the percentage updating rule is met, the current user can update; the combined strategy firstly executes the list updating strategy, then executes the percentage updating strategy, and if any strategy is successfully matched, the current user can update.

The service end gray release version access routing strategy in the gray update flow is as follows:

And realizing interface self-defined routing strategy based on API gateway expansion, converting and routing based on rules of service configuration, judging whether request uri, request header parameter information and a user meet corresponding conditions in the gray level updating strategy, splicing gray level version interface information on uri if the conditions are met, and forwarding the route to a new version.

In the gray level updating process, a rollback rule is defined in the API gateway, whether rollback conditions are met is judged according to the request header parameter information and the configured rollback rule, and if the rollback conditions are met, part of the new version of the scene is quickly rolled back to the old version.

The service end defines two interface addresses, the new version service interface is independent, dynamic routing is realized through the API gateway and the new and old versions of the client end, and the service processing logic extracts and encapsulates the public parts of the new and old versions during maintenance, and the new gray version routing address and the new gray version function characteristic are added.

In the gray level release process, log information of the new version address is monitored in real time, an access error report is formed, and alarm feedback is carried out on the abnormal log.

And the new version address is used for counting the behavior data of the user by combining with the embedded point system and the user operation record, analyzing the behavior and business quantity change indexes of the new and old versions, determining the new version operation effect and carrying out feedback optimization.

According to a second aspect of the present invention, there is provided an APP client-based gray scale distribution system, comprising:

the starting module is used for entering a gray level updating flow when a user starts the APP client;

The business logic judging module judges whether the gray level version is larger than the current version of the APP client, if so, the gray level updating strategy corresponding to the current gray level version is inquired and the gray level strategy executing module is called, otherwise, the gray level updating flow is ended;

The gray level strategy executing module judges the gray level updating strategy which is currently in effect, judges whether the current user can update according to the strategy which is in effect, if so, the gray level version updating information is put into the original updating information, the client is returned, and if not, the gray level updating flow is ended; in the gray level updating process, parameters in the gray level updating strategy are adjusted according to the updating condition so as to realize gradual discharging.

According to a third aspect of the present invention there is provided an electronic device comprising a memory and a processor, the memory having stored thereon a computer program, the processor implementing the method when executing the program.

According to a fourth aspect of the present invention there is provided a computer readable storage medium having stored thereon a computer program which when executed by a processor implements the method.

Compared with the prior art, the invention has the following beneficial effects:

(1) The client side supports the gray level release mode, can maintain release strategies through the management platform, supports the business to update parameters in the gray level update strategy by observing the update condition of the version, gradually releases the parameters, and supports the small batch update of the client side APP, thereby realizing the stable upgrade of users.

(2) The invention adopts the automatic route distinguishing strategy of the new version and the old version of the gateway side, supports the configuration and the switching of the flexible and configurable API gateway route strategy, and realizes the smooth and stable switching of the stable version and the gray version.

(3) The invention has the new function data collecting and analyzing capability in the gray level release mode, and the problems can be found more quickly by monitoring the log information of the new version address and the service resource service condition, so that the risk of the new function on-line is reduced, and the accurate new version effect feedback is provided for the service.

(4) The invention can acquire the access track and data of the new version user by combining the request address, analyze and compare the user behavior and the change of the traffic, thereby realizing the efficient monitoring of the new version in the gray release mode, and locating and finding the problem of the gray version in time.

(5) The upgrading and reforming of part of the client functions supports rollback, and if problems are found in the running process of the new version, the functions can be switched back to the old version by modifying routing rules, replacing application programs and the like.

Drawings

FIG. 1 is a schematic diagram of a blue-green publishing technology;

FIG. 2 is a flow chart of the method of the present invention;

fig. 3 is a schematic diagram of an automatic routing strategy of the present invention.

Detailed Description

The following description of the embodiments of the present invention will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all embodiments of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the present invention without making any inventive effort, shall fall within the scope of the present invention.

The existing gray level release method or canary release is adopted, the original version is not affected, a set of new version application is deployed, a service configuration strategy enables a designated user to access a new system, a part of users experience new products, usage data and service resource information are collected, the use range of the users is gradually enlarged, and smooth transition of version switching is achieved. The API gateway is used as an intermediate gateway for connecting the client and the server and is used for realizing the routing forwarding from the client request to the application service, and can perform the functions of request authentication, current limiting, service load balancing and the like.

As shown in fig. 2, the present embodiment provides a gray level publishing method based on an APP client, which includes the following steps:

s1, when a user starts an APP client, a gray scale updating flow is entered.

S2, judging whether the gray level version is larger than the current version of the APP client (namely judging whether the business logic rule is met), if so, inquiring a gray level updating strategy corresponding to the current gray level version, and if not, ending the gray level updating flow.

Taking the version number of the current user when starting the APP as an example, if the version number corresponding to the gray version is 8.0, judging that the gray version is larger than the current version of the APP client, and if the user meets the primary condition of gray updating, continuing to execute the next step, otherwise, indicating that the current version of the user is the latest version, and directly ending the gray updating flow.

S3, judging the gray level updating strategy which is currently in effect, judging whether the current user can update according to the gray level updating strategy which is in effect, if so, putting the updating information of the gray level version into the original updating information, returning to the client, otherwise, ending the gray level updating flow.

In one embodiment, the gray level updating strategy comprises a list updating strategy, a percentage updating strategy and a combination strategy, only one updating strategy is effective in each version issuing process according to rules configured by service personnel, and in the gray level updating process, the service personnel can adjust parameters in the gray level updating strategy according to actual updating conditions so as to gradually put the parameters into quantity and realize gradual version updating.

Specifically, S3 includes the following steps:

S31, if the currently effective gray level updating strategy is a list updating strategy, firstly judging the user and the label information thereof, if the labels are not matched, directly ending the updating process, otherwise, acquiring list group information according to configuration, judging whether the list group is successfully acquired, if the acquisition is failed, directly ending the updating process, otherwise, continuously judging whether the user is in the list group, if the user is in the list group, the user accords with the relevant conditions when the user opens the APP at the time, and updating the user, and executing step S34, otherwise, directly ending the updating process;

s32, if the currently effective gray level updating strategy is a percentage updating strategy, firstly acquiring the percentage of strategy configuration, solving the percentage of users by using a related algorithm, judging whether the percentage updating rule is met, if so, indicating that the users meet the related conditions when the APP is opened at the time, updating, and executing the step S34, otherwise, directly ending the updating flow;

S33, if the gray level updating strategy which is currently effective is a combined strategy, a list updating strategy is firstly executed, then a percentage updating strategy is executed, if any strategy is successfully matched, the user is indicated to accord with the relevant conditions when the APP is opened at the moment, the updating can be carried out, and step S34 is executed, otherwise, the updating flow is directly ended;

s34, the update information of the gray version is put into the original update information, and the client is returned to complete the update.

Taking a list updating policy as an example, an operator can configure a list group in advance through information such as a customer group/IP (Internet protocol), the number of users in the list group can be flexibly configured, and when the users in the list group complete updating and find that the gray version operates stably after a period of operation, the policy can be expanded into full updating, namely all the users opening the APP update. In addition, after the user in the list group in the first batch is updated, the configuration of the list group can be changed, a small-range updating service is provided for the second batch of users, and the like, so that the small-batch updating is realized, and the reduction of the experience of the large-range users caused by the bug of the new version is avoided.

Taking the percentage update strategy as an example, the operator may preset a percentage value, such as 10%. When one user opens the APP, a related algorithm (such as a random number algorithm) is adopted to give a percentage value, and if the given value is 5% and the total number of the current updated users does not reach 10% of all users, the user can update; if the value is 20%, even if the total number of the current updating users does not reach 10% of all users, the users do not accord with the percentage updating rule and cannot be updated; if the total number of the current updating users does not reach 10% of all users, the users entering the APP cannot update.

The APP client release is changed from original batch release to operator user-defined client version update rules, the version is accurately controlled to carry out gray release, and the risk of version update is reduced.

In a preferred embodiment, as shown in fig. 3, the access routing policy of the service-side gray release version in the gray update procedure is:

Based on API gateway sping cloud gateway expansion implementation GlobalFilter interface custom routing strategy GrayReactiveLoadBancerFliter, conversion and routing are carried out based on rules of service configuration, whether request uri, request header parameter information and a user meet corresponding conditions in a gray level updating strategy or not is judged, gray level version (v 2) interface information is spliced on uri if the conditions are met, and routing is forwarded to a new version (v 2), wherein v1 represents a current old version of the user, and v2 represents a new version which needs to be updated by the user.

For example, when the current client requests a xxx/v1/log in the background, the API gateway recognizes that GlobalFilter interfaces are maintained by service personnel, and needs to update to v2 address, it automatically forwards to the new address xxx/v2/log, and the process is not perceived by the client.

The original new version and the original old version are compatible with redundancy, the routing address is consistent, the service end carries out version control on the routing strategy, the scene division and the rule division routing are realized, and the influence of the history version can be reduced even if switching is carried out after the problem is found.

In addition, the rollback rule is defined in the API gateway to support rollback of part of the scene, specifically, a filter is customized in the gateway layer, whether rollback conditions are met is judged according to the request header parameter information and the configured rollback rule, and if the rollback conditions are met, the part of the scene with the new version is quickly rolled back to the old version.

The user's interface address information is stored in the buffer, and the filtering process of the program can be understood by the rule configured in the filter, so that the interface address can be automatically processed. For example, the address of the current client request to the background is xxx/v 2/logic, but the service personnel find that a certain function in the new version has a bug, the service personnel perform configuration through the management platform, and after the filter senses that the service personnel modify the configuration, the xxx/v 2/logic interface is automatically switched to the old interface xxx/v 1/logic, so that rollback of the scene is realized.

In order to not increase service deployment resources, the service end code is newly increased requetMapping on the basis of the original service end, two interface addresses are defined at the service end, a new version of service interface is independent, dynamic routing is realized through an API gateway and a new version and an old version of a client, public parts of the new version and the old version are extracted and packaged by service processing logic during maintenance, and a v2 gray version routing address and a gray version function new characteristic are newly increased.

In addition, the invention can also realize the automatic collection and analysis of the new version running condition in the gray level release mode. Because the addresses of the new version and the old version are decoupled, the abnormal log can be fed back by monitoring the log information of the addresses of the new version in real time and forming an access and error report. Meanwhile, by combining the new version address with the behavior data of the user counted by the embedded point system and the user operation record, the new and old version user behavior and service quantity change indexes are analyzed, the new version operation effect can be determined, feedback optimization can be performed, and better planning of service functions by service personnel is facilitated.

The original mode has the defect in the aspect of accurate new version use experience collection, and the APP client gray level release of the invention supports the automatic collection and analysis of new version user data use experience data so as to assist the business in carrying out new version operation analysis.

The foregoing description of the embodiments of the method further describes the embodiments of the present invention through system embodiments.

An APP client-based gray scale publishing system comprising:

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the described modules may refer to corresponding procedures in the foregoing method embodiments, and are not described herein again.

The electronic device of the present invention includes a Central Processing Unit (CPU) that can perform various appropriate actions and processes according to computer program instructions stored in a Read Only Memory (ROM) or computer program instructions loaded from a storage unit into a Random Access Memory (RAM). In the RAM, various programs and data required for the operation of the device can also be stored. The CPU, ROM and RAM are connected to each other by a bus. An input/output (I/O) interface is also connected to the bus.

A plurality of components in a device are connected to an I/O interface, comprising: an input unit such as a keyboard, a mouse, etc.; an output unit such as various types of displays, speakers, and the like; a storage unit such as a magnetic disk, an optical disk, or the like; and communication units such as network cards, modems, wireless communication transceivers, and the like. The communication unit allows the device to exchange information/data with other devices via a computer network, such as the internet, and/or various telecommunication networks.

The processing unit performs the respective methods and processes described above, for example, the methods S1 to S3. For example, in some embodiments, methods S1-S3 may be implemented as a computer software program tangibly embodied on a machine-readable medium, such as a storage unit. In some embodiments, part or all of the computer program may be loaded and/or installed onto the device via the ROM and/or the communication unit. When the computer program is loaded into RAM and executed by the CPU, one or more steps of the methods S1 to S3 described above may be performed. Alternatively, in other embodiments, the CPU may be configured to perform methods S1-S3 in any other suitable manner (e.g., by means of firmware).

The functions described above herein may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: a Field Programmable Gate Array (FPGA), an Application Specific Integrated Circuit (ASIC), an Application Specific Standard Product (ASSP), a system on a chip (SOC), a Complex Programmable Logic Device (CPLD), and the like.

Program code for carrying out methods of the present invention may be written in any combination of one or more programming languages. These program code may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus such that the program code, when executed by the processor or controller, causes the functions/operations specified in the flowchart and/or block diagram to be implemented. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of the present invention, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

While the invention has been described with reference to certain preferred embodiments, it will be understood by those skilled in the art that various changes and substitutions of equivalents may be made and equivalents will be apparent to those skilled in the art without departing from the scope of the invention. Therefore, the protection scope of the invention is subject to the protection scope of the claims.

Claims

1. The gray level publishing method based on the APP client is characterized by comprising the following steps:

when a user starts an APP client, a gray level updating flow is entered;

2. The gray level publishing method based on the APP client according to claim 1, wherein the gray level updating strategy comprises a list updating strategy, a percentage updating strategy and a combination strategy, wherein the list updating strategy judges whether a user is in a list group or not based on the matching of preconfigured list group information and user tag information, and if the user is in the list group, the current user can update; the percentage updating strategy is used for judging whether the percentage updating rule is met or not by acquiring the preset percentage and calculating the percentage of the current user, and if the percentage updating rule is met, the current user can update; the combined strategy firstly executes the list updating strategy, then executes the percentage updating strategy, and if any strategy is successfully matched, the current user can update.

3. The gray scale release method based on the APP client according to claim 1, wherein the service end gray scale release version access routing policy in the gray scale update flow is:

4. The gray scale release method based on the APP client according to claim 1, wherein in the gray scale update process, a rollback rule is defined in the API gateway, whether a rollback condition is satisfied is determined according to the request header parameter information and the configured rollback rule, and if the rollback condition is satisfied, the new version of the partial scene is quickly rolled back to the old version.

5. The gray scale release method based on the APP client according to claim 1, wherein the service end defines two interface addresses, the service interface of the new version is independent, dynamic routing is realized through the API gateway and the new and old versions of the client, and the service processing logic extracts and encapsulates the public parts of the new and old versions during maintenance, and adds the gray scale version routing address and the new characteristics of gray scale version functions.

6. The gray level publishing method based on the APP client according to claim 1, wherein in the gray level publishing process, log information of a new version address is monitored in real time, an access and error report is formed, and alarm feedback is carried out on an abnormal log.

7. The gray level release method based on the APP client according to claim 1, wherein the new version operation effect is determined and feedback optimization is performed by analyzing new and old version user behaviors and business volume change indexes through new version addresses and combining buried point systems and user operation records to count the behavior data of the user.

8. An APP client-based gray scale publishing system, comprising:

9. An electronic device comprising a memory and a processor, the memory having stored thereon a computer program, characterized in that the processor, when executing the program, implements the method of any of claims 1-7.

10. A computer readable storage medium, on which a computer program is stored, characterized in that the program, when being executed by a processor, implements the method according to any one of claims 1-7.