Business application version fallback method and device, electronic equipment and storage medium

Abstract

The embodiment of the invention provides a service application version rollback method and device, electronic equipment and a storage medium. The method can be used in financial or other fields. The method comprises the following steps: when it is monitored that an application version needs to be subjected to version rollback, determining a plurality of target server clusters having service correlation with the application version, determining a traffic adjustment corresponding relationship based on performance and service requirements of each target server cluster, and adjusting the traffic of the application version according to the predetermined traffic adjustment corresponding relationship. And transferring the traffic of the first target server to the second target server cluster, fully deploying the fallback version of the application corresponding to the first target server cluster in the environment where the second target server cluster is located, and recovering the traffic to the fallback first target server cluster. According to the method, the effects of service continuity, system stability, resource optimization and improvement of operation and maintenance efficiency are achieved through accurate operations such as target server cluster selection, flow adjustment, version rollback and flow recovery.

Description

Technical Field

[0001] The present application relates to the financial field or other fields, and in particular to a method, device, electronic device and storage medium for rolling back a business application version. Background Art

[0002] In the banking operating environment, the stable and efficient operation of application systems is the cornerstone of ensuring the continuity of financial services and customer satisfaction. With the rapid development of financial technology and the increasing complexity of banking business needs, version iteration and upgrade of application systems have become increasingly frequent.

[0003] Traditional application version update methods, especially large-scale version rollbacks involving business suspension, will not only have a significant impact on the bank's daily operations, but may also cause a crisis of customer trust and potential financial losses.

[0004] In summary, how to implement application version rollback without shutting down business is a technical problem that urgently needs to be solved in this field. Summary of the invention

[0005] The embodiments of the present application provide a method, device, electronic device and storage medium for rolling back a business application version, so as to solve the technical problem of how to implement application version rollback without stopping business.

[0006] In a first aspect, an embodiment of the present application provides a method for rolling back a service application version, including:

[0007] When it is detected that an application version needs to be rolled back, multiple target server clusters having business relevance to the application version are determined;

[0008] According to a predetermined traffic adjustment correspondence, the traffic of the first target server is transferred to the second target server cluster;

[0009] A rollback version of the application corresponding to the first target server cluster is fully deployed in the environment where the second target server cluster is located, and traffic is restored to the rolled-back first target server cluster.

[0010] In a possible implementation manner, before transferring the traffic of the first target server to the second target server cluster according to the predetermined traffic adjustment correspondence, the method further includes:

[0011] The traffic adjustment correspondence is determined based on the performance and business requirements of each target server cluster, and the traffic adjustment correspondence is used to indicate that the traffic of the first target server cluster is transferred to the second target server cluster.

[0012] In a possible implementation manner, the fully deploying the fallback version of the application corresponding to the first target server cluster in the environment where the second target server cluster is located includes:

[0013] Obtain the software packages, configuration parameters, and dependencies of the rollback version based on business needs;

[0014] Based on the software package, the configuration parameters and the dependencies, a service access and deployment platform is used to fully deploy a fallback version of the application corresponding to the first target server cluster in the environment where the second target server cluster is located.

[0015] In a possible implementation, the method further includes:

[0016] Determine whether there are application anomalies based on the log information obtained in real time;

[0017] If it is determined that there is an application anomaly, an anomaly analysis is performed on the application with the application anomaly to determine whether to perform a version rollback.

[0018] In a possible implementation, the method further includes:

[0019] Reclaiming the server in the first target server cluster using the service access and deployment platform, and re-registering the server in the second target server cluster;

[0020] Accordingly, based on the software package, the configuration parameters and the dependencies, the fallback version of the application corresponding to the first target server cluster is fully deployed in the environment where the second target server cluster is located using the service access and deployment platform, including:

[0021] Based on the software package, the configuration parameters and the dependencies, a service access and deployment platform is used to configure a fallback version of the re-registered server in the environment where the second target server cluster is located.

[0022] In a possible implementation manner, determining the traffic adjustment correspondence relationship based on the performance and service requirements of each target server cluster includes:

[0023] Obtain performance data of each server cluster, including CPU usage, memory usage, disk information, and network bandwidth;

[0024] Analyze the business traffic currently carried by each target server cluster, where the business traffic includes traffic type, traffic size, and access mode;

[0025] The traffic adjustment correspondence is determined based on the performance data and service traffic of each server cluster.

[0026] In a second aspect, an embodiment of the present application provides a device for rolling back a service application version, including:

[0027] A determination module, for determining, when detecting that an application version needs to be rolled back, a plurality of target server clusters that are business-relevant to the application version;

[0028] A transfer module, configured to transfer the traffic of the first target server to the second target server cluster according to a predetermined traffic adjustment correspondence relationship;

[0029] The deployment module is used to fully deploy the rollback version of the application corresponding to the first target server cluster in the environment where the second target server cluster is located, and restore the traffic to the rolled-back first target server cluster.

[0030] In a possible implementation manner, the determining module is further configured to:

[0031] The traffic adjustment correspondence is determined based on the performance and business requirements of each target server cluster, and the traffic adjustment correspondence is used to indicate that the traffic of the first target server cluster is transferred to the second target server cluster.

[0032] In a possible implementation manner, the deployment module is specifically used to:

[0033] Obtain the software packages, configuration parameters, and dependencies of the rollback version based on business needs;

[0034] Based on the software package, the configuration parameters and the dependencies, a service access and deployment platform is used to fully deploy a fallback version of the application corresponding to the first target server cluster in the environment where the second target server cluster is located.

[0035] In a possible implementation manner, the determining module is further configured to:

[0036] Determine whether there are application anomalies based on the log information obtained in real time;

[0037] If it is determined that there is an application anomaly, an anomaly analysis is performed on the application with the application anomaly to determine whether to perform a version rollback.

[0038] In a possible implementation manner, the deployment module is further specifically configured to:

[0039] Reclaiming the server in the first target server cluster using the service access and deployment platform, and re-registering the server in the second target server cluster;

[0040] Correspondingly, the deployment module uses the service access and deployment platform to fully deploy the fallback version of the application corresponding to the first target server cluster in the environment where the second target server cluster is located based on the software package, the configuration parameters and the dependencies, specifically including:

[0041] Based on the software package, the configuration parameters and the dependencies, a service access and deployment platform is used to configure a fallback version of the re-registered server in the environment where the second target server cluster is located.

[0042] In a possible implementation manner, the determining module is specifically configured to:

[0043] Obtain performance data of each server cluster, including CPU usage, memory usage, disk information, and network bandwidth;

[0044] Analyze the business traffic currently carried by each target server cluster, where the business traffic includes traffic type, traffic size, and access mode;

[0045] The traffic adjustment correspondence is determined based on the performance data and service traffic of each server cluster.

[0046] In a third aspect, an embodiment of the present application provides an electronic device, including: a memory, a processor;

[0047] The memory stores computer-executable instructions;

[0048] The processor executes the computer-executable instructions stored in the memory, so that the processor executes the above first aspect and / or various possible implementations of the first aspect.

[0049] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed by a processor, they are used to implement the first aspect above and / or various possible implementations of the first aspect.

[0050] In a fifth aspect, an embodiment of the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the above first aspect and / or various possible implementation methods of the first aspect.

[0051] The business application version rollback method, device, electronic device and storage medium provided in the embodiment of the present application, when it is detected that there is an application version that needs to be rolled back, multiple target server clusters with business relevance to the application version are determined, and the traffic adjustment correspondence is determined based on the performance and business requirements of each target server cluster. According to the predetermined traffic adjustment correspondence, the traffic of the first target server is transferred to the second target server cluster, and the rollback version of the application corresponding to the first target server cluster is fully deployed in the environment where the second target server cluster is located, and the traffic is restored to the first target server cluster after the rollback. This method achieves business continuity, system stability, resource optimization, operation and maintenance efficiency improvement, and enhanced system maintainability through precise target server cluster selection, traffic adjustment, version rollback and traffic recovery operations. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0053] Figure 1 Schematic diagram of the process of rolling back the business application version provided in this application Figure 1 ;

[0054] Figure 2 Schematic diagram of the process of rolling back the business application version provided in this application Figure 2 ;

[0055] Figure 3 Schematic diagram of the process of rolling back the business application version provided in this application Figure 3 ;

[0056] Figure 4 Schematic diagram of the process of rolling back the business application version provided in this application Figure 4 ;

[0057] Figure 5 A schematic diagram of the structure of the rollback device for the service application version provided by this application;

[0058] Figure 6 A schematic diagram of the structure of the electronic device provided in this application.

[0059] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0060] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0061] In the banking operating environment, the stable and efficient operation of application systems is the cornerstone of ensuring the continuity of financial services and customer satisfaction. With the rapid development of financial technology and the increasing complexity of banking business needs, version iteration and upgrade of application systems have become increasingly frequent. Traditional application version update methods, especially large-scale version rollbacks involving suspension of business, will not only have a significant impact on the daily operations of banks, but may also cause a crisis of customer trust and potential financial losses. In summary, how to achieve application version rollback without suspension of business is a technical problem that needs to be solved urgently in this field.

[0062] In response to the above problems, the present application provides a business application version rollback method, device, electronic device and storage medium, which realizes the rollback of the application version without stopping business. Specifically, in the prior art, it is usually necessary to suspend the business in the running environment and then adjust the application version. This will not only have a significant impact on the daily operations of the bank, but may also cause a crisis of customer trust and potential financial losses. In view of these problems, the inventor studied whether it is possible to use traffic management tools to stably transfer the traffic through the server cluster to the server cluster related to the business of the server cluster when the application version needs to be adjusted, and then restore the traffic after deploying the rolled back version. Business continuity and system stability are achieved. Based on this, the solution of the present application is proposed.

[0063] It should be noted that the rollback method, device, electronic device and storage medium of the business application version of the present application can be used in the financial field or other fields, and can also be used in any field except the financial field or other fields. The application field of the rollback method, device, electronic device and storage medium of the business application version of the present application is not limited.

[0064] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0065] Figure 1 Schematic diagram of the process of rolling back the business application version provided in this application Figure 1 ,like Figure 1As shown, the method includes:

[0066] S101: When it is detected that an application version needs to be rolled back, multiple target server clusters having business relevance to the application version are determined.

[0067] In this step, in order to ensure the stability of the operating system and to roll back the problematic application version while ensuring business continuity and stability, the operating data of each application in the operating environment is detected in real time. When it is detected that a version rollback is needed, multiple target server clusters that are business-relevant to the application version are determined.

[0068] Specifically, based on the log information obtained in real time, it is determined whether there is an application anomaly. If it is determined that there is an application anomaly, an anomaly analysis is performed on the application with the application anomaly to determine whether to perform a version rollback.

[0069] S102: According to a predetermined traffic adjustment correspondence, transfer the traffic of the first target server to the second target server cluster.

[0070] In this step, after the target server cluster is determined, in order to ensure that the version rollback does not affect the system operation, the traffic of the first target server cluster that needs to be rolled back is transferred.

[0071] Specifically, in order to ensure that the service is not affected after the traffic transfer, a traffic adjustment correspondence is predetermined, wherein the traffic adjustment correspondence is used to indicate that the traffic of the first target server cluster is transferred to the second target server cluster. Then, traffic transfer is performed based on the correspondence between the server clusters in the traffic adjustment correspondence.

[0072] It should be noted that for the server cluster of the version to be rolled back, traffic transfer can be performed sequentially or synchronously, and can be selected based on the actual operation of the actual business system. The embodiments of the present application do not make specific limitations.

[0073] S103: Fully deploy the rollback version of the application corresponding to the first target server cluster in the environment where the second target server cluster is located, and restore the traffic to the rolled-back first target server cluster.

[0074] In this step, after the traffic transfer is completed, the fallback version of the application corresponding to the first target server cluster is fully deployed in the environment where the second target server cluster is located, and then the traffic is restored to the deployed fallback version.

[0075] Specifically, according to business needs, obtain the software package, configuration parameters and dependencies of the fallback version, and based on the software package, configuration parameters and dependencies, use the service access and deployment platform to fully deploy the fallback version of the corresponding application of the first target server cluster in the environment where the second target server cluster is located.

[0076] Optionally, before step S102, the method may further include:

[0077] S104: Determine a traffic adjustment correspondence based on the performance and business requirements of each target server cluster.

[0078] In this step, in order to ensure the continuity and stability of business operation, it is necessary to determine the traffic adjustment correspondence based on the performance and business requirements of each target server cluster.

[0079] Specifically, the performance data of each server cluster is obtained, the business traffic currently carried by each target server cluster is analyzed, and the traffic adjustment correspondence is determined based on the performance data and business traffic of each server cluster.

[0080] For example, take the bank's operating environment as two environments, computer room A and computer room B. Computer room A is deployed with Group 2 and Group 3, and computer room B is deployed with Group 1. When it is detected that a version rollback is needed, the information of the two computer rooms is imported into the service access and deployment platform in advance, and the traffic is transferred to Group 1. Then the service access and deployment platform recovers the server information of Group 2 / Group 3 in computer room A, and fully deploys the rollback version of Group 2 / Group 3 in computer room B, and then transfers the traffic back to Group 2 / Group 3. If Group 1 also needs a version rollback, all the traffic of Group 1 is switched to Group 2 / Group 3, and then the service access and deployment platform recovers the server information of Group 1 in computer room B, and fully deploys the rollback version of Group 1 in computer room A, and finally restores the traffic of each server.

[0081] The business application version rollback method provided in the embodiment of the present application determines multiple target server clusters that are business-related to the application version when it is detected that an application version needs to be rolled back, determines the traffic adjustment correspondence based on the performance and business requirements of each target server cluster, and transfers the traffic of the first target server to the second target server cluster according to the predetermined traffic adjustment correspondence. The rollback version of the application corresponding to the first target server cluster is fully deployed in the environment where the second target server cluster is located, and the traffic is restored to the first target server cluster after the rollback. This method achieves business continuity, system stability, resource optimization, operation and maintenance efficiency improvement, and enhanced system maintainability through precise target server cluster selection, traffic adjustment, version rollback, and traffic recovery operations.

[0082] Figure 2 Schematic diagram of the process of rolling back the business application version provided in this application Figure 2 ,like Figure 2 As shown, based on the above embodiment, step 103 specifically includes:

[0083] S201: Obtain the software package, configuration parameters, and dependencies of the rollback version according to business requirements.

[0084] S202: Based on the software package, configuration parameters and dependencies, a service access and deployment platform is used to fully deploy a fallback version of the application corresponding to the first target server cluster in the environment where the second target server cluster is located.

[0085] First, collaborate with the development team or version control system to identify the application version to which you need to roll back. Download the specified version of the software package from the version control system, software repository, or backup storage. Ensure the integrity and correctness of the software package and verify it when necessary. Consult the configuration document or configuration file of the first target server cluster and extract the configuration parameters that match the rollback version. Ensure that the configuration parameters meet current business requirements and are compatible with the rollback version of the software. Use dependency management tools (such as Maven, Gradle, npm, etc.) to analyze the dependencies of the rollback version of the software. List all required dependencies and their versions to ensure that they are compatible with the rollback version of the software.

[0086] Ensure that the hardware and operating system of the second target server cluster meet the deployment requirements of the fallback version software. Clean up irrelevant applications and files on the second target server cluster to avoid interfering with the deployment of the fallback version. Use the upload function provided by the deployment platform to upload the fallback version software package to the second target server cluster. Configure the corresponding environment variables on the second target server cluster according to the extracted configuration parameters. Ensure that the environment variables are set correctly to support the operation of the fallback version software. Use the deployment platform or dependency management tool to install all required dependencies on the second target server cluster. Ensure that the versions of the dependencies are compatible with the fallback version software and can pass the dependency verification. Perform deployment operations on the deployment platform to install the fallback version software package on the second target server cluster. Complete the steps of installing, configuring, and starting the software according to the operation guide of the deployment platform. Perform necessary verification tests on the deployment platform to ensure that the fallback version software can run normally on the second target server cluster. Monitor the performance and stability of the second target server cluster to ensure that no abnormalities or errors occur.

[0087] The method for rolling back the business application version provided in the application embodiment obtains the software package, configuration parameters and dependencies of the rolled back version according to business needs, and based on the software package, configuration parameters and dependencies, uses the service access and deployment platform to fully deploy the rolled back version of the corresponding application of the first target server cluster in the environment where the second target server cluster is located. This method has shown significant technical effects in ensuring business continuity, improving deployment efficiency, ensuring system stability, optimizing resource utilization, and improving version management capabilities. These effects work together on the entire business deployment process, providing a strong guarantee for the smooth operation and sustainable development of the business.

[0088] Figure 3 Schematic diagram of the process of rolling back the business application version provided in this application Figure 3 ,like Figure 3 As shown, based on the above embodiment, step S101 specifically includes:

[0089] S301: Determine whether there is an application anomaly based on the log information obtained in real time.

[0090] S302: If it is determined that there is an application anomaly, an anomaly analysis is performed on the application with the application anomaly to determine whether to perform a version rollback.

[0091] Use log collection tools (such as Logstash, Fluentd, Filebeat, etc.) to collect log information from application servers, databases, middleware and other components in real time. Ensure the integrity and accuracy of logs, including timestamps, log levels, log content, etc. Store the collected log information in a centralized log storage system, such as Elasticsearch, Splunk, etc. This facilitates subsequent log retrieval and analysis. Configure log monitoring rules, such as keyword matching, error level filtering, etc., to monitor log information in real time. When a log that meets the rules is monitored, an alarm notification is triggered.

[0092] When the log monitoring rule is triggered, an alarm notification is sent to the operation and maintenance personnel through email, SMS, phone, instant messaging tools, etc. The alarm notification should include detailed information such as the time, location, and log content of the exception. After receiving the alarm notification, the operation and maintenance personnel confirm whether there is an application exception based on the log information and system status. The nature and severity of the exception can be judged by the error code, exception stack, business data, etc. in the log content.

[0093] Analyze the problems of applications that are confirmed to have anomalies to determine the causes of the anomalies and the possible scope of impact. A comprehensive analysis can be conducted in combination with system architecture, business processes, historical experience, etc. Assess the impact of the anomaly on the business, including user experience, business continuity, data security, etc., and formulate a response plan based on the assessment results. Based on the results of the anomaly analysis, determine whether the conditions for version rollback are met. Rollback conditions may include that the anomaly cannot be repaired immediately, the anomaly seriously affects the business, and the rollback version has been fully tested. If you decide to roll back a version, you need to prepare the software package, configuration parameters, dependencies, etc. of the rollback version in advance. Ensure that the rollback version is compatible with the current environment and has been fully tested and verified.

[0094] The business application version rollback method provided in the application embodiment determines whether there is an application anomaly based on the real-time acquired log information. If it is determined that there is an application anomaly, an anomaly analysis is performed on the application with the application anomaly to determine whether to roll back the version. This method effectively improves the stability, reliability and user experience of the system through technical means such as real-time log analysis, precise problem location, intelligent decision-making and version management, while optimizing resource utilization and cost-effectiveness.

[0095] Figure 4 Schematic diagram of the process of rolling back the business application version provided in this application Figure 4 ,like Figure 4 As shown, based on the above embodiment, step S104 specifically includes:

[0096] S401: Obtain performance data of each server cluster.

[0097] S402: Analyze the service traffic currently carried by each target server cluster.

[0098] S403: Determine a traffic adjustment correspondence based on the performance data and service traffic of each server cluster.

[0099] You can use system monitoring tools to obtain performance information for each server cluster. For example, for Windows systems, you can use Task Manager or Performance Monitor. For Linux systems, you can use command line tools such as top, htop, and vmstat. You can choose open source monitoring software such as Zabbix, Nagios, and Cacti. Or use the monitoring service of a cloud service provider to monitor data. The monitoring system can execute the command line tools provided by the node operating system and obtain the required monitoring data from the results of the command execution.

[0100] Install traffic monitoring applications on the server, such as Datadog, New Relic, etc. These applications usually provide mobile versions, which are convenient for viewing and analyzing data on mobile phones. If the server monitoring service provider provides an API interface, you can call these interfaces by writing code to obtain traffic data. The acquired data can be visualized on mobile devices, such as generating charts and reports. Use remote desktop connection tools (such as Microsoft's Remote Desktop, TeamViewer, AnyDesk, etc.) to directly access the server. Operate the server on your mobile phone like on a computer, and view and analyze traffic data. Import the server's traffic data into third-party data analysis platforms such as Google Analytics and Matomo. Use the powerful analysis functions of these platforms to conduct detailed traffic analysis.

[0101] Compare and analyze the obtained server cluster performance data with the business traffic data. Find out the performance bottlenecks and traffic peak periods, as well as the correlation. According to the analysis results, formulate targeted traffic adjustment strategies. For example, increase server resources or optimize application performance during traffic peak periods to cope with high concurrent access.

[0102] The application embodiment provides a rollback method for the service application version, obtains the performance data of each server cluster, analyzes the service traffic currently carried by each target server cluster, and determines the traffic adjustment correspondence based on the performance data and service traffic of each server cluster. This method effectively improves resource utilization efficiency, system stability, and service processing capabilities by accurately grasping the server cluster status, scientifically analyzing the service traffic distribution, and reasonably determining the traffic adjustment correspondence.

[0103] Figure 5 A schematic diagram of the structure of the rollback device for the service application version provided by this application, such as Figure 5 As shown, the service application version rollback device 500 provided in this embodiment includes:

[0104] The determination module 501 is used to determine a plurality of target server clusters that are business-relevant to the application version when it is detected that an application version needs to be rolled back.

[0105] The transfer module 502 is used to transfer the traffic of the first target server to the second target server cluster according to a predetermined traffic adjustment correspondence.

[0106] The deployment module 503 is used to fully deploy the rollback version of the application corresponding to the first target server cluster in the environment where the second target server cluster is located, and restore the traffic to the rolled-back first target server cluster.

[0107] In a possible implementation manner, the determination module 501 is further configured to:

[0108] Based on the performance and business requirements of each target server cluster, a traffic adjustment correspondence is determined, where the traffic adjustment correspondence is used to indicate that the traffic of the first target server cluster is transferred to the second target server cluster.

[0109] In a possible implementation, the deployment module 503 is specifically configured to:

[0110] Obtain the software packages, configuration parameters, and dependencies of the rollback version based on business needs;

[0111] Based on the software package, configuration parameters and dependencies, the service access and deployment platform is used to fully deploy the fallback version of the corresponding application of the first target server cluster in the environment where the second target server cluster is located.

[0112] In a possible implementation manner, the determination module 501 is further configured to:

[0113] Determine whether there are application anomalies based on the log information obtained in real time;

[0114] If it is determined that there is an application anomaly, an anomaly analysis is performed on the application with the application anomaly to determine whether to perform a version rollback.

[0115] In a possible implementation manner, the deployment module 503 is further specifically configured to:

[0116] Reclaim the server in the first target server cluster using the service access and deployment platform, and re-register it in the second target server cluster;

[0117] Accordingly, the deployment module 503 deploys the fallback version of the application corresponding to the first target server cluster in the environment where the second target server cluster is located in full quantity using the service access and deployment platform based on the software package, configuration parameters and dependencies, specifically including:

[0118] Based on the software package, configuration parameters and dependencies, the service access and deployment platform is used to configure the fallback version of the re-registered server in the environment where the second target server cluster is located.

[0119] In a possible implementation, the determination module 501 is specifically configured to:

[0120] Obtain performance data for each server cluster, including CPU usage, memory usage, disk information, and network bandwidth;

[0121] Analyze the business traffic currently carried by each target server cluster, including traffic type, traffic volume, and access mode;

[0122] Based on the performance data and business traffic of each server cluster, determine the traffic adjustment correspondence.

[0123] The service application version rollback device provided in this embodiment can execute the service application version rollback method provided in the above method embodiment. Its implementation principle and technical effect are similar, and will not be described in detail in this embodiment.

[0124] Figure 6 This is a schematic diagram of the structure of the electronic device provided in this application. Figure 6 As shown, the electronic device 600 provided in this embodiment includes: at least one processor 601 and a memory 602. Optionally, the device 600 also includes a communication component 603. The processor 601, the memory 602 and the communication component 603 are connected via a bus 604.

[0125] In a specific implementation process, at least one processor 601 executes the computer execution instructions stored in the memory 602, so that at least one processor 601 executes the above method.

[0126] The specific implementation process of the processor 601 can be found in the above method embodiment, and its implementation principle and technical effect are similar, so this embodiment will not be repeated here.

[0127] In the above embodiments, it should be understood that the processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), etc. A general-purpose processor may be a microprocessor or any conventional processor. The steps of the method disclosed in the invention may be directly implemented as being executed by a hardware processor, or may be executed by a combination of hardware and software modules in the processor.

[0128] The memory may include a high-speed memory (Random Access Memory, RAM), and may also include a non-volatile memory (Non-volatile Memory, NVM), such as at least one disk storage.

[0129] The bus may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, the bus in the drawings of the present application is not limited to only one bus or one type of bus.

[0130] The present application also provides a computer program product, including a computer program, which implements the above method when executed by a processor.

[0131] The present application also provides a computer-readable storage medium, in which computer-executable instructions are stored. When a processor executes the computer-executable instructions, the above method is implemented.

[0132] The above-mentioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk. The readable storage medium can be any available medium that can be accessed by a general or special-purpose computer.

[0133] An exemplary readable storage medium is coupled to a processor so that the processor can read information from the readable storage medium and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can be located in an application specific integrated circuit (Application Specific Integrated Circuits, referred to as: ASIC). Of course, the processor and the readable storage medium can also exist in the device as discrete components.

[0134] The division of units is only a logical function division, and there may be other divisions in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interface, device or unit, which can be electrical, mechanical or other forms.

[0135] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0136] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0137] If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods of each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk, etc. Various media that can store program codes.

[0138] Those skilled in the art can understand that all or part of the steps of implementing the above-mentioned method embodiments can be completed by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the steps of the above-mentioned method embodiments are executed; and the aforementioned storage medium includes: ROM, RAM, disk or optical disk and other media that can store program codes.

[0139] Finally, it should be noted that those skilled in the art will readily conceive of other embodiments of the present invention after considering the specification and practicing the invention disclosed herein. The present invention is intended to cover any variations, uses or adaptations of the present invention, which follow the general principles of the present invention and include common knowledge or customary technical means in the art not disclosed by the present invention, are not limited to the precise structure described above and shown in the drawings, and may be modified and changed in various ways without departing from the scope thereof. The scope of the present invention is limited only by the appended claims.

Claims

1. A method for rolling back a business application version, characterized in that: include: When it is detected that an application version needs to be rolled back, multiple target server clusters having business relevance to the application version are determined; According to a predetermined traffic adjustment correspondence, the traffic of the first target server is transferred to the second target server cluster; A rollback version of the application corresponding to the first target server cluster is fully deployed in the environment where the second target server cluster is located, and traffic is restored to the rolled-back first target server cluster.

2. The method according to claim 1, characterized in that Before transferring the traffic of the first target server to the second target server cluster according to the predetermined traffic adjustment correspondence, the method further includes: The traffic adjustment correspondence is determined based on the performance and business requirements of each target server cluster, and the traffic adjustment correspondence is used to indicate that the traffic of the first target server cluster is transferred to the second target server cluster.

3. The method according to claim 1, characterized in that The fully deploying the fallback version of the application corresponding to the first target server cluster in the environment where the second target server cluster is located includes: Obtain the software packages, configuration parameters, and dependencies of the rollback version based on business needs; Based on the software package, the configuration parameters and the dependencies, a service access and deployment platform is used to fully deploy a fallback version of the application corresponding to the first target server cluster in the environment where the second target server cluster is located.

4. The method according to claim 1, characterized in that: The method further comprises: Determine whether there are application anomalies based on the log information obtained in real time; If it is determined that there is an application anomaly, an anomaly analysis is performed on the application with the application anomaly to determine whether to perform a version rollback.

5. The method according to claim 3, characterized in that: The method further comprises: Reclaiming the server in the first target server cluster using the service access and deployment platform, and re-registering the server in the second target server cluster; Accordingly, based on the software package, the configuration parameters and the dependencies, the fallback version of the application corresponding to the first target server cluster is fully deployed in the environment where the second target server cluster is located using the service access and deployment platform, including: Based on the software package, the configuration parameters and the dependencies, a service access and deployment platform is used to configure a fallback version of the re-registered server in the environment where the second target server cluster is located.

6. The method according to claim 2, characterized in that The determining the traffic adjustment correspondence relationship based on the performance and business requirements of each target server cluster includes: Obtain performance data of each server cluster, including CPU usage, memory usage, disk information, and network bandwidth; Analyze the business traffic currently carried by each target server cluster, where the business traffic includes traffic type, traffic size, and access mode; The traffic adjustment correspondence is determined based on the performance data and service traffic of each server cluster.

7. A device for rolling back a business application version, characterized in that: include: A determination module, configured to determine, when detecting that an application version needs to be rolled back, a plurality of target server clusters that are business-related to the application version; A transfer module, configured to transfer the traffic of the first target server to the second target server cluster according to a predetermined traffic adjustment correspondence; The deployment module is used to fully deploy the rollback version of the application corresponding to the first target server cluster in the environment where the second target server cluster is located, and restore the traffic to the rolled-back first target server cluster.

8. An electronic device, characterized in that: include: Memory, processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory, so that the processor performs the method according to any one of claims 1 to 6.

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

10. A computer program product, comprising a computer program, wherein when the computer program is executed by a processor, the method according to any one of claims 1 to 6 is implemented.

Images