Business system upgrading method and device, computer device, storage medium and program product

Abstract

The application relates to a business system upgrading method and device, computer equipment, a storage medium and a program product. The method comprises the following steps: first, by dividing micro-service groups, only one group of micro-services is set to an offline state to perform an upgrading operation at any moment, and the remaining micro-service groups always remain in an online state and normally process business traffic, so that user-perceived upgrading is realized. Secondly, in the embodiment, the existing micro-service instance resources are directly utilized to complete upgrading, without the need of additionally deploying servers or containers, so that the hardware and operation and maintenance costs are greatly saved, and resource consumption is significantly reduced. In addition, in the embodiment, the upgrading operation is performed in groups, so that upgrading is avoided for each micro-service instance, and meanwhile, complex traffic routing rules do not need to be configured, so that the operation process is simplified, the system-perceived upgrading is realized, resource consumption is reduced, and upgrading efficiency is improved.

Description

Technical Field

[0001] This application relates to the field of microservice architecture technology, and in particular to a business system upgrade method, apparatus, computer equipment, storage medium, and program product. Background Technology

[0002] Microservices are characterized by independent deployment and autonomous operation, which can improve the scalability and maintenance efficiency of business systems. With the widespread application of microservice architecture in large-scale business systems, the number of microservice instances has surged, version iterations have become more frequent, and microservices do not exist in isolation. There are complex calls and dependencies between microservices, which significantly increases the complexity of business system upgrades. Therefore, upgrade methods such as blue-green deployment and canary deployment have emerged.

[0003] However, the upgrade methods for microservice business systems in related technologies struggle to achieve seamless upgrades while simultaneously considering resource costs and upgrade efficiency. Therefore, how to reduce resource consumption and improve upgrade efficiency while achieving seamless system upgrades has become a pressing technical problem to be solved in this field. Summary of the Invention

[0004] Therefore, it is necessary to provide a business system upgrade method, apparatus, computer equipment, storage medium, and program product that can reduce resource consumption and improve upgrade efficiency while achieving seamless system upgrades, in order to address the aforementioned technical problems.

[0005] Firstly, this application provides a method for upgrading a business system, including:

[0006] Divide each microservice in the business system to be upgraded into at least two microservice groups;

[0007] Set the target microservice group to an offline state and control the target microservice group to perform an upgrade operation; the target microservice group is any one of the at least two microservice groups.

[0008] After the target microservice group completes the upgrade operation, the target microservice group is set to online status, and the other microservice groups in the at least two microservice groups other than the target microservice group are set to offline status, and the other microservice groups are controlled to perform the upgrade operation.

[0009] In the aforementioned business system upgrade method, firstly, by dividing the system into microservice groups, only one group of microservices is set to an offline state to perform the upgrade operation at any given time, while the remaining microservice groups remain online and process business traffic normally, achieving a seamless upgrade for users. Secondly, this embodiment directly utilizes existing microservice instance resources to complete the upgrade, eliminating the need for additional server or container deployment, significantly saving hardware and maintenance costs and substantially reducing resource consumption. Furthermore, this embodiment performs the upgrade operation on a group basis, avoiding the need to upgrade each microservice instance individually, and eliminating the need to configure complex traffic routing rules, simplifying the operation process, achieving a seamless system upgrade while reducing resource consumption and improving upgrade efficiency.

[0010] In one embodiment, controlling the target microservice group to perform the upgrade operation includes:

[0011] For each target microservice in the target microservice group, control the business node corresponding to the target microservice to upgrade the target microservice using the upgrade package corresponding to the target microservice.

[0012] In this embodiment, the upgrade operation is performed on a single microservice basis for each target microservice, enabling parallel upgrades of each microservice within the microservice group. This shortens the upgrade time for the target microservice group and improves upgrade efficiency. Furthermore, upgrading is performed based on the upgrade package corresponding to each target microservice, improving the accuracy of the upgrade and enhancing its reliability and security.

[0013] In one embodiment, controlling the business node corresponding to the target microservice to upgrade the target microservice using the upgrade package corresponding to the target microservice includes:

[0014] Control the business node corresponding to the target microservice to perform any of the following update operations based on the upgrade package:

[0015] The database of the target microservice is upgraded based on the database change script in the upgrade package;

[0016] The runtime configuration of the target microservice is upgraded based on the configuration file template in the upgrade package;

[0017] The program files of the target microservice are upgraded based on the target version of the program files in the upgrade package.

[0018] In this embodiment, the upgrade process for the target microservice is refined into database upgrade, runtime configuration update, and program file upgrade. Based on the target version information in the upgrade package, automatic upgrades of the target microservice are achieved, simplifying the upgrade process and improving its efficiency. Simultaneously, the automatic upgrade process based on the upgrade package reduces the risk of human error, further enhancing the reliability and security of the target microservice upgrade.

[0019] In one embodiment, upgrading the runtime configuration of the target microservice based on the configuration file template in the upgrade package includes:

[0020] Based on the configuration file template, obtain the full configuration information of the target version from the environment configuration repository;

[0021] The changes are obtained by comparing the full configuration information with the current configuration information of the target microservice.

[0022] If the changes are confirmed to meet the preset change requirements, the running configuration of the target microservice is upgraded based on the full configuration information of the target version.

[0023] In this embodiment, the full configuration information of the target version is compared with the current, unupdated configuration information to determine the changes, thus avoiding accidental modification or deletion of critical configuration items due to direct overwriting. The update is only performed after confirming that the changes meet preset requirements, preventing system failures caused by incorrect configuration. Furthermore, full information is pulled from the environment repository based on the configuration file template, ensuring consistency between the configuration and the environment, reducing the risk of configuration errors, and further guaranteeing the reliability of configuration upgrades.

[0024] In one embodiment, the method further includes:

[0025] If any of the update operations fails during the execution of the upgrade operation, a rollback operation is performed based on the initial version information of the target microservice; the initial version information is obtained by backing up the initial version information of the target microservice before the upgrade operation is executed.

[0026] In this embodiment, a rollback mechanism is introduced during the upgrade process to improve the system's fault tolerance. When any update operation in the database, configuration, or program files encounters an anomaly, a rollback can be automatically performed based on the pre-backed-up initial version information, avoiding service anomalies caused by partial upgrade failures and improving the security and reliability of business system upgrades.

[0027] In one embodiment, setting the target microservice group to an online state after the upgrade operation is completed includes:

[0028] After the target microservice group completes the upgrade operation, the functionality of the target microservice group is verified based on preset test cases;

[0029] After successful verification, the target microservice group will be set to online status.

[0030] In this embodiment, functional verification is performed after the upgrade is completed to ensure that only microservice groups that pass the verification of preset test cases can be brought back online. This can quickly verify the availability and correctness of the upgraded services, reduce the cost of manual regression testing, and ensure the reliability of the upgrade process.

[0031] In one embodiment, the method further includes:

[0032] Based on the target version information, generate upgrade packages corresponding to each of the microservices to be upgraded;

[0033] Based on the topological relationship between each microservice to be upgraded and each business node in the business system to be upgraded, the upgrade package corresponding to the microservice to be upgraded is sent to the business node corresponding to the microservice to be upgraded.

[0034] In this embodiment, upgrade packages for each microservice are generated based on the target version information, ensuring version consistency and traceability. Furthermore, upgrade packages are sent in a targeted manner based on the topological relationship between microservices and business nodes, improving the efficiency and reliability of upgrade package distribution.

[0035] In one embodiment, sending the upgrade package corresponding to the microservice to be upgraded to the business node corresponding to the microservice to be upgraded includes:

[0036] Obtain the communication status of the business node corresponding to the microservice to be upgraded;

[0037] If the communication status of the business node corresponding to the microservice to be upgraded is normal, send the upgrade package corresponding to the microservice to be upgraded to the business node corresponding to the microservice to be upgraded.

[0038] In this embodiment, by checking the communication status of the service nodes before sending, it is ensured that the upgrade package is only distributed when the nodes are normal, avoiding invalid sending of upgrade packages to disconnected or faulty nodes, thus saving network bandwidth and storage resources.

[0039] In one embodiment, the method further includes:

[0040] If the communication status of the business node corresponding to the microservice to be upgraded is abnormal, the upgrade process of the microservice to be upgraded is interrupted, and an alarm message indicating that the communication status of the business node corresponding to the microservice to be upgraded is abnormal is generated.

[0041] In this embodiment, when a communication anomaly is detected at a business node, the upgrade process of that microservice is immediately interrupted and an alarm message is generated. This prevents some nodes from experiencing upgrade process anomalies due to unsuccessful distribution of the upgrade package or inability to issue commands. Furthermore, timely output of alarm messages can shorten the time for problem discovery and repair, further improving the reliability and maintainability of the upgrade process.

[0042] Secondly, this application also provides a business system upgrade apparatus, comprising:

[0043] The microservice grouping module is used to divide each microservice to be upgraded in the business system into at least two microservice groups.

[0044] The first upgrade module is used to set the target microservice group to an offline state and control the target microservice group to perform an upgrade operation; the target microservice group is any one of the at least two microservice groups.

[0045] The second upgrade module is used to set the target microservice group to an online state and set the other microservice groups (excluding the target microservice group) to an offline state after the target microservice group has completed the upgrade operation, and to control the other microservice groups to perform the upgrade operation.

[0046] Thirdly, this application also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps:

[0047] Divide each microservice in the business system to be upgraded into at least two microservice groups;

[0048] Set the target microservice group to an offline state and control the target microservice group to perform an upgrade operation; the target microservice group is any one of the at least two microservice groups.

[0049] After the target microservice group completes the upgrade operation, the target microservice group is set to online status, and the other microservice groups in the at least two microservice groups other than the target microservice group are set to offline status, and the other microservice groups are controlled to perform the upgrade operation.

[0050] Fourthly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, performs the following steps:

[0051] Divide each microservice in the business system to be upgraded into at least two microservice groups;

[0052] Set the target microservice group to an offline state and control the target microservice group to perform an upgrade operation; the target microservice group is any one of the at least two microservice groups.

[0053] After the target microservice group completes the upgrade operation, the target microservice group is set to online status, and the other microservice groups in the at least two microservice groups other than the target microservice group are set to offline status, and the other microservice groups are controlled to perform the upgrade operation.

[0054] Fifthly, this application also provides a computer program product, including a computer program that, when executed by a processor, performs the following steps:

[0055] Divide each microservice in the business system to be upgraded into at least two microservice groups;

[0056] Set the target microservice group to an offline state and control the target microservice group to perform an upgrade operation; the target microservice group is any one of the at least two microservice groups.

[0057] After the target microservice group completes the upgrade operation, the target microservice group is set to online status, and the other microservice groups in the at least two microservice groups other than the target microservice group are set to offline status, and the other microservice groups are controlled to perform the upgrade operation.

[0058] The aforementioned business system upgrade method, apparatus, computer equipment, storage medium, and program product divide each microservice to be upgraded in the business system into at least two microservice groups; set the target microservice group to an offline state and control the target microservice group to perform the upgrade operation; the target microservice group can be any one of the at least two microservice groups; after the target microservice group has completed the upgrade operation, set the target microservice group to an online state, and set the other microservice groups in the at least two microservice groups (excluding the target microservice group) to an offline state, and control the other microservice groups to perform the upgrade operation. In this embodiment, firstly, by dividing the microservice groups, only one group of microservices is set to an offline state to perform the upgrade operation at any given time, while the remaining microservice groups always remain online and process business traffic normally, achieving a seamless upgrade for users. Secondly, this embodiment directly utilizes existing microservice instance resources to complete the upgrade, without the need for additional server or container deployment, significantly saving hardware and maintenance costs and significantly reducing resource consumption. Furthermore, this embodiment performs upgrade operations on a group basis, avoiding the need to upgrade each microservice instance individually. It also eliminates the need to configure complex traffic routing rules, simplifying the operation process. This achieves seamless system upgrades while reducing resource consumption and improving upgrade efficiency. Attached Figure Description

[0059] To more clearly illustrate the technical solutions in the embodiments of this application or related technologies, the drawings used in the description of the embodiments of this application or related technologies will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0060] Figure 1 This is an application environment diagram of a business system upgrade method in one embodiment;

[0061] Figure 2 This is a flowchart illustrating a business system upgrade method in one embodiment;

[0062] Figure 3 This is a flowchart illustrating the steps of upgrading a target microservice in one embodiment;

[0063] Figure 4 This is a flowchart illustrating step S302 in one embodiment;

[0064] Figure 5 This is a flowchart illustrating step S203 in one embodiment;

[0065] Figure 6 This is a flowchart illustrating the upgrade package distribution steps in one embodiment;

[0066] Figure 7 This is a flowchart illustrating step S602 in one embodiment;

[0067] Figure 8 This is a structural block diagram of a business system upgrade device in one embodiment;

[0068] Figure 9 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0069] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0070] It should be noted that the terms "first," "second," etc., used in this application can be used to describe various elements, but these elements are not limited by these terms. These terms are only used to distinguish the first element from the second element. The terms "comprising" and "having," and any variations thereof, used in this application, are intended to cover non-exclusive inclusion. The term "multiple" used in this application refers to two or more. The term "and / or" used in this application refers to one of the embodiments, or any combination of multiple embodiments.

[0071] Microservices are characterized by independent deployment and autonomous operation, which can improve the scalability and maintenance efficiency of business systems. With the widespread application of microservice architecture in large-scale business systems, the number of microservice instances has surged, version iterations have become more frequent, and microservices do not exist in isolation. There are complex calls and dependencies between microservices, which significantly increases the complexity of business system upgrades. Therefore, upgrade methods such as blue-green deployment and canary deployment have emerged.

[0072] However, the upgrade methods for microservice business systems in related technologies struggle to achieve seamless upgrades while simultaneously considering resource costs and upgrade efficiency. Therefore, how to reduce resource consumption and improve upgrade efficiency while achieving seamless system upgrades has become a pressing technical problem to be solved in this field.

[0073] The business system upgrade method provided in this application embodiment can be applied to, for example, Figure 1 The application environment shown is as follows. The control node communicates with the business nodes. The control node issues control commands to the business nodes, and the business nodes respond to these commands by performing corresponding upgrade operations. Each microservice is deployed on its respective business node. The control node can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing cloud computing services.

[0074] In one exemplary embodiment, such as Figure 2 As shown, a business system upgrade method is provided, which can be applied to... Figure 1 The following is an example of a control node in a system. This embodiment includes the following steps:

[0075] S201 divides each microservice in the business system to be upgraded into at least two microservice groups.

[0076] For example, each microservice in the business system to be upgraded can be divided into two microservice groups. Both microservice groups can independently implement normal business functions and carry production traffic, so that the business system can maintain normal operation when only one microservice group is online and operating normally.

[0077] Optionally, if the microservices to be upgraded in the business system to be upgraded are divided into two or more microservice groups, then at least when each microservice group is offline, the other microservice groups should be able to operate normally, so as to ensure that when one microservice group is offline to execute the upgrade process, the other microservice groups can keep the business system running normally.

[0078] S202 sets the target microservice group to an offline state and controls the target microservice group to perform an upgrade operation.

[0079] The target microservice group can be any one of at least two microservice groups.

[0080] In this embodiment, any one of the above at least two microservice groups can be identified as the target microservice group. The target microservice group is then safely taken offline from the online group of the traffic proxy and service registry to stop receiving external traffic. Finally, the target microservice group is controlled to perform an upgrade operation.

[0081] S203, after the target microservice group has completed the upgrade operation, set the target microservice group to online status, set the other microservice groups in at least two microservice groups other than the target microservice group to offline status, and control the other microservice groups to perform upgrade operations.

[0082] In one possible implementation, taking the division of the microservice to be upgraded into at least two microservice groups as an example, assuming the first microservice group is first identified as the target microservice group, the first microservice group can be securely taken offline from the online groups of the traffic proxy and service registry, ceasing to receive external traffic, and the first microservice group is controlled to perform the upgrade operation. After the first microservice group completes the upgrade operation, it is switched to the online group of the traffic proxy and service registry. Then, the second microservice group is securely taken offline from the online group of the traffic proxy and service registry, ceasing to receive external traffic, and the second microservice group is controlled to perform the upgrade operation. After the second microservice group completes the upgrade, it is switched to the online group of the traffic proxy and service registry, thus completing the upgrade of the business system.

[0083] Optionally, if the microservices to be upgraded in the business system are divided into two or more microservice groups, the upgrade operation is executed sequentially for each microservice group. Before executing the upgrade operation, the microservice group is set to an offline state. After the upgrade operation is completed, the microservice group is set to an online state. Then, another microservice group is set to an offline state, and after the upgrade operation is completed, the other microservice group is set to an online state, until all microservice groups have completed the upgrade operation and are set to an online state, thus completing the upgrade of the business system.

[0084] In this embodiment, firstly, by dividing the system into microservice groups, only one group of microservices is set to an offline state to perform the upgrade operation at any given time, while the remaining microservice groups remain online and handle business traffic normally, achieving a seamless upgrade process for users. Secondly, this embodiment directly utilizes existing microservice instance resources to complete the upgrade, eliminating the need for additional server or container deployment, significantly saving hardware and maintenance costs and substantially reducing resource consumption. Furthermore, this embodiment performs the upgrade operation on a group basis, avoiding the need to upgrade each microservice instance individually, and eliminating the need to configure complex traffic routing rules, simplifying the operation process, achieving a seamless system upgrade while reducing resource consumption and improving upgrade efficiency.

[0085] Based on the above embodiments, S202 can be implemented in the following ways:

[0086] For each target microservice in the target microservice group, control the corresponding business nodes to upgrade the target microservice using the corresponding upgrade package.

[0087] In this embodiment, each microservice is deployed on each business node. When performing an upgrade operation on the target microservice group, the upgrade package corresponding to each target microservice in the target microservice group can be obtained. Then, for each target microservice, the upgrade package corresponding to the target microservice is distributed to the business node where the target microservice is deployed, thereby controlling the business node where the target microservice is deployed to upgrade the target microservice using the upgrade package corresponding to the target microservice.

[0088] In this embodiment, for each target microservice in the target microservice group, the corresponding business node is controlled to upgrade the target microservice using the corresponding upgrade package. By performing the upgrade operation on a single microservice basis for each target microservice, parallel upgrades of each microservice within the microservice group are achieved, shortening the upgrade time of the target microservice group and improving upgrade efficiency. Furthermore, upgrading based on the upgrade package corresponding to each target microservice improves the accuracy of the upgrade and enhances its reliability and security.

[0089] This embodiment will explain in detail the process of upgrading the target microservice using the corresponding upgrade package on the business node corresponding to the target microservice. In an exemplary embodiment, such as Figure 3 As shown, the business nodes corresponding to the target microservice can be controlled to perform any of the following update operations based on the upgrade package:

[0090] S301 upgrades the database of the target microservice based on the database change script in the upgrade package.

[0091] For example, the database change script, configuration file template, and program files corresponding to the target version can be packaged into an upgrade package.

[0092] In this embodiment, after the upgrade package corresponding to the target microservice is distributed to the business node where the target microservice is deployed, the business node can be controlled to decompress the upgrade package to obtain the database change script, configuration file template and program file encapsulated in the upgrade package. Then, the business node is controlled to execute the database change script in the database of the target microservice, thereby upgrading the database of the target microservice.

[0093] It should be noted that the database change script adopts a forward-compatible design, ensuring that during database structure upgrades, older version microservice instances that have not yet been upgraded can still perform correct read and write operations on the changed database.

[0094] S302 upgrades the runtime configuration of the target microservice based on the configuration file template in the upgrade package.

[0095] In one embodiment, business nodes can be controlled to obtain full configuration information of the target version based on a configuration file template, and update the running configuration of the target microservice based on the full configuration information.

[0096] S303 upgrades the program files of the target microservice based on the target version of the program files in the upgrade package.

[0097] For example, after obtaining the program file of the target version in the upgrade package, the business node can be controlled to stop the target microservice process, replace the current program file of the target microservice with the program file of the target version, and then restart the target microservice process. The version number of the replaced program file is verified to be consistent with the target version, and the target microservice process is checked to see if it is running normally. If the version number verification is successful and the target microservice process is running normally, the program file upgrade of the target microservice is determined to be complete.

[0098] In this embodiment, the upgrade process for the target microservice is refined into database upgrade, runtime configuration update, and program file upgrade. Based on the target version information in the upgrade package, automatic upgrades of the target microservice are achieved, simplifying the upgrade process and improving its efficiency. Simultaneously, the automatic upgrade process based on the upgrade package reduces the risk of human error, further enhancing the reliability and security of the target microservice upgrade.

[0099] This embodiment will explain the detailed process of running configuration upgrades. In an exemplary embodiment, such as Figure 4 As shown, S302 above includes:

[0100] S401 retrieves the full configuration information of the target version from the environment configuration repository based on the configuration file template.

[0101] In this embodiment, the business node can be controlled to pull the specific configuration value corresponding to the configuration file template from the environment configuration repository based on the configuration file template, and then obtain the full configuration information of the target version based on the configuration file template and its corresponding specific configuration value.

[0102] S402 compares the full configuration information with the current configuration information of the target microservice to obtain the changes.

[0103] For example, the current configuration information of the target microservice that is currently in effect can be obtained from the configuration center, and the full configuration information can be compared with the current configuration information based on the preset configuration items to obtain the change content corresponding to each preset configuration item.

[0104] S403, if the changes are confirmed to meet the preset change requirements, upgrade the runtime configuration of the target microservice based on the full configuration information of the target version.

[0105] In one embodiment, the changes corresponding to each preset configuration item can be checked. If the changes are confirmed to meet the preset change requirements, the business node can be controlled to replace the current configuration information of the target microservice with the full configuration information of the target version, so as to upgrade the running configuration of the target microservice.

[0106] For example, the front-end interface can display the changes corresponding to each preset configuration item and receive the check results input by the user. If the check results indicate that the changes meet the preset change requirements, the business node can be controlled to replace the current configuration information of the target microservice with the full configuration information of the target version, so as to upgrade the running configuration of the target microservice.

[0107] In this embodiment, the full configuration information of the target version is compared with the current, unupdated configuration information to determine the changes, thus avoiding accidental modification or deletion of critical configuration items due to direct overwriting. The update is only performed after confirming that the changes meet preset requirements, preventing system failures caused by incorrect configuration. Furthermore, full information is pulled from the environment repository based on the configuration file template, ensuring consistency between the configuration and the environment, reducing the risk of configuration errors, and further guaranteeing the reliability of configuration upgrades.

[0108] Based on the above embodiments, the method further includes the following steps:

[0109] If any update operation fails during the upgrade process, a rollback operation will be performed based on the initial version information of the target microservice. The initial version information is obtained by backing up the initial version information of the target microservice before the upgrade operation is performed.

[0110] Optionally, after distributing the upgrade package corresponding to the target microservice to the business nodes where the target microservice is deployed, the business nodes can be controlled to perform a full backup of the initial version information of the target microservice, such as program files and configuration files. During the sequential upgrade of the database, runtime configuration, and program files of the target microservice, the execution status of each update operation is monitored. If any update operation fails, the upgrade process is immediately paused, and then each update operation is rolled back in reverse order based on the backed-up initial version information to restore the target microservice to its initial state.

[0111] For example, if an anomaly occurs during the database upgrade of the target microservice, and the runtime configuration and program files of the target microservice have not yet been updated, then it is only necessary to perform a rollback operation on the database of the target microservice based on the backup initial version information, so as to restore the database of the target microservice to the initial state before the upgrade.

[0112] Alternatively, if an anomaly occurs during the upgrade of the target microservice's application files, and the target microservice's database and runtime configuration have already been upgraded, then a rollback operation can be performed on the target microservice's application files, runtime configuration, and database sequentially based on the backed-up initial version information, so that the target microservice's application files, runtime configuration, and database are all restored to their initial state before the upgrade.

[0113] In this embodiment, a rollback mechanism is introduced during the upgrade process to improve system fault tolerance. When any update operation in the database, configuration, or program files fails, a rollback can be automatically performed based on the pre-backed-up initial version information, avoiding service anomalies caused by partial upgrade failures and improving the security and reliability of business system upgrades.

[0114] This embodiment will explain in detail the process of setting the target microservice group to an online state after the upgrade operation has been completed. In an exemplary embodiment, such as Figure 5 As shown, S203 above includes:

[0115] S501: After the target microservice group has completed the upgrade operation, verify the functionality of the target microservice group based on preset test cases.

[0116] In this embodiment, after the database, runtime configuration, and program files of the target microservice are upgraded, the business nodes can be controlled to execute preset test cases to verify the correctness and stability of the new functions, core business processes, and key interfaces of the target microservice group.

[0117] S502, after successful verification, sets the target microservice group to online status.

[0118] Optionally, if the verification passes, the target microservice group can be set to online status; if the verification fails, the above rollback operation is performed to restore the target microservice's program files, runtime configuration, and database to their initial state before the upgrade.

[0119] In this embodiment, functional verification is performed after the upgrade is completed to ensure that only microservice groups that pass the verification of preset test cases can be brought back online. This can quickly verify the availability and correctness of the upgraded service, reduce the cost of manual regression testing, and ensure the reliability of the upgrade process.

[0120] In one exemplary embodiment, such as Figure 6 As shown, the method also includes the following steps:

[0121] S601 generates upgrade packages for each microservice to be upgraded based on the target version information.

[0122] For example, based on the target version information, artifacts (such as JAR packages, images, or executable files) corresponding to each microservice to be upgraded can be pulled. For each microservice to be upgraded, the artifacts corresponding to the microservice to be upgraded can be integrated and packaged into a standardized upgrade package according to predefined packaging specifications. The upgrade package for each microservice to be upgraded also includes target version metadata, database change scripts, configuration file templates, and verification information.

[0123] S602, based on the topology between each microservice to be upgraded and each business node in the business system to be upgraded, sends the upgrade package corresponding to the microservice to be upgraded to the business node corresponding to the microservice to be upgraded.

[0124] For example, the above topology is the correspondence between the microservice to be upgraded and the addresses of each business node.

[0125] In this embodiment, for each microservice to be upgraded, the address of the business node deploying the microservice to be upgraded can be obtained based on the above topology relationship, and then the upgrade package corresponding to the microservice to be upgraded can be distributed to the business node corresponding to the microservice to be upgraded based on the address of the business node.

[0126] In this embodiment, upgrade packages are generated for each microservice to be upgraded based on the target version information. Then, based on the topological relationship between each microservice and the business nodes in the business system to be upgraded, the upgrade packages are sent to the corresponding business nodes of the microservices to be upgraded. By generating upgrade packages for each microservice based on the target version information, version consistency and traceability are ensured. Furthermore, sending upgrade packages in a targeted manner based on the topological relationship between microservices and business nodes improves the efficiency and reliability of upgrade package distribution.

[0127] This embodiment will explain in detail the process of sending the upgrade package corresponding to the microservice to be upgraded to the corresponding business node. In an exemplary embodiment, such as Figure 7 As shown, the above S602 includes:

[0128] S701: Obtain the communication status of the business node corresponding to the microservice to be upgraded.

[0129] For example, before sending the upgrade package corresponding to the microservice to be upgraded to the business node, the SSH (Secure Shell) passwordless communication status between the control node and the business node can be obtained.

[0130] S702: If the communication status of the business node corresponding to the microservice to be upgraded is normal, send the upgrade package corresponding to the microservice to be upgraded to the business node corresponding to the microservice to be upgraded.

[0131] Optionally, the SSH passwordless communication status between the control node and the business node can be detected. If the communication status of the business node corresponding to the microservice to be upgraded is normal, the upgrade package corresponding to the microservice to be upgraded can be sent to the business node corresponding to the microservice to be upgraded.

[0132] Alternatively, if the communication status of the business node corresponding to the microservice to be upgraded is abnormal, the upgrade process of the microservice to be upgraded can be interrupted, and an alarm message indicating that the communication status of the business node corresponding to the microservice to be upgraded is abnormal can be generated.

[0133] In this embodiment, by pre-checking the communication status of service nodes before sending, the upgrade package is ensured to be distributed only when the nodes are functioning normally. This avoids sending upgrade packages to disconnected or faulty nodes, saving network bandwidth and storage resources. Upon detecting communication abnormalities in a service node, the upgrade process for that microservice is immediately interrupted and an alarm message is generated. This prevents some nodes from experiencing upgrade process anomalies due to unsuccessful upgrade package distribution or inability to issue commands. Furthermore, timely output of alarm messages shortens the time for problem discovery and repair, further improving the reliability and maintainability of the upgrade process.

[0134] The following will explain the overall implementation logic of the microservice architecture-based business system upgrade method proposed in this application through a complete embodiment:

[0135] In this embodiment, the business system upgrade method based on a microservice architecture is deployed at the end of the continuous integration (CI) process. Specifically, it includes: dividing each microservice to be upgraded in the business system into at least two microservice groups; pulling artifacts (such as JAR packages, images, or executable files) corresponding to each microservice to be upgraded based on the target version information; and for each microservice to be upgraded, integrating and encapsulating the artifacts, target version metadata, database change scripts, configuration file templates, and verification information into a standardized upgrade package according to predefined packaging specifications; and determining the address of the business node where each microservice to be upgraded is deployed based on the topological relationship between each microservice and each business node in the business system to be upgraded.

[0136] Before sending the upgrade package corresponding to the microservice to be upgraded to the business node, the SSH passwordless communication status between the control node and the business node is checked. If the communication status of the business node corresponding to the microservice to be upgraded is normal, the upgrade package corresponding to the microservice to be upgraded is sent to the business node corresponding to the microservice to be upgraded.

[0137] After distributing the upgrade package corresponding to the microservice to be upgraded to the business nodes where the microservice to be upgraded is deployed, first control the business nodes to perform a full backup of the initial version information such as the program files and configuration files of the microservice to be upgraded, and then control the business nodes to decompress the upgrade package.

[0138] After the upgrade preparation is complete, identify any one of the at least two microservice groups that has not yet undergone the upgrade as the target microservice group. Securely take this target microservice group offline from the online groups of the traffic proxy and service registry, stopping it from receiving external traffic. Then, for each target microservice in the target microservice group, upgrade its database, runtime configuration, and program files based on the database change scripts, configuration file templates, and program files in the upgrade package. Next, verify the correctness and stability of the newly added functions, core business processes, and key interfaces of the upgraded target microservices. If the verification passes, the target microservice group can be set to online status.

[0139] If any update operation in the database, runtime configuration, or program files fails, or if the functional verification fails, a review operation will be performed based on the backup initial version information to restore the target microservice to its initial state before the upgrade.

[0140] Perform the above upgrade operations on each microservice group in sequence until all microservice groups have completed the upgrade operations and been set to online status, thus completing the upgrade of the business system.

[0141] It should be understood that although the steps in the flowcharts of the embodiments described above 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 flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages in other steps. It is understood that the steps in different embodiments can be freely combined as needed, and all non-contradictory solutions formed by such combinations are within the scope of protection of this application.

[0142] Based on the same inventive concept, this application also provides a business system upgrade apparatus for implementing the business system upgrade method described above. The solution provided by this apparatus is similar to the implementation scheme described in the above method; therefore, the specific limitations in one or more business system upgrade apparatus embodiments provided below can be found in the limitations of the business system upgrade method described above, and will not be repeated here.

[0143] In one exemplary embodiment, such as Figure 8 As shown, a business system upgrade device is provided, including: a microservice group partitioning module, a first upgrade module, and a second upgrade module, wherein:

[0144] The microservice grouping module is used to divide each microservice to be upgraded in the business system into at least two microservice groups.

[0145] The first upgrade module is used to set the target microservice group to an offline state and control the target microservice group to perform upgrade operations; the target microservice group can be any one of at least two microservice groups.

[0146] The second upgrade module is used to set the target microservice group to an online state after the target microservice group has completed the upgrade operation, and to set the other microservice groups (excluding the target microservice group) in at least two other microservice groups to an offline state, and to control the other microservice groups to perform upgrade operations.

[0147] In one embodiment, the first upgrade module includes:

[0148] The microservice upgrade unit is used to control the business nodes corresponding to each target microservice in the target microservice group to upgrade the target microservice using the corresponding upgrade package.

[0149] In one embodiment, the microservice upgrade unit includes any one of the following update sub-units:

[0150] The database update subunit is used to control the business nodes corresponding to the target microservice to upgrade the database of the target microservice based on the database change script in the upgrade package;

[0151] The Run Configuration Update subunit is used to control the business nodes corresponding to the target microservice to upgrade the runtime configuration of the target microservice based on the configuration file template in the upgrade package;

[0152] The program file update subunit is used to control the business nodes corresponding to the target microservice to upgrade the program files of the target microservice based on the target version of the program files in the upgrade package.

[0153] In one embodiment, the runtime configuration update subunit is specifically used to control the business node corresponding to the target microservice to obtain the full configuration information of the target version from the environment configuration repository based on the configuration file template; compare the full configuration information with the current configuration information of the target microservice to obtain the change content; and, if the change content is confirmed to meet the preset change requirements, upgrade the runtime configuration of the target microservice based on the full configuration information of the target version.

[0154] In one embodiment, the device further includes: a rollback module;

[0155] The rollback module is used to perform a rollback operation based on the initial version information of the target microservice if any update operation fails during the upgrade process. The initial version information is obtained by backing up the initial version information of the target microservice before the upgrade operation is performed.

[0156] In one embodiment, the second upgrade module includes:

[0157] The functional verification unit is used to verify the functionality of the target microservice group based on preset test cases after the target microservice group has completed the upgrade operation.

[0158] The status setting unit is used to set the target microservice group to an online state after successful verification.

[0159] In one embodiment, the device further includes:

[0160] The upgrade package generation module is used to generate upgrade packages for each microservice to be upgraded based on the target version information.

[0161] The upgrade package distribution module is used to send the upgrade package corresponding to the microservice to be upgraded to the business node corresponding to the microservice to be upgraded, based on the topology relationship between each microservice to be upgraded and each business node in the business system to be upgraded.

[0162] In one embodiment, the upgrade package distribution module includes:

[0163] The communication status acquisition unit is used to acquire the communication status of the business nodes corresponding to the microservice to be upgraded.

[0164] The upgrade package distribution unit is used to send the upgrade package corresponding to the microservice to be upgraded to the business node corresponding to the microservice to be upgraded when the communication status of the business node corresponding to the microservice to be upgraded is normal.

[0165] In one embodiment, the device further includes:

[0166] The alarm module is used to interrupt the upgrade process of the microservice to be upgraded and generate alarm information indicating that the communication status of the business node corresponding to the microservice to be upgraded is abnormal when the communication status of the business node corresponding to the microservice to be upgraded is abnormal.

[0167] Each module in the aforementioned business system upgrade device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device as software, so that the processor can call and execute the operations corresponding to each module.

[0168] In one exemplary embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 9 As shown, this computer device includes a processor, memory, input / output (I / O) interfaces, and a communication interface. The processor, memory, and I / O interfaces are connected via a system bus, and the communication interface is also connected to the system bus via the I / O interfaces. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and databases. The internal memory provides the environment for the operating system and computer programs stored in the non-volatile storage media to run. The I / O interfaces are used for exchanging information between the processor and external devices. The communication interface is used for communicating with external terminals via a network connection. When the computer program is executed by the processor, it implements a business system upgrade method.

[0169] Those skilled in the art will understand that Figure 9 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0170] In one exemplary embodiment, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps:

[0171] Divide each microservice in the business system to be upgraded into at least two microservice groups;

[0172] Set the target microservice group to offline status and control the target microservice group to perform upgrade operations; the target microservice group can be any one of at least two microservice groups.

[0173] After the target microservice group completes the upgrade operation, set the target microservice group to online status, set the other microservice groups (excluding the target microservice group) to offline status, and control the other microservice groups to perform upgrade operations.

[0174] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0175] For each target microservice in the target microservice group, control the corresponding business nodes to upgrade the target microservice using the corresponding upgrade package.

[0176] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0177] The control unit executes any one of the following update operations on the business node corresponding to the target microservice based on the upgrade package:

[0178] The database of the target microservice is upgraded based on the database change script in the upgrade package;

[0179] The runtime configuration of the target microservice is upgraded based on the configuration file template in the upgrade package;

[0180] The program files of the target microservice are upgraded based on the target version of the program files in the upgrade package.

[0181] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0182] Retrieves full configuration information for the target version from the environment configuration repository based on the configuration file template;

[0183] The changes are obtained by comparing the full configuration information with the current configuration information of the target microservice.

[0184] Once it is confirmed that the changes meet the preset change requirements, the runtime configuration of the target microservice is upgraded based on the full configuration information of the target version.

[0185] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0186] If any update operation fails during the upgrade process, a rollback operation will be performed based on the initial version information of the target microservice. The initial version information is obtained by backing up the initial version information of the target microservice before the upgrade operation is performed.

[0187] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0188] After the target microservice group has completed the upgrade operation, the functionality of the target microservice group is verified based on preset test cases;

[0189] After successful verification, the target microservice group will be set to online status.

[0190] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0191] Based on the target version information, generate upgrade packages for each microservice to be upgraded.

[0192] Based on the topology between each microservice to be upgraded and each business node in the business system to be upgraded, the upgrade package corresponding to the microservice to be upgraded is sent to the business node corresponding to the microservice to be upgraded.

[0193] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0194] Obtain the communication status of the business nodes corresponding to the microservice to be upgraded;

[0195] If the communication status of the business node corresponding to the microservice to be upgraded is normal, send the upgrade package corresponding to the microservice to be upgraded to the business node corresponding to the microservice to be upgraded.

[0196] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0197] If the communication status of the business node corresponding to the microservice to be upgraded is abnormal, the upgrade process of the microservice to be upgraded will be interrupted, and an alarm message indicating that the communication status of the business node corresponding to the microservice to be upgraded is abnormal will be generated.

[0198] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, the computer program performing the following steps when executed by a processor:

[0199] Divide each microservice in the business system to be upgraded into at least two microservice groups;

[0200] Set the target microservice group to offline status and control the target microservice group to perform upgrade operations; the target microservice group can be any one of at least two microservice groups.

[0201] After the target microservice group completes the upgrade operation, set the target microservice group to online status, set the other microservice groups (excluding the target microservice group) to offline status, and control the other microservice groups to perform upgrade operations.

[0202] In one embodiment, when the computer program is executed by a processor, it further performs the following steps:

[0203] For each target microservice in the target microservice group, control the corresponding business nodes to upgrade the target microservice using the corresponding upgrade package.

[0204] In one embodiment, when the computer program is executed by a processor, it further performs the following steps:

[0205] The control unit executes any one of the following update operations on the business node corresponding to the target microservice based on the upgrade package:

[0206] The database of the target microservice is upgraded based on the database change script in the upgrade package;

[0207] The runtime configuration of the target microservice is upgraded based on the configuration file template in the upgrade package;

[0208] The program files of the target microservice are upgraded based on the target version of the program files in the upgrade package.

[0209] In one embodiment, when the computer program is executed by a processor, it further performs the following steps:

[0210] Retrieves full configuration information for the target version from the environment configuration repository based on the configuration file template;

[0211] The changes are obtained by comparing the full configuration information with the current configuration information of the target microservice.

[0212] Once it is confirmed that the changes meet the preset change requirements, the runtime configuration of the target microservice is upgraded based on the full configuration information of the target version.

[0213] In one embodiment, when the computer program is executed by a processor, it further performs the following steps:

[0214] If any update operation fails during the upgrade process, a rollback operation will be performed based on the initial version information of the target microservice. The initial version information is obtained by backing up the initial version information of the target microservice before the upgrade operation is performed.

[0215] In one embodiment, when the computer program is executed by a processor, it further performs the following steps:

[0216] After the target microservice group has completed the upgrade operation, the functionality of the target microservice group is verified based on preset test cases;

[0217] After successful verification, the target microservice group will be set to online status.

[0218] In one embodiment, when the computer program is executed by a processor, it further performs the following steps:

[0219] Based on the target version information, generate upgrade packages for each microservice to be upgraded.

[0220] Based on the topology between each microservice to be upgraded and each business node in the business system to be upgraded, the upgrade package corresponding to the microservice to be upgraded is sent to the business node corresponding to the microservice to be upgraded.

[0221] In one embodiment, when the computer program is executed by a processor, it further performs the following steps:

[0222] Obtain the communication status of the business nodes corresponding to the microservice to be upgraded;

[0223] If the communication status of the business node corresponding to the microservice to be upgraded is normal, send the upgrade package corresponding to the microservice to be upgraded to the business node corresponding to the microservice to be upgraded.

[0224] In one embodiment, when the computer program is executed by a processor, it further performs the following steps:

[0225] If the communication status of the business node corresponding to the microservice to be upgraded is abnormal, the upgrade process of the microservice to be upgraded will be interrupted, and an alarm message indicating that the communication status of the business node corresponding to the microservice to be upgraded is abnormal will be generated.

[0226] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, performs the following steps:

[0227] Divide each microservice in the business system to be upgraded into at least two microservice groups;

[0228] Set the target microservice group to offline status and control the target microservice group to perform upgrade operations; the target microservice group can be any one of at least two microservice groups.

[0229] After the target microservice group completes the upgrade operation, set the target microservice group to online status, set the other microservice groups (excluding the target microservice group) to offline status, and control the other microservice groups to perform upgrade operations.

[0230] In one embodiment, when the computer program is executed by a processor, it further performs the following steps:

[0231] For each target microservice in the target microservice group, control the corresponding business nodes to upgrade the target microservice using the corresponding upgrade package.

[0232] In one embodiment, when the computer program is executed by a processor, it further performs the following steps:

[0233] The control unit executes any one of the following update operations on the business node corresponding to the target microservice based on the upgrade package:

[0234] The database of the target microservice is upgraded based on the database change script in the upgrade package;

[0235] The runtime configuration of the target microservice is upgraded based on the configuration file template in the upgrade package;

[0236] The program files of the target microservice are upgraded based on the target version of the program files in the upgrade package.

[0237] In one embodiment, when the computer program is executed by a processor, it further performs the following steps:

[0238] Retrieves full configuration information for the target version from the environment configuration repository based on the configuration file template;

[0239] The changes are obtained by comparing the full configuration information with the current configuration information of the target microservice.

[0240] Once it is confirmed that the changes meet the preset change requirements, the runtime configuration of the target microservice is upgraded based on the full configuration information of the target version.

[0241] In one embodiment, when the computer program is executed by a processor, it further performs the following steps:

[0242] If any update operation fails during the upgrade process, a rollback operation will be performed based on the initial version information of the target microservice. The initial version information is obtained by backing up the initial version information of the target microservice before the upgrade operation is performed.

[0243] In one embodiment, when the computer program is executed by a processor, it further performs the following steps:

[0244] After the target microservice group has completed the upgrade operation, the functionality of the target microservice group is verified based on preset test cases;

[0245] After successful verification, the target microservice group will be set to online status.

[0246] In one embodiment, when the computer program is executed by a processor, it further performs the following steps:

[0247] Based on the target version information, generate upgrade packages for each microservice to be upgraded.

[0248] Based on the topology between each microservice to be upgraded and each business node in the business system to be upgraded, the upgrade package corresponding to the microservice to be upgraded is sent to the business node corresponding to the microservice to be upgraded.

[0249] In one embodiment, when the computer program is executed by a processor, it further performs the following steps:

[0250] Obtain the communication status of the business nodes corresponding to the microservice to be upgraded;

[0251] If the communication status of the business node corresponding to the microservice to be upgraded is normal, send the upgrade package corresponding to the microservice to be upgraded to the business node corresponding to the microservice to be upgraded.

[0252] In one embodiment, when the computer program is executed by a processor, it further performs the following steps:

[0253] If the communication status of the business node corresponding to the microservice to be upgraded is abnormal, the upgrade process of the microservice to be upgraded will be interrupted, and an alarm message indicating that the communication status of the business node corresponding to the microservice to be upgraded is abnormal will be generated.

[0254] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, artificial intelligence (AI) processors, etc., and are not limited to these.

[0255] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0256] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A method for upgrading a business system, characterized in that, The method includes: Divide each microservice in the business system to be upgraded into at least two microservice groups; Set the target microservice group to an offline state and control the target microservice group to perform an upgrade operation; the target microservice group is any one of the at least two microservice groups. After the target microservice group completes the upgrade operation, the target microservice group is set to online status, and the other microservice groups in the at least two microservice groups other than the target microservice group are set to offline status, and the other microservice groups are controlled to perform the upgrade operation.

2. The method according to claim 1, characterized in that, The step of controlling the target microservice group to perform the upgrade operation includes: For each target microservice in the target microservice group, control the business node corresponding to the target microservice to upgrade the target microservice using the upgrade package corresponding to the target microservice.

3. The method according to claim 2, characterized in that, The step of controlling the business node corresponding to the target microservice to upgrade the target microservice using the upgrade package corresponding to the target microservice includes: Control the business node corresponding to the target microservice to perform any of the following update operations based on the upgrade package: The database of the target microservice is upgraded based on the database change script in the upgrade package; The runtime configuration of the target microservice is upgraded based on the configuration file template in the upgrade package; The program files of the target microservice are upgraded based on the target version of the program files in the upgrade package.

4. The method according to claim 3, characterized in that, The upgrade of the target microservice's runtime configuration based on the configuration file template in the upgrade package includes: Based on the configuration file template, obtain the full configuration information of the target version from the environment configuration repository; The changes are obtained by comparing the full configuration information with the current configuration information of the target microservice. If the changes are confirmed to meet the preset change requirements, the running configuration of the target microservice is upgraded based on the full configuration information of the target version.

5. The method according to claim 3, characterized in that, The method further includes: If any of the update operations fails during the execution of the upgrade operation, a rollback operation is performed based on the initial version information of the target microservice; the initial version information is obtained by backing up the initial version information of the target microservice before the upgrade operation is executed.

6. The method according to any one of claims 1-5, characterized in that, The step of setting the target microservice group to an online state after the target microservice group has completed the upgrade operation includes: After the target microservice group completes the upgrade operation, the functionality of the target microservice group is verified based on preset test cases; After successful verification, the target microservice group will be set to online status.

7. The method according to any one of claims 1-5, characterized in that, The method further includes: Based on the target version information, generate upgrade packages corresponding to each of the microservices to be upgraded; Based on the topological relationship between each microservice to be upgraded and each business node in the business system to be upgraded, the upgrade package corresponding to the microservice to be upgraded is sent to the business node corresponding to the microservice to be upgraded.

8. The method according to claim 7, characterized in that, Sending the upgrade package corresponding to the microservice to be upgraded to the business node corresponding to the microservice to be upgraded includes: Obtain the communication status of the business node corresponding to the microservice to be upgraded; If the communication status of the business node corresponding to the microservice to be upgraded is normal, send the upgrade package corresponding to the microservice to be upgraded to the business node corresponding to the microservice to be upgraded.

9. The method according to claim 8, characterized in that, The method further includes: If the communication status of the business node corresponding to the microservice to be upgraded is abnormal, the upgrade process of the microservice to be upgraded is interrupted, and an alarm message indicating that the communication status of the business node corresponding to the microservice to be upgraded is abnormal is generated.

10. A business system upgrade device, characterized in that, The device includes: The microservice grouping module is used to divide each microservice to be upgraded in the business system into at least two microservice groups. The first upgrade module is used to set the target microservice group to an offline state and control the target microservice group to perform an upgrade operation; the target microservice group is any one of the at least two microservice groups. The second upgrade module is used to set the target microservice group to an online state and set the other microservice groups (excluding the target microservice group) to an offline state after the target microservice group has completed the upgrade operation, and to control the other microservice groups to perform the upgrade operation.

11. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 9.

12. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 9.

13. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 9.

Images