Service execution method and device, program product, storage medium and electronic equipment

Abstract

The embodiment of the invention provides a service execution method and device, a program product, a storage medium and electronic equipment, and the method comprises the steps: obtaining platform configuration parameters from a platform configuration center under the condition that a first service platform is abnormal when executing a target service, acquiring application mirror image information of the target application from an application mirror image library; configuring a second service platform by using the platform configuration parameters and the application mirror image information; determining service execution resources allocated to the target service from a second service platform according to a service execution demand of the target service; and switching the target service to the second service platform so as to execute the target service through the service execution resource in the second service platform. Through application of the method and the device, the problems that the service execution platform cannot be switched in time and resources are wasted due to lack of flexibility when the service is switched to the second service platform in the related technology are solved, and the effects of switching the service execution platform in time and reducing the waste of the resources are further achieved.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of computers, and specifically, to a method and apparatus for executing a service, a program product, a storage medium, and an electronic device. Background Art

[0002] In the modern information technology environment, enterprises increasingly rely on stable, uninterrupted business platforms to provide continuous service. However, even carefully designed and maintained business platforms can experience anomalies due to various unforeseen factors (such as hardware failures, software defects, natural disasters, or cyberattacks), leading to business interruptions. Business interruptions not only damage a company's reputation but can also result in significant financial losses. Therefore, building an effective disaster recovery system that can quickly restore services on another platform when an anomaly occurs on the primary platform has become an integral part of an enterprise's information technology (IT) architecture.

[0003] In related hot standby disaster recovery solutions, the secondary business platform (i.e., the disaster recovery environment) is always running, with business data and application status synchronized in real time, allowing business takeover in seconds. However, this solution is costly and resource-intensive. For resource-constrained and cost-sensitive enterprises, ensuring a quick and accurate switchover to the secondary business platform while reducing disaster recovery costs is a major challenge. Traditional disaster recovery solutions typically require significant human and material resources, including regular manual testing, complex network configuration, and expensive hardware redundancy. This not only increases the operational and maintenance burden but also limits the widespread adoption and application of disaster recovery solutions. Summary of the Invention

[0004] The embodiments of the present application provide a service execution method and device, program product, storage medium, and electronic device to at least solve the problem in the related art of lack of flexibility when switching the service to the second service platform, resulting in the inability to switch the service execution platform in time and wasting resources.

[0005] According to one embodiment of the present application, a method for executing a business is provided, comprising: when an exception occurs when a first business platform executes a target business, obtaining platform configuration parameters from a platform configuration center, and obtaining application image information of a target application from an application image library, wherein the target application is an application set in the first business platform and used to execute the target business; configuring a second business platform using the platform configuration parameters and the application image information; determining business execution resources allocated to the target business from the second business platform according to business execution requirements of the target business; and switching the target business to the second business platform to execute the target business through the business execution resources in the second business platform.

[0006] In an exemplary embodiment, when an abnormality occurs when the first business platform executes the target business, before obtaining the platform configuration parameters from the platform configuration center and obtaining the application image information of the target application from the application image library, the method further includes: monitoring the status of the first business platform executing the target business through a monitoring application to obtain a monitoring result; when it is determined from the monitoring result that the network of the first business platform is abnormal or the target application service is abnormal, it is determined that an abnormality occurs when the first business platform executes the target business.

[0007] In an exemplary embodiment, after monitoring the status of the first business platform executing the target business through a monitoring application and obtaining the monitoring results, the method further includes: when it is determined from the monitoring results that the first business platform executes the target business normally, periodically obtaining the platform configuration parameters of the first business platform and the application image information of the target application; when it is determined that the platform configuration parameters have changed, storing the changed platform configuration parameters of the first business platform in the platform configuration center; when it is determined that the application image information has changed, obtaining the changed application image information of the target application, and storing the changed application image information in the application image library.

[0008] In an exemplary embodiment, before determining the business execution resources allocated to the above-mentioned target business from the above-mentioned second business platform according to the business execution requirements of the above-mentioned target business, the above-mentioned method also includes: obtaining the log file generated when the above-mentioned first business platform executes the above-mentioned target business; calculating the business weight of the above-mentioned target business based on the above-mentioned log file; and determining the above-mentioned business execution requirements based on the above-mentioned business weight.

[0009] In an exemplary embodiment, the business weight of the target business is calculated based on the log file, including: determining the number of exceptions, the target time, and the first usage rate when the processor in the first business platform reads the target business from the log file, wherein the number of exceptions is the number of exceptions that occur when the first business platform reads the target business within the target time; calculating the reading exception rate of the first business platform based on the number of exceptions and the target time; determining the health parameters of the first business platform based on the reading exception rate and the first usage rate, wherein the health parameters are parameters used to indicate whether the first business platform executes the target business normally within the target time; and determining the business weight using the health parameters.

[0010] In an exemplary embodiment, the business weight includes at least one of the following: a weight indicating the execution priority of the first business platform in executing the target business; and a weight indicating the execution requirement for the first business platform to execute the target business within the target time.

[0011] According to another embodiment of the present application, a business execution device is provided, including: an acquisition module, which is used to obtain platform configuration parameters from a platform configuration center and application image information of a target application from an application image library when an exception occurs when executing a target business on a first business platform, wherein the above-mentioned target application is an application set in the above-mentioned first business platform and used to execute the above-mentioned target business; a configuration module, which is used to configure a second business platform using the above-mentioned platform configuration parameters and the above-mentioned application image information; a determination module, which is used to determine the business execution resources allocated to the above-mentioned target business from the above-mentioned second business platform according to the business execution requirements of the above-mentioned target business; and a switching module, which is used to switch the above-mentioned target business to the above-mentioned second business platform, so as to execute the above-mentioned target business through the above-mentioned business execution resources in the above-mentioned second business platform.

[0012] According to another embodiment of the present application, a computer program product is provided, including a computer program, which implements the steps of any of the above method embodiments when executed by a processor.

[0013] According to another embodiment of the present application, a computer-readable storage medium is provided, in which a computer program is stored. The computer program is configured to execute the steps of any one of the above method embodiments when run.

[0014] According to another embodiment of the present application, an electronic device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0015] Through this application, when an abnormality is detected when the first business platform is executing the target business, the platform configuration parameters are obtained from the platform configuration center, and the image information of the target application is obtained from the application image library. Then, these platform configuration parameters and the information of the target application are used to configure the second business platform, and according to the execution requirements of the target business, the business execution resources allocated to the target business by the second business platform are determined. Finally, the target business is switched from the first business platform to the second business platform, and the second business platform continues to execute the target business. Through pre-configuration and resource allocation, the efficiency and success rate of platform switching are improved, and the problem of lack of flexibility when switching the business to the second business platform in related technologies, resulting in the inability to switch the business execution platform in time and wasting resources, is solved, thereby achieving the effect of switching the business execution platform in time and reducing the waste of resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 This is a schematic diagram of a hardware environment for a method of executing a service according to an embodiment of the present application;

[0017] Figure 2 is a flowchart of a method for executing a service according to an embodiment of the present application;

[0018] Figure 3 is a flowchart of a method for executing a target service according to an embodiment of the present application;

[0019] Figure 4 This is a structural block diagram of a device for executing a service according to an embodiment of the present application. DETAILED DESCRIPTION

[0020] The embodiments of the present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0021] It should be noted that the terms "first", "second", etc. in the description and claims of this application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0022] The method embodiments provided in the embodiments of the present application can be executed in a server device or a similar computing device. Taking running on a server device as an example, Figure 1 This is a hardware environment diagram of a method for executing a service in an embodiment of the present application. Figure 1 As shown, the server device may include one or more ( Figure 1 Only one is shown) a processor 102 (the processor 102 may include but is not limited to a microprocessor MCU or a programmable logic device FPGA and other processing devices) and a memory 104 for storing data, wherein the above-mentioned server device may also include a transmission device 106 for communication functions and an input and output device 108. It will be understood by those skilled in the art that Figure 1 The structure shown is only for illustration and does not limit the structure of the above server device. Figure 1 More or fewer components than shown, or with Figure 1 Different configurations shown.

[0023] The memory 104 can be used to store computer programs, for example, software programs and modules of application software, such as a computer program corresponding to a method for executing a business in an embodiment of the present application. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, that is, implementing the above method. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include a memory remotely located relative to the processor 102, and these remote memories may be connected to a server device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0024] The transmission device 106 is used to receive or send data via a network. A specific example of the aforementioned network may include a wireless network provided by a communication provider of the server device. In one embodiment, the transmission device 106 includes a network interface controller (NIC), which can be connected to other network devices via a base station to enable communication with the Internet. In another embodiment, the transmission device 106 may be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0025] In this embodiment, a method for executing a service is provided. Figure 2 is a flow chart of a method for executing a service according to an embodiment of the present application, such as Figure 2 As shown, the process includes the following steps:

[0026] Step S202: When an exception occurs when the first service platform executes the target service, platform configuration parameters are obtained from the platform configuration center, and application image information of the target application is obtained from the application image library, wherein the target application is an application set in the first service platform and used to execute the target service;

[0027] Optionally, the first business platform in this embodiment is a business platform used in normal operations of the enterprise, usually located in a private cloud environment or data center within the enterprise, and is responsible for daily business operations and service provision.

[0028] Optionally, the target business in this embodiment refers to a specific business or service executed on the first business platform, such as online transactions, data processing, user account management, etc.

[0029] Optionally, the abnormal situation in this embodiment refers to any situation that affects the normal operation of the business encountered by the first business platform when executing the target business, including but not limited to network interruption, hardware failure, software error, database access problem or external attack.

[0030] Optionally, the platform configuration center in this embodiment is a system that centrally manages business platform configuration information, and stores various parameters required for the normal operation of the business platform, such as network configuration, security policies, resource scheduling rules, etc. In actual use, the platform configuration center can also be called the production configuration center (Production Configuration Center, abbreviated as PCC).

[0031] Optionally, the application image library in this embodiment stores service images of all enterprise applications. These images are deployment templates for applications in a containerized environment (such as Docker), and include application code, dependency libraries, resource quota policies (memory / number of replicas, network topology rules, service degradation policies, and operating environments. In actual use, the application image library can also be called a Business Disaster Recovery Center (BDRC).

[0032] Step S204, configuring the second service platform using the platform configuration parameters and the application image information;

[0033] Optionally, the platform configuration parameters in this embodiment are configuration information provided by the platform configuration center, and are used to guide the rapid deployment and operation of the second service platform to ensure that the configuration thereof is as consistent as possible with the configuration of the first service platform.

[0034] Optionally, the application image information of the target application in this embodiment refers to the image information of the application used to execute the target service in the first service platform, including the image version, configuration files, dependencies, etc.

[0035] Step S206 , determining the business execution resources allocated to the target business from the second business platform according to the business execution requirements of the target business;

[0036] Optionally, the second service platform in this embodiment is typically located in a third-party data center or a disaster recovery service platform in a public cloud environment, and is used to take over services when a failure occurs in the first service platform to provide continuous services.

[0037] Optionally, the business execution requirements in this embodiment are intended to ensure that the target business can run efficiently and stably under the second business platform (i.e., the disaster recovery environment) to meet the user's access needs and business performance indicators. Including but not limited to: computing resource requirements (requiring a certain number of CPU cores and corresponding computing power), memory resource requirements, storage resource requirements, network bandwidth and latency requirements, load balancing requirements, security and compliance requirements, data consistency requirements, disaster recovery drills and testing requirements, etc. For example, for an e-commerce company with a large user base, its target business execution requirements may include: computing resources (enough central processing units (CPUs) and memory resources to support peak transaction processing), storage resources (high-performance storage systems for storing product information, user orders and payment records), network resources (high-bandwidth and low-latency networks to ensure fast responses for users to browse web pages, place orders and pay), etc.

[0038] Step S208: switching the target service to the second service platform, so as to execute the target service through the service execution resources in the second service platform.

[0039] Optionally, the business execution resources in this embodiment are resources that provide services for the target business in the disaster recovery environment, including but not limited to computing resources (for example, CPU, random access memory (RAM)), storage resources (for example, disk space for storing application data, databases, log files, configuration files, etc.), network resources (for example, network bandwidth), and service resources (for example, Web servers, database services, message queues, application interface gateways).

[0040] Through the above steps, when an abnormality is detected when the first business platform executes the target business, the platform configuration parameters are obtained from the platform configuration center, and the image information of the target application is obtained from the application image library. Then, these platform configuration parameters and the information of the target application are used to configure the second business platform. Based on the execution requirements of the target business, the business execution resources allocated to the target business by the second business platform are determined. Finally, the target business is switched from the first business platform to the second business platform, and the second business platform continues to execute the target business. Through pre-configuration and resource allocation, the efficiency and success rate of platform switching are improved, and the problem of lack of flexibility when switching the business to the second business platform in related technologies, which leads to the inability to switch the business execution platform in time and waste of resources, is solved, thereby achieving the effect of switching the business execution platform in time and reducing the waste of resources.

[0041] In an exemplary embodiment, when an abnormality occurs when the first business platform executes the target business, before obtaining the platform configuration parameters from the platform configuration center and obtaining the application image information of the target application from the application image library, the method further includes: monitoring the status of the first business platform executing the target business through a monitoring application to obtain a monitoring result; when it is determined from the monitoring result that the network of the first business platform is abnormal or the target application service is abnormal, it is determined that an abnormality occurs when the first business platform executes the target business.

[0042] Optionally, the monitoring application in this embodiment refers to a software tool or service specifically designed to monitor the operating status of the business platform in real time. It can be independently deployed software, a cloud service product, or a monitoring module integrated into the existing IT infrastructure. Such tools usually have functions such as collecting system logs, network traffic, application performance indicators and resource usage, and can perform comprehensive monitoring and analysis of the health status of the first business platform.

[0043] For example, a lightweight probe program deployed in a data center or a first business platform operated by a third-party company can be used to check the network connectivity of the target Internet Protocol (IP) using the Internet Control Message Protocol (ICMP), and to detect the availability of application layer services by using the port handshake of the Transport Layer Security Protocol (TLS) (this dual-protocol detection method can ensure that not only the network is reachable, but also the target service is running normally); when the lightweight probe program performs the "ICMP+TLS port handshake" detection, if three consecutive detections of the target IP fail (i.e., no ICMP echo reply is received or the TLS handshake fails), it is determined that the network of the first business platform is abnormal or the target application service is abnormal, and emergency measures are required to handle it, and it automatically switches to the second business platform (i.e., the disaster recovery environment) and starts the emergency process to ensure service continuity. Through this two-level detection mechanism, the system can effectively monitor the health status of the first business platform (i.e., the primary environment), promptly identify potential service interruption risks, and take prompt action when necessary to ensure that when the primary environment fails, it can switch to the disaster recovery environment in a timely and reliable manner, thereby achieving business continuity and data security.

[0044] Optionally, in actual use, domain names can be configured through the two products DNSPod and "Intelligent Global Traffic Management (IGTM)" to monitor the status of the first business platform executing the target business. DNSPod can perform domain name resolution for the target business being served, and resolve the actually used domain name to the public IP connected to the private cloud (corresponding to the above-mentioned first business platform). The private cloud group provides services through the public IP. DNSpad configures multiple resolution records, pointing to the IPs of multiple service private clouds, and easily implements traffic scheduling. IGTM hosts the business domain name in the form of a canonical name (CNAME) domain name. At the same time, the service detects the production environment IP address from multiple nodes, and configures the public cloud disaster recovery (corresponding to the above-mentioned second business platform) IP as a backup IP address. When IGTM discovers an abnormality in the private cloud IP node, it will call the DNSPod interface to remove the corresponding resolution record from the authority and switch the traffic to the backup public cloud disaster recovery address.

[0045] Optionally, the monitoring results in this embodiment are comprehensive information about the business operation status obtained after the monitoring application analyzes the business platform data, including but not limited to key indicators such as application response time, CPU utilization, memory usage, network latency, error rate, and whether alarms for network anomalies or application service anomalies are detected.

[0046] Optionally, the network anomaly of the first business platform in this embodiment refers to problems occurring within the first business platform or between the platform and the external network, such as network interruption, high latency, data packet loss, etc. These problems may cause the platform to be unable to provide services normally to the outside world or reduce internal communication efficiency.

[0047] Optionally, the target application service anomaly in this embodiment refers to the target business executed on the first business platform encountering a functional failure, performance bottleneck or stability problem, such as application crash, database connection failure, service response timeout, etc.

[0048] For example, consider an online education platform whose primary business platform (i.e., the main environment) resides in the company's internal data center and provides services such as online course access and learning material downloads for all users. The platform's uptime is crucial to the company's business success, requiring a reliable monitoring mechanism to ensure that any anomalies are detected and addressed promptly. The company's operations team deploys a monitoring application, such as Prometheus or Zabbix, on the primary business platform to collect and analyze key business metrics in real time. The monitoring application continuously collects and analyzes metrics such as CPU utilization, memory usage, network traffic, database connections, and response time, generating detailed real-time monitoring reports. By setting thresholds and anomaly detection algorithms, the monitoring application identifies any metric that deviates from normal ranges, such as a sudden spike in CPU utilization, network latency exceeding 100ms, or frequent database connection disconnections. When an anomaly is detected, the monitoring application generates an alert and detailed report clearly indicating the anomaly type, occurrence time, severity, and potentially affected services. If the monitoring results indicate a network anomaly or an anomaly in the target application service, the system automatically determines that the primary business platform has experienced an anomaly while executing the target service, triggering the subsequent disaster recovery failover process.

[0049] Through the above steps, a monitoring application is used to continuously monitor the status of the target business on the first business platform. The monitoring results are analyzed to determine whether there are any network or application service anomalies. If an anomaly is confirmed, the subsequent disaster recovery switchover process is triggered. By introducing an active monitoring mechanism, faults can be detected promptly, response time can be shortened, and the accuracy and speed of disaster recovery decision-making can be improved.

[0050] In an exemplary embodiment, after monitoring the status of the first business platform executing the target business through a monitoring application and obtaining the monitoring results, the method further includes: when it is determined from the monitoring results that the first business platform executes the target business normally, periodically obtaining the platform configuration parameters of the first business platform and the application image information of the target application; when it is determined that the platform configuration parameters have changed, storing the changed platform configuration parameters of the first business platform in the platform configuration center; when it is determined that the application image information has changed, obtaining the changed application image information of the target application, and storing the changed application image information in the application image library.

[0051] Optionally, the monitoring result in this embodiment is to conduct a real-time evaluation of the operating status of the first business platform through a deployed monitoring application or system, including system health, application performance, network status, etc., to determine whether the platform is in normal operation.

[0052] Optionally, the timed acquisition in this embodiment refers to automatically acquiring the latest platform configuration parameters and application image information from the first service platform at preset time intervals, so as to synchronously update data in the platform configuration center and the application image library.

[0053] Optionally, in this embodiment, the application image information in the application image library can be updated in the following manner: configure an rsync server on the version release server of the target application, and when upgrading the program code, simultaneously update the target application in the first business platform and the application image information in the application image library.

[0054] Optionally, in this embodiment, the processing data of the target business will also be updated in the following ways: configure MySQL master-slave synchronization to perform data synchronization, so that the relevant data in the main database of the first business platform is synchronized to the database of the shared server, and the data is kept timely and consistent, and the health of the database is monitored through monitoring; by sharing session data in the MySQL database, a MySQL server is used as a shared server, and all session data is saved on the MySQL server. The second business platform obtains session data from this MySQL server, wherein the server storing the session is an independent MySQL server.

[0055] For example, a bank has its core business systems running in its internal data center (i.e., the primary business platform), including key services such as online banking transactions, account management, and risk assessment. Due to the sensitivity and continuity requirements of the business, the bank needs to ensure that when the main data center encounters a sudden failure, it can quickly start the disaster recovery environment located in a third-party data center and continue to provide services. To achieve this goal, the bank has implemented a disaster recovery synchronization mechanism, that is, when the business is operating normally, the configuration parameters and application image information of the main data center are regularly synchronized to the disaster recovery environment to ensure that its disaster recovery system can take over the latest version of business services at any time. The bank has deployed a monitoring system to continuously monitor the system health status of the data center and the responsiveness of business services. When the monitoring results confirm that the data center and business services are operating normally, the system will enter the synchronization update process. According to the pre-set strategy, for example, at 10 o'clock every night, the system will automatically obtain the latest platform configuration parameters and the image information of the target application from the first business platform. The system checks whether the obtained platform configuration parameters are different from the parameters of the last synchronization, such as network topology adjustments, resource allocation strategy changes, security updates, etc. Once a parameter change is detected, the system will store the changed configuration parameters in the platform configuration center for use when the disaster recovery environment is switched. The system also checks whether the target application image information has been updated, such as a new version of the code is released, the dependency library is upgraded, or the configuration file is adjusted. After confirming that the application image information has changed, the system will download and store the changed application image to the application image library so that the updated application service can be quickly deployed in the disaster recovery environment. Through the above process, banks can effectively control disaster recovery costs while ensuring business continuity. When business is operating normally, the disaster recovery environment (i.e., the second business platform) does not need to activate and run all application services. Instead, it automatically updates configuration parameters and application images at set time points to ensure that it can be quickly started when the main data center (i.e., the first business platform) fails, and use the latest system configuration and application versions to provide services, thereby reducing business interruption time and protecting user data security.

[0056] Through the above steps, when the monitoring results show that the first business platform is operating normally, the platform configuration parameters and application image information are synchronized regularly, and changes in parameters or image information are detected. If there are any changes, the changed data is updated to the platform configuration center and application image library, ensuring that the data in the platform configuration center and application image library are the latest, which is conducive to the instant synchronization and update of the second business platform, reducing additional problems caused by configuration differences when switching business platforms, and enhancing the effectiveness and adaptability of the second business platform (i.e., disaster recovery environment).

[0057] In an exemplary embodiment, before determining the business execution resources allocated to the above-mentioned target business from the above-mentioned second business platform according to the business execution requirements of the above-mentioned target business, the above-mentioned method also includes: obtaining the log file generated when the above-mentioned first business platform executes the above-mentioned target business; calculating the business weight of the above-mentioned target business based on the above-mentioned log file; and determining the above-mentioned business execution requirements based on the above-mentioned business weight.

[0058] Optionally, the log file in this embodiment is a record file generated by the first business platform during the execution of the target business, which contains detailed information during the business execution process, such as operation timestamps, execution details, error information, performance indicators, etc., and is an important data source for analyzing business behavior and system health.

[0059] Optionally, the business weight in this embodiment is a numerical value that measures the relative importance and busyness of the target business in its business platform, which can be used to optimize resource allocation and disaster recovery environment deployment strategies to ensure that key business priorities and performance requirements are met.

[0060] Optionally, the business execution requirements in this embodiment are a collection of resource types, quantities and configurations required to provide services for the target business in the second business platform (i.e., disaster recovery environment) determined based on the business weight and current business status, including CPU, memory, storage, network bandwidth, etc., as well as specific application service image versions and parameters.

[0061] For example, a large e-commerce company has a primary business platform responsible for handling all online transactions, inventory management, and other businesses. To cope with possible system failures and disasters, the company has designed a disaster recovery system. This system needs to dynamically adjust the resource allocation of the disaster recovery environment based on the real-time workload and importance of each target business on the primary business platform. This system is required to quickly take over and prioritize the continuity of critical businesses when the primary business platform fails. The company deploys log management tools (such as ELK Stack or Logstash) to continuously collect log files about target businesses on the main business platform, including transaction requests, inventory change records, etc., as well as monitoring logs of system performance and health status; log files are regularly analyzed to calculate the weight of each target business. The weight calculation can be based on factors such as the business's visits, transaction amount, consumption of system resources, and the importance of the business to the entire company's operations. For example, a machine learning model is used to analyze the request frequency and response time in the log, combined with the revenue contribution of the business, to derive the comprehensive weight value of each business; based on the calculated business weight, the company can determine the optimal resource allocation strategy for providing services to each target business in the disaster recovery environment. For example, for core transaction businesses with high weights, more CPU resources and faster storage devices may need to be allocated, while for non-core businesses with lower weights, resource allocation can be appropriately reduced to optimize the overall cost of the disaster recovery environment. Through the above process, e-commerce companies effectively control disaster recovery costs while ensuring business continuity and user experience. Resource allocation in the disaster recovery environment is no longer a one-size-fits-all model, but is dynamically adjusted according to the real-time weight of each business. When a disaster recovery switch occurs, the company can quickly recover and prioritize the operation of key businesses. At the same time, it avoids the cost waste caused by excessive investment in disaster recovery resources and maximizes resource utilization.

[0062] Through the above steps, the log files of the target business execution on the first business platform are obtained. The log files are then analyzed to calculate the business weight of the target business, which is then used to guide resource allocation on the second business platform. Log analysis provides a quantitative basis for business execution, helping to accurately determine the health of business execution. Dynamically adjusting business execution resources based on the business weight of the target business optimizes resource utilization on the second business platform (i.e., the disaster recovery environment) while meeting business needs.

[0063] In an exemplary embodiment, the business weight of the target business is calculated based on the log file, including: determining the number of exceptions, the target time, and the first usage rate when the processor in the first business platform reads the target business from the log file, wherein the number of exceptions is the number of exceptions that occur when the first business platform reads the target business within the target time; calculating the reading exception rate of the first business platform based on the number of exceptions and the target time; determining the health parameters of the first business platform based on the reading exception rate and the first usage rate, wherein the health parameters are parameters used to indicate whether the first business platform executes the target business normally within the target time; and determining the business weight using the health parameters.

[0064] Optionally, the number of exceptions in this embodiment is the number of failures, errors or abnormal behaviors that occur when the first business platform processes the target business within a specific monitoring time period, such as database connection failure, service unavailability, response timeout, etc.

[0065] Optionally, the target time in this embodiment is a time window defined by the system for counting abnormality times and performance indicators. This time window can be set dynamically to accurately analyze the system health status within a specific time period.

[0066] Optionally, the first usage rate in this embodiment refers to the usage rate of the first service platform when reading the target service.

[0067] Optionally, the calculation formula for the read exception rate in this embodiment is the number of exceptions / the total number of times the target business is read within the target time, which represents the probability of an exception occurring in the target business operation and is used to evaluate the stability and robustness of the business.

[0068] Optionally, the health parameter in this embodiment comprehensively reflects the first business platform's ability to execute the target business within the target time, and is usually calculated from multi-dimensional data such as reading exception rate and processor usage rate, and is used to judge the health status of the platform.

[0069] Optionally, the service weight in this embodiment is a numerical value determined based on factors such as health parameters, importance, and impact range of the service, and is used for priority sorting, resource allocation, and service recovery order in a disaster recovery environment.

[0070] Optionally, the health parameter in this embodiment may also use a second usage rate when calculating, wherein the second usage rate refers to a threshold value of an average usage rate of the processor of the second service platform within a target time.

[0071] Optionally, the health parameter in this embodiment can be calculated by the following formula: health parameter H = (1-α)*(1-reading anomaly rate)+α*(second usage rate-first usage rate), where α is the resource sensitivity coefficient. The value of the coefficient corresponding to the target business can be set according to the actual business execution situation. In the normal case, the coefficient takes a value between 0.2-0.6.

[0072] For example, an online financial services company's primary business platform is responsible for processing key financial transactions, including payments, transfers, and loan approvals. To ensure service quality and effectively manage disaster recovery resources, the company needs to dynamically monitor and quantitatively assess the health of the business platform to guide the formulation and adjustment of disaster recovery strategies. The company's log management system continuously collects log files generated by business platforms, such as payment service logs, database operation logs, and system performance monitoring logs. Within a target timeframe (e.g., the past hour), it filters and counts service anomaly records from the log files, such as payment operation failures and service response timeouts. Within the same target timeframe, it extracts processor utilization data from system monitoring logs, calculates the average utilization rate, and distinguishes between the overall processor utilization threshold for the second business platform (the second utilization rate) and the processor utilization rate for the first business platform when processing the target business (the first utilization rate). This is calculated by combining the number of anomalies in the log files with the total number of operations within the target timeframe to reflect the stability of the target business. Combining the read anomaly rate, the first utilization rate, and the second utilization rate, the company has developed a health parameter calculation model that comprehensively assesses the health of the business platform when executing the target business. For example, a combination of indicators such as a low read anomaly rate and a reasonable processor utilization rate indicates good business health. Based on the business health parameters, business weights can be adjusted to prioritize resource allocation in the disaster recovery environment for businesses with good health and high processing efficiency. Businesses that frequently experience anomalies require additional attention and optimization, and may be given a lower priority in disaster recovery resource allocation until the issues are resolved.

[0073] Through the above steps, relevant parameters such as the number of exceptions, target time, and CPU usage are extracted from the logs, the read exception rate is calculated, and the health parameters of the first business platform are determined in combination with the CPU usage. The business weights are then calculated based on the health parameters. By using a specific calculation formula to evaluate the execution of the business, the scientific nature and accuracy of the weight calculation are increased. At the same time, the inclusion of indicators such as CPU usage makes the weight calculation more comprehensive, reflecting the actual load and health status of business execution, and rationally planning the allocation of business execution resources. This ensures that when the first business platform encounters an emergency, the most valuable and stable business can be restored first, thereby minimizing the impact of business interruptions and improving the efficiency and effectiveness of disaster recovery switching.

[0074] In an exemplary embodiment, the business weight includes at least one of the following: a weight indicating the execution priority of the first business platform in executing the target business; and a weight indicating the execution requirement for the first business platform to execute the target business within the target time.

[0075] Optionally, the execution priority in this embodiment is the order of processing assigned according to the importance and urgency of the businesses when the first business platform processes multiple businesses. The execution priority determines which businesses should be executed first under limited system resources, and is usually closely related to factors such as the strategic value of the business to the enterprise, customer satisfaction, and financial impact.

[0076] Optionally, the execution priority in this embodiment can be determined by searching the execution priority corresponding to the target business in the hierarchical weight mapping table, where the hierarchical weight mapping table is set according to the actual execution situation of the business, for example: the execution priority corresponding to the transaction type of business is higher than the execution priority of the content browsing type of business.

[0077] Optionally, the execution demand weight in this embodiment represents a quantitative indicator of the resource demand intensity and importance of the first business platform executing the target business within a specific time period, including but not limited to calculations based on comprehensive factors such as historical data of the business (such as access frequency, data processing volume, system load) and potential impact of the business (such as revenue contribution, risk of service interruption).

[0078] Optionally, the execution demand weight in this embodiment can also be called a time period coefficient in actual use, allowing the weight to be automatically adjusted according to business needs and user behavior patterns in different time periods of the day, ensuring that critical services can be protected from excessive traffic impact during peak periods, while resources can be fully utilized during off-peak periods.

[0079] Optionally, the time period coefficient in this embodiment is used to represent the operational requirements, urgency, or time sensitivity of a business or service within a specific time period. During certain periods of the day, the business may experience traffic peaks, such as in the morning and afternoon on weekdays. The time period coefficient at this time can reflect the peak demand of the business, ensuring that during these periods, the target business can be preferentially executed by the second business platform and allocated more business execution resources. If the abnormal execution of the target business occurs during non-peak hours, a longer recovery window may be given to gradually restore the service. The time period coefficient can also be used to optimize the use of disaster recovery resources. For example, when it is predicted that business demand will drop significantly in the future, the reservation of business execution resources can be appropriately reduced to save costs. On the contrary, when it is predicted that business demand will increase, business execution resources can be increased in advance to ensure the continuity and stability of the service.

[0080] Optionally, the execution demand weight (i.e., time period coefficient) in this embodiment can be calculated in the following manner: T = basic weight + sin2(πt / 24)*peak amplitude, where the basic weight is a constant, representing the lowest level or default level of business execution demand within a day, t is a time variable, representing the current time point (accurate to the minute), and the peak amplitude is an adjustable parameter, representing the maximum difference in execution demand between peak and non-peak periods of the day.

[0081] Optionally, the service weights in this embodiment may also include a test phase index S when actually used, which is used to indicate the state or readiness of the second service platform (i.e., the disaster recovery environment) from the test phase to being ready to bear actual user traffic. The test phase index S reflects the stability and reliability of the disaster recovery environment after a series of tests, including but not limited to code synchronization testing, data consistency checking, network connectivity verification, application container pull-up and response time testing, and the health status of various components and services in the disaster recovery environment. When S reaches a predetermined threshold, it can be considered that the disaster recovery environment is mature and stable enough to safely and smoothly connect to the target business of the first service platform, provide services in a timely manner in the event of a failure, and ensure that business continuity and user experience are not affected.

[0082] Optionally, when the business weight includes the health parameter H, the execution priority P of the target business, the execution requirement weight T of the target business and the test phase index S, the business weight can be calculated in the following manner: W = (H × P × T) / (S + γ), where γ is the system protection constant to prevent the denominator from being zero.

[0083] For example, in a large-scale Internet medical service platform, the first business platform is responsible for handling diversified medical services ranging from online consultation, appointment registration to patient electronic medical record management. In order to optimize resource utilization, ensure the stability and response speed of key businesses, and quickly start the disaster recovery environment to restore services when a system failure occurs, the platform adopts a dynamic resource allocation strategy based on execution priority and execution demand weight. The platform's business management team assigns execution priority to each business based on the nature of the business, user needs and corporate strategic goals. For example, "online emergency consultation service" may be marked as the highest priority (priority level 10) because it is related to the patient's life safety and needs to be ensured to operate even when resources are tight. "Drug recommendation and advertising push" may be assigned a lower priority (priority level 2) because it can be temporarily shelved without causing serious impact on key services when system resources are limited or disaster recovery is switched. The business platform's operation and maintenance team calculates the execution requirements of each business within the target time (such as the peak visit period from 8 am to 10 am) through historical data analysis. The execution demand weight of each service is calculated based on metrics such as service access frequency, data throughput, and processor utilization, while also taking into account the importance of the service (such as its contribution to revenue). For example, during peak visit periods, the execution demand weight of "Online Emergency Consultation Service" may be as high as 95%, indicating that it has an extremely high demand for resources during this period. Due to its importance, it should be allocated sufficient resources even in the secondary service platform (i.e., the disaster recovery environment) to ensure service quality. The execution demand weight of "Drug Recommendation and Advertising Push" during this period may be 5%, reflecting that although it also has certain resource requirements, it should give way to more critical services in resource allocation. Through the above process, the Internet medical service platform can not only reasonably allocate resources in daily operations to ensure the efficient operation of key services, but also prioritize the startup and recovery of key services during disaster recovery switchover based on their importance and resource requirements, reducing the impact of disaster events on service continuity and user experience, maximizing the use of limited disaster recovery resources, and improving the effectiveness and flexibility of disaster recovery strategies.

[0084] Optionally, in this embodiment, before the second business platform is officially used to execute the target business, the second business platform will also be tested. First, the relevant parameters will be configured, and the time and frequency for starting the test of the second business platform, as well as the group of people who can directly access the second business platform, will be set; then the second business platform will be automatically started according to the settings, and the mirroring of each application generated on the second business platform will be automatically executed. The time and frequency can be configured, and the access group can also be automatically configured. The actual user access will be simulated for internal testers. After it stabilizes, the actual user group can be configured according to the weight according to actual needs to access the remote second business platform; the tester accesses the enterprise virtual private network (Virtual Private Network, referred to as VPN) through the program to connect to the internal network of the disaster recovery environment, and uses tools such as JMeter / LoadRunner to perform testing.

[0085] Through the above steps, it is determined that business weights can include execution priority and execution demand weight. The setting of execution priority helps to prioritize the normal operation of key businesses when resources are limited. The execution demand weight can guide the second business platform to reasonably allocate resources, helping enterprises with complex businesses and large fluctuations in resource demands to maintain the stability and continuity of core businesses in the face of uncertainties and challenges, avoid waste of resources, and improve the economic benefits of disaster recovery switching.

[0086] The above method is described below with a specific example. Figure 3 This is a flowchart of a method for executing a target business according to an embodiment of the present application. A financial services company is operating an online payment application that runs on a first business platform built within the company. One day, due to a network equipment failure in the data center, the first business platform cannot provide services normally, which will affect customers' online payment operations (i.e., the above-mentioned target business) and have a serious impact on the company's business. Figure 3 As shown, the target service is switched to the second service platform for execution through the following steps:

[0087] Step S302 , determining that an anomaly occurs when executing the target business on the first business platform: the company's monitoring system detects a network anomaly in the online payment application, triggering a disaster recovery switching mechanism;

[0088] Step S304: Obtaining platform configuration parameters from the platform configuration center and application image information of the target application from the application image library: The second service platform automatically obtains configuration parameters (current network configuration, security policy, and resource allocation parameters) from the platform configuration center and obtains the latest image information of the online payment application from the application image library;

[0089] Step S306: Using the acquired configuration parameters and image information, quickly configure the second business platform (e.g., a disaster recovery environment deployed in Tencent Cloud) to ensure that it can inherit the functions and configurations of the first business platform;

[0090] Step S308: Determine the business execution resources allocated to the target business from the second business platform based on the execution requirements of the target business. Determine the computing and storage resources, such as CPU, memory, and database services, allocated to the target business by the second business platform based on the concurrent processing capability of payment requests.

[0091] Step S310: Switch the target business to the second business platform for execution: the second business platform takes over and continues to execute the online payment application through the allocated business execution resources, ensuring that business continuity is not affected.

[0092] Through the above steps, through seamless connection with the first business platform, the second business platform can be quickly activated after detecting an anomaly, load the latest application image, configure the corresponding resources, and switch the target business. The entire process is automated and efficient, significantly reducing business interruption time. The company can regularly synchronize application images and configuration parameters to the application image library and platform configuration center respectively. The second business platform does not usually start application services, but only quickly configures and deploys based on the latest information obtained when problems occur on the first business platform, thereby achieving the goals of saving costs, ensuring data security, and improving business continuity. In this way, even in the face of sudden network failures or data center problems, the company can ensure that critical businesses are not affected and maintain normal operations.

[0093] It should be noted that, through the description of the above implementation methods, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus the necessary general hardware platform, and of course it can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for enabling a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods described in each embodiment of the present application.

[0094] This embodiment also provides a service execution device for implementing the above-mentioned embodiments and preferred implementations. Details already described will not be repeated here. As used below, the term "module" may refer to a combination of software and / or hardware that implements a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, implementation using hardware, or a combination of software and hardware, is also possible and contemplated.

[0095] Figure 4 This is a structural block diagram of a device for executing a service according to an embodiment of the present application. Figure 4 As shown, the device includes:

[0096] an acquisition module 42 configured to, when an exception occurs while executing a target service on the first service platform, acquire platform configuration parameters from the platform configuration center and acquire application image information of a target application from an application image library, wherein the target application is an application configured in the first service platform and used to execute the target service;

[0097] Configuration module 44, configured to configure the second service platform using the platform configuration parameters and the application image information;

[0098] A determination module 46 is configured to determine, from the second service platform, service execution resources allocated to the target service according to the service execution requirements of the target service;

[0099] The switching module 48 is configured to switch the target service to the second service platform, so as to execute the target service through the service execution resources in the second service platform.

[0100] In an exemplary embodiment, the above-mentioned device is also used to monitor the status of the above-mentioned first business platform executing the above-mentioned target business through a monitoring application before obtaining platform configuration parameters from the platform configuration center and obtaining application image information of the target application from the application image library when an abnormality occurs when the first business platform executes the target business, and obtain monitoring results; when it is determined from the above-mentioned monitoring results that the network of the above-mentioned first business platform is abnormal or the above-mentioned target application service is abnormal, it is determined that an abnormality occurs when the above-mentioned first business platform executes the above-mentioned target business.

[0101] In an exemplary embodiment, the above-mentioned device is also used to monitor the status of the above-mentioned first business platform executing the above-mentioned target business through a monitoring application. After obtaining the monitoring results, if it is determined from the above-mentioned monitoring results that the above-mentioned first business platform is executing the above-mentioned target business normally, the platform configuration parameters of the above-mentioned first business platform and the application image information of the above-mentioned target application are periodically obtained; if it is determined that the above-mentioned platform configuration parameters have changed, the changed platform configuration parameters of the above-mentioned first business platform are stored in the above-mentioned platform configuration center; if it is determined that the above-mentioned application image information has changed, the changed application image information of the above-mentioned target application is obtained, and the above-mentioned changed application image information is stored in the above-mentioned application image library.

[0102] In an exemplary embodiment, the above-mentioned device is also used to obtain the log file generated when the above-mentioned first business platform executes the above-mentioned target business before determining the business execution resources allocated to the above-mentioned target business from the above-mentioned second business platform according to the business execution requirements of the above-mentioned target business; calculate the business weight of the above-mentioned target business based on the above-mentioned log file; and determine the above-mentioned business execution requirements based on the above-mentioned business weight.

[0103] In an exemplary embodiment, the above-mentioned device is also used to determine the number of exceptions, the target time, and the first usage rate when the processor in the above-mentioned first business platform reads the above-mentioned target business from the above-mentioned log file, wherein the above-mentioned number of exceptions is the number of exceptions that occur when the above-mentioned first business platform reads the above-mentioned target business within the above-mentioned target time; the reading exception rate of the above-mentioned first business platform is calculated based on the above-mentioned number of exceptions and the above-mentioned target time; the health parameters of the above-mentioned first business platform are determined based on the above-mentioned reading exception rate and the above-mentioned first usage rate, wherein the above-mentioned health parameters are parameters used to indicate whether the above-mentioned first business platform executes the above-mentioned target business normally within the above-mentioned target time; the above-mentioned business weight is determined using the above-mentioned health parameters, wherein the above-mentioned business weight includes at least one of the following: used to indicate the execution priority of the above-mentioned first business platform to execute the above-mentioned target business; used to indicate the execution requirement weight of the above-mentioned first business platform to execute the above-mentioned target business within the above-mentioned target time.

[0104] It should be noted that the above modules can be implemented through software or hardware. For the latter, it can be implemented in the following ways, but not limited to: the above modules are all located in the same processor; or the above modules are located in different processors in any combination.

[0105] An embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored. The computer program is configured to execute the steps of any of the above method embodiments when run.

[0106] In an exemplary embodiment, the computer-readable storage medium may include, but is not limited to, various media that can store computer programs, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk, or an optical disk.

[0107] An embodiment of the present application further provides an electronic device, comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0108] In an exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor, and the input / output device is connected to the processor.

[0109] An embodiment of the present application further provides a computer program product, which includes a computer program. When the computer program is executed by a processor, the steps in any one of the above method embodiments are implemented.

[0110] An embodiment of the present application further provides another computer program product, comprising a non-volatile computer-readable storage medium, wherein the non-volatile computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of any of the above method embodiments are implemented.

[0111] An embodiment of the present application also provides a computer program, which includes computer instructions, which are stored in a computer-readable storage medium; a processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device performs the steps of any of the above method embodiments.

[0112] For specific examples in this embodiment, reference may be made to the examples described in the above embodiments and exemplary implementation modes, and this embodiment will not be described in detail here.

[0113] Obviously, those skilled in the art should understand that the modules or steps of the present application described above can be implemented using a general-purpose computing device, they can be concentrated on a single computing device, or distributed across a network composed of multiple computing devices, they can be implemented using program code executable by the computing device, and thus, they can be stored in a storage device and executed by the computing device, and in some cases, the steps shown or described can be performed in a different order than herein, or they can be fabricated into separate integrated circuit modules, or multiple modules or steps can be fabricated into a single integrated circuit module for implementation. Thus, the present application is not limited to any specific combination of hardware and software.

[0114] The above description is merely a preferred embodiment of the present application and is not intended to limit the present application. Various modifications and variations are possible for those skilled in the art. Any modifications, equivalent substitutions, improvements, etc. made within the principles of the present application shall be included within the scope of protection of the present application.

Claims

1. A method for executing a business, characterized in that: include: When an exception occurs when the first service platform executes the target service, obtaining platform configuration parameters from the platform configuration center and obtaining application image information of a target application from an application image library, wherein the target application is an application set in the first service platform and used to execute the target service; Configuring a second service platform using the platform configuration parameters and the application image information; Determining, from the second service platform, service execution resources allocated to the target service according to service execution requirements of the target service; The target service is switched to the second service platform, so as to execute the target service in the second service platform through the service execution resources.

2. The method according to claim 1, characterized in that When an exception occurs when the first service platform executes the target service, before obtaining the platform configuration parameters from the platform configuration center and obtaining the application image information of the target application from the application image library, the method further includes: monitoring the state of the first service platform executing the target service through a monitoring application to obtain a monitoring result; When it is determined from the monitoring result that the network of the first service platform is abnormal or the target application service is abnormal, it is determined that an abnormality occurs when the first service platform executes the target service.

3. The method according to claim 2, characterized in that After monitoring the state of the target service being executed by the first service platform through a monitoring application and obtaining a monitoring result, the method further includes: When it is determined from the monitoring result that the first service platform is executing the target service normally, periodically obtaining platform configuration parameters of the first service platform and application image information of the target application; When it is determined that the platform configuration parameters have changed, storing the changed platform configuration parameters of the first service platform in the platform configuration center; When it is determined that the application image information has changed, the changed application image information of the target application is obtained, and the changed application image information is stored in the application image library.

4. The method according to claim 1, wherein Before determining, from the second service platform, the service execution resources allocated to the target service according to the service execution requirements of the target service, the method further includes: Obtaining a log file generated when the first service platform executes the target service; Calculating a service weight of the target service based on the log file; The service execution requirement is determined based on the service weight.

5. The method according to claim 4, characterized in that Calculating the service weight of the target service based on the log file includes: Determining, from the log file, the number of exceptions, the target time, and a first usage rate of a processor in the first service platform when reading the target service, wherein the number of exceptions is the number of exceptions that occur when the first service platform reads the target service within the target time; Calculating a read exception rate of the first service platform based on the number of exceptions and the target time; determining a health parameter of the first service platform based on the read exception rate and the first usage rate, wherein the health parameter is a parameter used to indicate whether the first service platform normally performs the target service within the target time; The service weight is determined using the health parameter.

6. The method according to claim 5, characterized in that The service weight includes at least one of the following: Used to indicate the execution priority of the first service platform in executing the target service; Used to represent the execution requirement weight of the first service platform to execute the target service within the target time.

7. A service execution device, characterized in that: include: an acquisition module, configured to, when an exception occurs when the first service platform executes a target service, acquire platform configuration parameters from the platform configuration center and acquire application image information of a target application from an application image library, wherein the target application is an application set in the first service platform and used to execute the target service; A configuration module, configured to configure a second service platform using the platform configuration parameters and the application image information; a determination module, configured to determine, from the second service platform, service execution resources allocated to the target service according to service execution requirements of the target service; A switching module is used to switch the target service to the second service platform, so as to execute the target service through the service execution resources in the second service platform.

8. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

9. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, wherein the computer program implements the steps of the method described in any one of claims 1 to 6 when executed by a processor.

10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

Images