Method for changing version parameters of distributed application and method for deploying version parameters of distributed application

Abstract

The embodiment of the invention provides a version parameter changing method and deployment method of a distributed application, and relates to the field of financial science and technology or other related fields. The method comprises the steps that a to-be-changed version package pushed by a version package unit is received, the to-be-changed version package is stored in a first area, an inheritance version corresponding to the to-be-changed version package and corresponding inheritance parameters are determined, and the to-be-changed version package comprises corresponding full-amount version parameter information, the first area and version parameters used for storing the version package according to versions; determining a to-be-maintained version parameter corresponding to the to-be-changed version package according to the full version parameter information and the inheritance parameter of the to-be-changed version package; and after a maintenance success instruction is received, changing the to-be-maintained version parameter into a maintenance version parameter, and determining a to-be-released version parameter according to the inheritance parameter and the maintenance version parameter. According to the method, version isolation during parameter modification in the version change process is achieved, and parameter abnormity is prevented from taking effect.

Description

Technical Field

[0001] This application relates to the field of fintech or other related fields, and in particular to a method for changing version parameters and deployment of a distributed application. Background Technology

[0002] To meet the diverse needs of users and businesses, applications typically exist in multiple versions. Updating versions enhances application functionality, thereby improving competitiveness and user experience; conversely, when an updated version proves unstable, it's necessary to revert to a stable historical version. Through version updates and rollbacks, a balance is achieved between application stability and functionality.

[0003] Currently, when changing the application version, the dynamic version parameters that need to be changed are maintained and published in the configuration center.

[0004] However, in existing technologies, when versions overlap, unexpected effects can easily occur (e.g., when patches and official versions are deployed simultaneously, the patch may mistakenly apply parameter values ​​from the official version). When rolling back a version, each parameter needs to be confirmed and restored to its historical value, and managing parameters from multiple versions can easily lead to configuration conflicts. Summary of the Invention

[0005] This application provides a method for changing version parameters and a deployment method for distributed applications, in order to solve the technical problem of parameters taking effect unexpectedly when multiple versions are mixed and managed.

[0006] Firstly, this application provides a method for changing version parameters of a distributed application, including:

[0007] The system receives a version package to be changed pushed by the version package unit and stores the version package to be changed in a first area. It determines the inherited version and the corresponding inherited parameters of the version package to be changed. The version package to be changed includes: the corresponding full version parameter information. The inherited parameters are used to indicate the fixed static constants in the version change process. The first area is used to store the version parameters of the version package by version.

[0008] Based on the full version parameter information of the version package to be changed and the inheritance parameters, determine the version parameters to be maintained corresponding to the version package to be changed;

[0009] After receiving the maintenance success instruction, the parameter of the version to be maintained is changed to the parameter of the maintenance version. Based on the inherited parameter and the maintenance version parameter, the parameter of the version to be released is determined. The parameter of the version to be released is used to change the version parameter of the version package to be changed.

[0010] Secondly, this application provides a method for deploying version parameters of a distributed application, applied to a version management system, the version management system including version package units and a configuration center for version parameters of the distributed application, the method comprising:

[0011] Upon receiving a version change instruction, the version package to be changed corresponding to the version change instruction is determined from the version package unit according to the version change instruction, and the version package to be changed is pushed to the configuration center of the version parameters of the distributed application. The version package unit stores version packages corresponding to multiple versions of multiple applications, and the storage location of the version packages corresponding to multiple versions of each application is different.

[0012] The parameters of the version package to be changed are modified to determine the parameters of the version to be released. The parameters of the version to be released are determined by the configuration center of the version parameters of the distributed application based on the method for changing the version parameters of the distributed application provided by the first aspect and / or various possible implementations of the first aspect.

[0013] The release parameters are processed to deploy the release parameters to the application corresponding to the version to be changed.

[0014] Thirdly, this application provides a configuration center for version parameters of distributed applications, including:

[0015] The processing module is used to receive the version package to be changed pushed by the version package unit, store the version package to be changed in the first area, determine the inherited version and the corresponding inheritance parameters of the version package to be changed, the version package to be changed includes: the corresponding full version parameter information, the inheritance parameters are used to indicate the fixed static constants in the version change process, and the first area is used to store the version parameters of the version package by version.

[0016] The processing module is further configured to determine the version parameters to be maintained corresponding to the version package to be changed based on the full version parameter information of the version package to be changed and the inheritance parameters;

[0017] The determination module, upon receiving a maintenance success instruction, is used to change the parameters of the version to be maintained to the parameters of the maintained version, and to determine the parameters of the version to be released based on the inherited parameters and the maintained version parameters. The parameters of the version to be released are used to change the version parameters of the version package to be modified.

[0018] Fourthly, this application provides a version management system, including a push module, a version package unit, a release module, and a configuration center as provided in the third aspect and / or various possible implementations of the third aspect;

[0019] Upon receiving a version change instruction, the push module is used to determine the version package to be changed corresponding to the version change instruction from the version package unit according to the version change instruction, and push the version package to be changed to the configuration center of the version parameters of the distributed application. The version package unit stores version packages corresponding to multiple versions of multiple applications, and the storage location of the version packages corresponding to multiple versions of each application is different.

[0020] The configuration center is used to modify the parameters of the version package to be changed and determine the parameters of the version to be released. The parameters of the version to be released are determined by the configuration center of the version parameters of the distributed application based on the method for changing the version parameters of the distributed application as described in any one of claims 1 to 6.

[0021] The publishing module is used to process the parameters of the version to be published so that the parameters of the version to be published can be deployed to the application corresponding to the version to be changed.

[0022] Fifthly, embodiments of this application provide an electronic device, including: a memory and a processor;

[0023] The memory stores computer-executed instructions;

[0024] The processor executes computer execution instructions stored in the memory, causing the processor to perform the first aspect and / or various possible implementations of the first aspect as described above.

[0025] In a sixth aspect, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the first aspect and / or various possible implementations of the first aspect.

[0026] In a seventh aspect, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the first aspect and / or various possible implementations of the first aspect.

[0027] The method and deployment method for changing version parameters of distributed applications provided in this application achieve version isolation during parameter modification by receiving the version package to be changed pushed by the version package unit and storing the version package to be changed in a first area; determining the inherited version and corresponding inherited parameters of the version package to be changed, the version package to be changed includes: corresponding full version parameter information, ensuring the continuity and smoothness of version changes, reducing the number of parameters to be maintained, and lowering maintenance costs; determining the version parameters to be maintained corresponding to the version package to be changed based on the full version parameter information of the version package to be changed and the inherited parameters, avoiding abnormal parameter activation and configuration conflicts caused by mixed management of multiple version parameters through version isolation operation and maintenance, identifying the parameters to be maintained that need to be maintained, and promoting necessary improvements to the application to improve its competitiveness and user experience; after receiving a maintenance success instruction, changing the version parameters to be maintained to the maintenance version parameters, and determining the release version parameters for parameter changes of the version package to be changed based on the inherited parameters and the maintenance version parameters, thereby improving the level of automated operation and maintenance of version parameters. Attached Figure Description

[0028] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0029] Figure 1 A flowchart illustrating a method for changing version parameters of a distributed application in the prior art, provided as an embodiment of this application;

[0030] Figure 2 A flowchart illustrating a method for changing version parameters of a distributed application provided in this application embodiment. Figure 1 ;

[0031] Figure 3 A flowchart illustrating a method for changing version parameters of a distributed application provided in this application embodiment. Figure 2 ;

[0032] Figure 4 A flowchart illustrating a method for deploying version parameters of a distributed application, as provided in an embodiment of this application;

[0033] Figure 5 A schematic diagram of the structure of a configuration center for version parameters of a distributed application provided in an embodiment of this application;

[0034] Figure 6 This application provides a schematic diagram of the structure of a version management system according to an embodiment of the present application.

[0035] Figure 7 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.

[0036] The accompanying drawings have illustrated specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to specific embodiments. Detailed Implementation

[0037] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0038] It should be noted that the method for changing the version parameters of the distributed application and the method for determining the parameters of the version to be released provided in this application can be used in the fintech field, or in any field other than fintech. The application fields of the method for changing the version parameters of the distributed application and the method for determining the parameters of the version to be released in this application are not limited.

[0039] "Multiple" refers to two or more, and other quantifiers are similar. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following objects have an "or" relationship.

[0040] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a particular order or sequence. It should be understood that such data can be interchanged where appropriate so that embodiments of the invention described herein can be implemented, for example, in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, products, or apparatus.

[0041] It should be noted that, in the embodiments of this application, the terms "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design scheme described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0042] To meet the diverse needs of users and businesses, the application exists in multiple versions. Updating the application's features enhances its competitiveness and user experience; conversely, when an updated version becomes unstable, it needs to be rolled back to a stable historical version. Through version updates and rollbacks, a balance is achieved between application stability and functionality.

[0043] Figure 1 A flowchart illustrating a method for changing version parameters of a distributed application in the prior art, as provided in this application embodiment, is shown below. Figure 1 As shown, there exists an application that includes, for example... Figure 1 The diagram shows a production version (V1.0) and a patch version (V1.1). Initially, the version package includes parameters A and B, where parameter A=1 and parameter B=1. During parameter import in production version V1.0, parameter A is modified in the configuration center, becoming parameter A=2, and this modified parameter A is stored in the configuration center. Before production deployment, the configuration center receives the patch version V1.1 package pushed from the version package unit and modifies parameter B in the configuration center, becoming parameter B=2, and this modified parameter B is also stored in the configuration center. When the patch is deployed, parameters A=2 and B=2 stored in the configuration center are released. It's understandable that because the modified parameters in production version V1.0 were not released but stored in the configuration center, parameter A=2 from production version V1.0 was prematurely released when patch version V1.1 was released.

[0044] Based on the above scenarios, it is evident that existing technologies, when versions overlap, can easily lead to unexpected effects. Furthermore, version rollback requires confirming and restoring each parameter to its historical value, and managing parameters from multiple versions can easily cause configuration conflicts.

[0045] The method for changing version parameters of distributed applications and the method for determining the parameters of the version to be released provided in this application achieve version isolation operation and maintenance by determining the version parameters to be maintained corresponding to the version package to be changed, aiming to solve the above-mentioned technical problems in the existing technology.

[0046] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0047] Figure 2 A flowchart illustrating a method for changing version parameters of a distributed application provided in this application embodiment. Figure 1 ,like Figure 2 As shown, the method includes:

[0048] S201. Receive the version package to be changed pushed by the version package unit, and store the version package to be changed in the first area. Determine the inherited version and the corresponding inherited parameters of the version package to be changed. The version package to be changed includes: the corresponding full version parameter information.

[0049] Among them, the inheritance parameters are used to indicate the fixed static constants in the version change process. The inheritance parameters can be, for example, environment variables. It can be understood that the version parameters of the inherited version are used to determine the inheritance parameters.

[0050] The version package unit is used to store version packages corresponding to multiple versions of multiple applications. The storage location of the version packages corresponding to the multiple versions of each application is different. The version package to be changed refers to the version package corresponding to the version that needs to be changed. Each version package includes full version parameter information, which may include, for example, version number, environment variables, resource paths, etc.

[0051] The first area is used to store the version parameters of the package by version. As you can understand, the first area stores the version parameters of multiple packages by version. The first area achieves parameter isolation and avoids parameter conflicts.

[0052] Upon receiving the version package to be changed pushed by the version package unit, the version package to be changed is stored in the first area, the inherited version corresponding to the version package to be changed is determined, and the inherited parameters corresponding to the version to be updated are obtained based on the full version parameter information of the version package to be updated and the version parameters corresponding to the inherited version.

[0053] S202. Based on the full version parameter information of the version package to be changed and the inheritance parameters, determine the version parameters to be maintained corresponding to the version package to be changed;

[0054] The "version to be maintained" parameter is used to indicate the dynamic variables corresponding to version changes.

[0055] Based on the full version parameter information and inherited parameters of the version package to be changed, the parameters that are not inherited are taken as the version parameters to be maintained for the version package to be changed.

[0056] S203. After receiving the maintenance success instruction, change the parameter of the version to be maintained to the parameter of the maintained version, and determine the parameter of the version to be released based on the inherited parameter and the parameter of the maintained version.

[0057] The "to be released version" parameter is used to change the version parameters of the package to be changed.

[0058] Upon receiving the maintenance success instruction, the status of the parameters of the version to be maintained is changed, and the maintenance version parameters are determined based on the status-changed parameters of the version to be maintained. The combined set of inherited parameters and maintenance version parameters is then used as the parameters of the version to be released.

[0059] Understandably, when staff perform maintenance on the parameters of the version to be maintained, they modify the parameters as needed. For example: if the parameter to be maintained includes A=1, after maintaining A=1, the staff changes A=1 to A=2 and issues a maintenance success command. Upon receiving the maintenance success command, the status of the parameter to be maintained is changed to indicate that the maintenance is complete.

[0060] This application provides a method for changing version parameters of a distributed application. It receives a version package to be changed pushed by a version package unit and stores it in a first area, achieving version isolation during parameter modification. The method determines the inherited version and parameters corresponding to the version package to be changed. The version package includes full version parameter information, ensuring the continuity and smoothness of version changes, reducing the number of parameters to be maintained, and lowering maintenance costs. Based on the full version parameter information and inherited parameters of the version package to be changed, the method determines the version parameters to be maintained. Through version isolation maintenance, it avoids abnormal parameter activation and configuration conflicts caused by mixed management of multiple version parameters, identifies the parameters to be maintained, and promotes necessary improvements to the application to enhance its competitiveness and user experience. After receiving a maintenance success instruction, the version parameters to be maintained are changed to maintenance version parameters. Based on the inherited parameters and the maintenance version parameters, the method determines the release version parameters for parameter changes to the version package to be changed, improving the level of automated version parameter maintenance.

[0061] Figure 3 A flowchart illustrating a method for changing version parameters of a distributed application provided in this application embodiment. Figure 2 In this embodiment, the version package to be changed also includes corresponding metadata information, which includes version information and application information. Figure 2Based on the examples, a method for changing version parameters of a distributed application is described in detail, such as... Figure 3 As shown, the method includes:

[0062] S301. Receive the version package to be changed pushed by the version package unit, and store the version package to be changed in the first area. Based on the version information in the version package to be changed, determine whether the version corresponding to the version package to be changed is a historical version. If yes, proceed to step S302. If no, proceed to steps S303 to S305.

[0063] Upon receiving the version package to be changed pushed by the version package unit, the version package to be changed is stored in the first area. Based on the version information in the version package to be changed, it is determined whether the version corresponding to the version package to be changed is a historical version. If the version corresponding to the version package to be changed is a historical version, the version package to be changed is determined to be a version package to be rolled back, and the historical version corresponding to the version package to be rolled back is determined to be the inherited version. The version parameters corresponding to the inherited version are determined in the first area, and the inheritance parameters are determined based on the version parameters corresponding to the historical version.

[0064] If the version of the package to be changed is not a historical version, then the package to be changed is determined to be an update package. Understandably, the update package cannot inherit parameters from historical versions. To ensure the stability of version updates, the parameters are determined to be inherited from the current version of the application corresponding to the update package.

[0065] When the version of the package to be changed is not a historical version, the package to be changed is determined to be an update package. Based on the application information of the update package, the application corresponding to the update package is identified, and the current version of the application is determined to be the inherited version of the update package. The second area is used to store the release version parameters. Therefore, the release version parameters corresponding to the current version are obtained from the second area and inherited to obtain the inherited parameters.

[0066] S302. Determine that the version package to be changed is a version package to be rolled back, and determine that the historical version corresponding to the version package to be rolled back is an inherited version. Based on the inherited version, determine the version parameters corresponding to the inherited version in the first region, and determine the inheritance parameters based on the version parameters corresponding to the historical version.

[0067] S303. Determine the application corresponding to the version package to be updated based on the application information of the version package to be updated;

[0068] S304. Use the current version of the application as the inherited version of the version package to be changed;

[0069] S305. Based on the full version parameter information, determine the inheritance parameters corresponding to the version to be changed from the release version parameters corresponding to the current version stored in the second area.

[0070] The second area is used to store parameters for the version to be released.

[0071] S306. Based on the full version parameter information and inherited parameters of the version package corresponding to the inherited version, determine the non-inherited parameters and use the non-inherited parameters as the version parameters to be maintained corresponding to the version to be changed.

[0072] Based on the full version parameter information and inherited parameters of the version package to be changed, the parameters that are not inherited are taken as the version parameters to be maintained for the version package to be changed.

[0073] S307. Determine whether a maintenance success command has been received; if yes, proceed to step S308; if no, proceed to step S309.

[0074] Determine whether a maintenance success command has been received. If a maintenance success command has been received, it means that the parameter to be maintained has been successfully maintained. Therefore, change the status of the parameter to be maintained to the maintenance success status, determine the maintenance version parameter, and take the set of inherited parameters and maintenance version parameters as the release version parameter. If no maintenance success command has been received, it means that the parameter to be maintained has not been successfully maintained. Unmaintained parameters cannot be released. Therefore, maintain the status of the parameter to be maintained as the maintenance pending status.

[0075] S308. Change the status of the version parameter to be maintained to the maintenance successful status, determine the maintenance version parameter, and determine the release version parameter based on the inherited parameter and the maintenance version parameter;

[0076] S309. Maintain the status of the parameters of the version to be maintained as the state to be maintained.

[0077] In one possible implementation, the method further includes:

[0078] Upon receiving an emergency instruction, the system receives a direct modification operation; it determines whether there is a difference between the parameter to be directly modified in the release version and the corresponding parameter with the same name in the first area; if there is a difference in the parameter with the same name, a notification message is generated.

[0079] The direct modification operation is used to modify the parameters of the version to be released in the second area, and the notification information is used to synchronize the version parameter values.

[0080] By directly modifying the parameters, the adaptability and flexibility of version changes are improved; the notification message reminds staff to synchronize parameter values, which avoids the problem that modified parameters will no longer take effect when new version parameters are released, thus preventing production issues and ensuring the consistency of version parameters.

[0081] This application provides a method for changing version parameters of a distributed application. It receives a version package to be changed pushed by a version package unit and stores the package in a first area. Based on the version information in the package, it determines whether the version corresponding to the package is a historical version. Depending on the type of the package, it determines whether to roll back or update the version parameters. Through version updates and rollbacks, a balance between application stability and functionality is achieved. If the version to be changed is a historical version, it is determined to be a rollback package, and the historical version corresponding to the rollback package is identified as the inherited version. Based on the full version parameter information and the version parameters corresponding to the historical version, the inherited parameters are determined, achieving automated and rapid rollback of version parameters. If the version to be changed is not a historical version, based on the application information of the package, the application corresponding to the package is determined, and the current version of the application is used as the inherited version of the package. Based on the full version parameters... The system uses data information stored in the second area to determine the inherited parameters of the version to be changed, ensuring the continuity and smoothness of version changes, reducing the number of parameters to be maintained, and lowering maintenance costs. Based on the full version parameter information of the inherited version's package and the inherited parameters, it identifies non-inherited parameters and uses them as the maintenance parameters for the version to be changed. This version isolation operation avoids abnormal parameter activation and configuration conflicts caused by mixed management of multiple version parameters, identifying the parameters that need maintenance and driving necessary application improvements to enhance application competitiveness and user experience. If a maintenance success command is received, the status of the maintenance parameters is changed, the maintenance version parameters are determined, and the release version parameters are determined based on the inherited and maintenance parameters. If no maintenance success command is received, this ensures the stability and data integrity of distributed application version parameter changes and improves the level of automated version parameter operation and maintenance.

[0082] Figure 4 This application provides a flowchart illustrating a method for deploying version parameters of a distributed application. The method is applied to a version management system, which includes version package units and a configuration center for version parameters of the distributed application. Figure 4 As shown, the method includes:

[0083] S401. Upon receiving a version change instruction, determine the version package to be changed corresponding to the version change instruction from the version package unit, and push the version package to be changed to the configuration center of the version parameters of the distributed application.

[0084] The version package unit stores version packages corresponding to multiple versions of multiple applications, and the storage location of the version packages corresponding to multiple versions of each application is different.

[0085] Upon receiving a version change instruction, the system determines the version package to be changed corresponding to the instruction, identifies the version package to be changed from the version package unit, and pushes the version package to be changed to the configuration center of the distributed application's version parameters.

[0086] In one possible implementation, the method of determining the version package to be modified corresponding to the version change instruction from the version package unit based on the version change instruction is described in detail, including:

[0087] Determine the version of the application to be changed corresponding to the version change instruction; determine the target storage location of the version to be changed in the version package unit; and use the version package stored in the target storage location as the version package to be changed.

[0088] Version package units enable parameter isolation of version packages.

[0089] S402. Modify the parameters of the version package to be changed and determine the parameters of the version to be released;

[0090] Among them, the version parameters to be released are determined by the configuration center of the version parameters of the distributed application based on the method provided in the above embodiment of the method for changing the version parameters of the distributed application;

[0091] S403. Process the release parameters of the version to be released so that the release parameters are deployed to the application corresponding to the version to be changed.

[0092] In one possible implementation, the method further includes: upon receiving a version change instruction, if the version change instruction is a version rollback instruction, determining the historical version corresponding to the version rollback instruction, determining the version package corresponding to the historical version in the first region, and using the version package corresponding to the historical version as the version package to be rolled back, and maintaining the parameters of the version package to be rolled back.

[0093] The ability to revert to previous versions is ensured by using version parameters from historical version packages stored in the first area.

[0094] This application provides a method for deploying version parameters of a distributed application. The method for changing version parameters of a package to be changed, determined by the above-mentioned method for changing version parameters of a distributed application, is used to deploy the version parameters of the package to be changed on the application. The implementation principle and technical effect are similar, and will not be described in detail here.

[0095] Figure 5 This application provides a schematic diagram of the structure of a configuration center for version parameters of a distributed application, as shown in the embodiments of this application. Figure 5 As shown, the configuration center 50 for version parameters of the distributed application provided in this embodiment includes:

[0096] Processing module 501 is used to receive the version package to be changed pushed by the version package unit, store the version package to be changed in the first area, determine the inherited version and the corresponding inherited parameters of the version package to be changed, the version package to be changed includes: the corresponding full version parameter information, the inherited parameters are used to indicate the fixed static constants in the version change process, and the first area is used to store the version parameters of the version package by version.

[0097] The processing module 501 is also used to determine the version parameters to be maintained corresponding to the version package to be changed based on the full version parameter information and inherited parameters of the version package to be changed.

[0098] After receiving the maintenance success instruction, module 502 is used to change the parameters of the version to be maintained to the parameters of the maintained version, and to determine the parameters of the version to be released based on the inherited parameters and the maintained version parameters. The parameters of the version to be released are used to change the version parameters of the version package to be changed.

[0099] In one possible implementation, the version package to be changed also includes corresponding metadata information, including version information. The processing module 501 is also used to determine whether the version corresponding to the version package to be changed is a historical version based on the version information in the version package to be changed.

[0100] If so, then determine that the version package to be changed is the version package to be rolled back, and determine that the historical version corresponding to the version package to be rolled back is the inherited version. Based on the inherited version, determine the version parameters corresponding to the inherited version in the first area, and determine the inherited parameters based on the version parameters corresponding to the historical version.

[0101] If not, then determine that the version package to be changed is the version package to be updated, and determine the inherited version and corresponding inheritance parameters of the version package to be updated.

[0102] In one possible implementation, the metadata information also includes: application information; the processing module 501 is further used to determine the application corresponding to the version package to be updated based on the application information of the version package to be updated.

[0103] Use the current version of the application as the inherited version of the package to be changed;

[0104] Based on the full version parameter information, the inherited parameters corresponding to the version to be changed are determined from the parameters of the version to be released corresponding to the current version stored in the second area. The second area is used to store the parameters of the version to be released.

[0105] In one possible implementation, the processing module 501 is further configured to determine the non-inherited parameters based on the full version parameter information of the version package corresponding to the inherited version and the inherited parameters; and to use the non-inherited parameters as the version parameters to be maintained corresponding to the version to be changed.

[0106] In one possible implementation, the determining module 502 is also used to determine whether a maintenance success instruction has been received; if so, the status of the version parameter to be maintained is changed to the maintenance success status, the maintenance version parameter is determined, and the release version parameter is determined based on the inherited parameter and the maintenance version parameter; if not, the status of the version parameter to be maintained is maintained as the maintenance status.

[0107] In one possible implementation, the processing module 501 is further configured to receive a direct modification operation when an emergency instruction is received, the direct modification operation being used to modify the parameters of the version to be released in the second area;

[0108] Determine if there are any differences between the parameters of the to-be-released version that are directly modified and the corresponding parameters with the same name in the first area;

[0109] If parameters with the same name differ, a notification message is generated.

[0110] The configuration center for version parameters of distributed applications provided in this embodiment can execute the method for changing version parameters of distributed applications provided in the above method embodiment. Its implementation principle and technical effect are similar, and will not be described in detail here.

[0111] Figure 6 This application provides a schematic diagram of the structure of a version management system, as shown in the embodiment of the present application. Figure 6 As shown, the version management system 60 provided in this embodiment includes: a push module 601, a version package unit 602, a publishing module 603, and as shown in the figure. Figure 5 Configuration center 50 is shown;

[0112] Upon receiving a version change instruction, the push module 601 is used to determine the version package to be changed corresponding to the version change instruction from the version package unit 602 according to the version change instruction, and push the version package to be changed to the configuration center of the version parameters of the distributed application. The version package unit stores version packages corresponding to multiple versions of multiple applications, and the storage location of the version packages corresponding to multiple versions of each application is different.

[0113] Configuration center 50 is used to modify the parameters of the version package to be changed and to determine the parameters of the version to be released. The parameters of the version to be released are determined by the configuration center of the version parameters of the distributed application based on the method for changing the version parameters of the distributed application provided in the above method embodiment.

[0114] The release module 602 is used to process the release parameters of the version to be released so that the release parameters can be deployed to the application corresponding to the version to be changed.

[0115] In one possible implementation, the push module 601 is further configured to determine the version of the application to be changed corresponding to the version change instruction; determine the target storage location of the version to be changed in the version package unit; and use the version package stored in the target storage location as the version package to be changed.

[0116] The configuration center for version parameters of distributed applications provided in this embodiment can execute the deployment method for version parameters of distributed applications provided in the above method embodiment. Its implementation principle and technical effects are similar, and will not be elaborated upon here.

[0117] Figure 7 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 7 As shown, the electronic device 70 provided in this embodiment includes at least one processor 701 and a memory 702. Optionally, the device 70 further includes a communication component 703. The processor 701, memory 702, and communication component 703 are connected via a bus 704.

[0118] In a specific implementation, at least one processor 701 executes computer execution instructions stored in memory 702, causing at least one processor 701 to perform the above-described method.

[0119] The specific implementation process of processor 701 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.

[0120] In the above embodiments, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.

[0121] The memory may include random access memory (RAM) and may also include non-volatile memory (NVM), such as at least one disk storage device.

[0122] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

[0123] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described method.

[0124] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the above-described method.

[0125] When integrated units / modules are implemented in hardware, the hardware can be digital circuits, analog circuits, etc. The physical implementation of the hardware structure includes, but is not limited to, transistors, memristors, etc. Unless otherwise specified, the processor can be any suitable hardware processor, such as a CPU, GPU, FPGA, DSP, and ASIC, etc. Unless otherwise specified, the storage unit can be any suitable magnetic or magneto-optical storage medium, such as Resistive Random Access Memory (RRAM), Dynamic Random Access Memory (DRAM), Static Random Access Memory (SRAM), Enhanced Dynamic Random Access Memory (EDRAM), High-Bandwidth Memory (HBM), Hybrid Memory Cube (HMC), etc.

[0126] If the integrated unit / module is implemented as a software program module and sold or used as an independent product, it can be stored in a computer-readable storage device. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a memory and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application.

[0127] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily essential to this application.

[0128] It should be further noted that although the steps in the flowchart are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowchart may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the sub-steps or stages of other steps.

[0129] It should be understood that the above-described device embodiments are merely illustrative, and the device of this application can also be implemented in other ways. For example, the division of units / modules in the above embodiments is only a logical functional division, and there may be other division methods in actual implementation. For example, multiple units, modules, or components may be combined, or integrated into another system, or some features may be ignored or not executed.

[0130] Furthermore, unless otherwise specified, the functional units / modules in the various embodiments of this application can be integrated into one unit / module, or each unit / module can exist physically separately, or two or more units / modules can be integrated together. The integrated units / modules described above can be implemented in hardware or as software program modules.

[0131] In the above embodiments, the descriptions of each embodiment have their own emphasis. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments. The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as the combination of these technical features does not contradict each other, it should be considered within the scope of this specification.

[0132] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.

[0133] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A method for changing version parameters of a distributed application, characterized in that, include: The system receives a version package to be changed pushed by the version package unit and stores the version package to be changed in a first area. It determines the inherited version and the corresponding inherited parameters of the version package to be changed. The version package to be changed includes: the corresponding full version parameter information. The inherited parameters are used to indicate the fixed static constants in the version change process. The first area is used to store the version parameters of the version package by version. Based on the full version parameter information of the version package to be changed and the inheritance parameters, determine the version parameters to be maintained corresponding to the version package to be changed; After receiving the maintenance success instruction, the parameter of the version to be maintained is changed to the parameter of the maintenance version. Based on the inherited parameter and the parameter of the maintenance version, the parameter of the version to be released is determined. The parameter of the version to be released is used to change the version parameter of the version package to be changed.

2. The method according to claim 1, characterized in that, The version package to be changed also includes corresponding metadata information, which includes version information; determining the inherited version and corresponding inheritance parameters of the version package to be changed includes: Based on the version information in the version package to be changed, determine whether the version corresponding to the version package to be changed is a historical version; If so, the version package to be changed is determined to be a version package to be rolled back, and the historical version corresponding to the version package to be rolled back is determined to be the inherited version. Based on the inherited version, the version parameters corresponding to the inherited version are determined in the first region, and the inheritance parameters are determined based on the version parameters corresponding to the historical version. If not, then the version package to be changed is determined to be the version package to be updated, and the inherited version and the corresponding inheritance parameters of the version package to be updated are determined.

3. The method according to claim 2, characterized in that, The metadata information also includes: application information, and determining the inherited version and corresponding inheritance parameters corresponding to the version package to be updated includes: Based on the application information of the version package to be updated, determine the application corresponding to the version package to be updated; The current version of the application is used as the inherited version of the version package to be changed. Based on the full version parameter information, the inheritance parameters corresponding to the version to be changed are determined from the release version parameters corresponding to the current version stored in the second area. The second area is used to store the release version parameters.

4. The method according to claim 1, characterized in that, The step of determining the version parameters to be maintained corresponding to the version package to be changed based on the full version parameter information of the version package to be changed and the inheritance parameters includes: Based on the full version parameter information and inherited parameters of the version package corresponding to the inherited version, determine the non-inherited parameters; The non-inherited parameters are used as the maintenance parameters for the version to be changed.

5. The method according to claim 1, characterized in that, Upon receiving the maintenance success instruction, the parameter of the version to be maintained is changed to the parameter of the maintained version, and the parameter of the version to be released is determined based on the inherited parameter and the maintained version parameter, including: Determine whether a maintenance success command has been received; If so, the status of the version parameter to be maintained is changed to the maintenance successful status, the maintenance version parameter is determined, and the release version parameter is determined based on the inherited parameter and the maintenance version parameter; If not, then the status of the version parameter to be maintained remains as pending maintenance.

6. The method according to claim 3, characterized in that, The method further includes: Upon receiving an emergency instruction, a direct modification operation is received, which is used to modify the parameters of the version to be released in the second region; Determine whether there is a difference between the parameters of the to-be-released version that are directly modified and the corresponding parameters with the same name in the first area; If there are differences in the parameters with the same name, a notification message is generated.

7. A method for deploying version parameters of a distributed application, characterized in that, Applied to a version control system, the version control system including version package units and a configuration center for version parameters of distributed applications, the method includes: Upon receiving a version change instruction, the version package to be changed corresponding to the version change instruction is determined from the version package unit according to the version change instruction, and the version package to be changed is pushed to the configuration center of the version parameters of the distributed application. The version package unit stores version packages corresponding to multiple versions of multiple applications, and the storage location of the version packages corresponding to multiple versions of each application is different. The parameters of the version package to be changed are modified to determine the parameters of the version to be released. The parameters of the version to be released are determined by the configuration center of the version parameters of the distributed application based on the method for changing the version parameters of the distributed application as described in any one of claims 1 to 6. The release parameters are processed to deploy the release parameters to the application corresponding to the version to be changed.

8. The method according to claim 7, characterized in that, The step of determining the version package to be changed corresponding to the version change instruction from the version package unit according to the version change instruction includes: Determine the version of the application to be changed corresponding to the version change instruction; Determine the target storage location of the version to be changed within the version package unit; The version package stored in the target storage location is used as the version package to be changed.

9. A configuration center for version parameters of a distributed application, characterized in that, include: The processing module is used to receive the version package to be changed pushed by the version package unit, store the version package to be changed in the first area, determine the inherited version and the corresponding inheritance parameters of the version package to be changed, the version package to be changed includes: the corresponding full version parameter information, the inheritance parameters are used to indicate the fixed static constants in the version change process, and the first area is used to store the version parameters of the version package by version. The processing module is further configured to determine the version parameters to be maintained corresponding to the version package to be changed based on the full version parameter information of the version package to be changed and the inheritance parameters; The determination module, upon receiving a maintenance success instruction, is used to change the parameters of the version to be maintained to the parameters of the maintained version, and to determine the parameters of the version to be released based on the inherited parameters and the maintained version parameters. The parameters of the version to be released are used to change the version parameters of the version package to be modified.

10. A version control system, characterized in that, It includes a push module, a version package unit, a release module, and a configuration center as described in claim 9; Upon receiving a version change instruction, the push module is used to determine the version package to be changed corresponding to the version change instruction from the version package unit according to the version change instruction, and push the version package to be changed to the configuration center of the version parameters of the distributed application. The version package unit stores version packages corresponding to multiple versions of multiple applications, and the storage location of the version packages corresponding to multiple versions of each application is different. The configuration center is used to modify the parameters of the version package to be changed and determine the parameters of the version to be released. The parameters of the version to be released are determined by the configuration center of the version parameters of the distributed application based on the method for changing the version parameters of the distributed application as described in any one of claims 1 to 6. The publishing module is used to process the parameters of the version to be published so that the parameters of the version to be published can be deployed to the application corresponding to the version to be changed.

11. An electronic device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the method as described in any one of claims 1 to 6.

12. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1 to 6.

13. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method of any one of claims 1 to 6.

Images