Business processing method and apparatus, computer device, and storage medium

Abstract

The application relates to a service processing method and device, computer equipment, a storage medium and a computer program product, and relates to the technical field of cloud computing. The method comprises the following steps: when a service degradation operation is triggered, determining first target services from a plurality of services, and performing degradation processing on the first target services; monitoring the load condition of an operation and maintenance item, and in the case that the load condition of the operation and maintenance item is less than a load threshold, determining a to-be-restored service from the first target services, performing service restoration processing on the to-be-restored service, and adding the to-be-restored service to a degradation stack; in the case that the load condition of the operation and maintenance item is greater than or equal to the load threshold, determining a second target service from the to-be-restored services according to the stacking order of the to-be-restored services in the degradation stack, and performing degradation processing on the second target service. The method can achieve the effect of self-adaptive adjustment of service degradation and service restoration, does not require manual operation, and improves the efficiency of service processing.

Description

Technical Field

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

[0002] With the development of cloud computing technology, servers are able to perform service degradation based on the current service load.

[0003] In the current technical implementation of service degradation, performance testing can be conducted on each service to determine the services to be degraded based on their performance requirements and capacity. During peak traffic periods, technical personnel determine whether the services to be degraded can be degraded. If degradability is possible, technical personnel or the contingency plan platform will perform the degradation operation on the services to be degraded some time before the peak traffic period.

[0004] However, since the current business degradation method relies on prior performance testing to determine the degradation items, discrepancies between test results and actual traffic can affect the correctness of the degradation strategy. To ensure the correctness of the strategy, developers need to make adjustments based on the actual situation, leading to low efficiency in degradation operations, a higher risk of errors, and ultimately, system instability. Summary of the Invention

[0005] Therefore, it is necessary to provide a business processing method, apparatus, computer equipment, computer-readable storage medium, and computer program product that can improve the efficiency of business degradation processing in response to the above-mentioned technical problems.

[0006] Firstly, this application provides a business processing method. The method includes:

[0007] When a service degradation operation is triggered, a first target service is determined from multiple services, and each of the first target services is degraded.

[0008] Monitor the load of the operation and maintenance items. If the load of the operation and maintenance items is less than the load threshold, determine the service to be restored from each of the first target services according to the degradation priority, perform service restoration processing on the service to be restored, and add the service to be restored to the degradation stack after the service restoration processing is completed.

[0009] Monitor the load status of the maintenance item. If the load status of the maintenance item is greater than or equal to the load threshold, determine the second target service from the services to be restored according to the stacking order of the services to be restored in the degradation stack, and perform degradation processing on the second target service.

[0010] In one embodiment, the degradation processing of each of the first target services includes:

[0011] Set the switch status of the dynamic degradation switch corresponding to each of the first target services to the on state;

[0012] The process of restoring the service to be restored includes:

[0013] Set the switch of the dynamic degradation switch corresponding to the service to be restored to the off state, and perform restoration processing on the service to be restored.

[0014] In one embodiment, the service recovery process for the service to be restored includes:

[0015] Based on the gradient recovery strategy, determine the request hit status of the service to be recovered;

[0016] Based on the success rate of the requests for the services to be restored, the services to be restored are restored.

[0017] In one embodiment, determining the request hit status of the service to be restored according to the gradient recovery strategy includes:

[0018] Obtain the user request for the service to be restored, wherein the user request carries a user feature identifier;

[0019] For any of the user requests, the feature value corresponding to the user request is determined based on the user feature identifier carried in the user request;

[0020] According to the gradient recovery strategy, the proportion of each recovery gradient is determined, and the proportion of the recovery gradient is in an increasing state;

[0021] Based on the feature values ​​corresponding to each user request and the recovery gradient ratio, the hit rate of the service to be restored for each recovery gradient ratio is determined.

[0022] In one embodiment, the step of restoring the service to be restored based on the request hit status of the service to be restored includes:

[0023] Determine the first recovery gradient ratio from each of the described recovery gradient ratios;

[0024] The service to be restored is restored according to the first recovery gradient ratio. After the service to be restored is restored, if the load of the operation and maintenance item is less than the load threshold, a second recovery gradient ratio is determined from each of the recovery gradient ratios. The second recovery gradient ratio is adjacent to the first recovery gradient ratio and is greater than the first recovery gradient ratio.

[0025] The second recovery gradient ratio is used as the first recovery gradient ratio, and the process jumps to the step of restoring the service to be restored according to the first recovery gradient ratio until the second recovery gradient ratio no longer exists, and then it is determined that the service to be restored has been restored.

[0026] In one embodiment, determining the second target service from the services to be restored according to the stacking order of the services to be restored in the degradation stack includes:

[0027] For each service to be restored in the degradation stack, the pop order of each service to be restored in the degradation stack is determined according to the last-in-first-out strategy;

[0028] Based on the pop order of each service to be restored in the downgrade stack, the second target service is determined from each service to be restored.

[0029] In one embodiment, when the load of the maintenance item is less than the load threshold, determining the service to be restored from each of the first target services according to the degradation priority includes:

[0030] If the load of the maintenance item is less than the load threshold, determine the difference between the load of the maintenance item and the load threshold;

[0031] Determine the range of the difference between the load status of the maintenance item and the load threshold;

[0032] Obtain the target number of services to be restored corresponding to the range of differences;

[0033] Based on the downgrade priority, the target number of services to be restored are determined from each of the first target services.

[0034] In one embodiment, the number of maintenance items is multiple, and monitoring the load of the maintenance items includes:

[0035] Obtain the real-time load status of each of the aforementioned operation and maintenance items;

[0036] The highest real-time load among all the described real-time load conditions is taken as the load condition of the operation and maintenance item.

[0037] Secondly, this application also provides a business processing apparatus. The apparatus includes:

[0038] The first degradation module is used to determine the first target service from multiple services when a service degradation operation is triggered, and to perform degradation processing on each of the first target services.

[0039] The recovery module is used to monitor the load status of the operation and maintenance items. When the load status of the operation and maintenance items is less than the load threshold, the module determines the service to be recovered from each of the first target services according to the degradation priority, performs service recovery processing on the service to be recovered, and adds the service to be recovered to the degradation stack after the service recovery processing is completed.

[0040] The second degradation module is used to monitor the load status of the operation and maintenance item. If the load status of the operation and maintenance item is greater than or equal to the load threshold, the module determines the second target service from the services to be restored according to the stacking order of the services to be restored in the degradation stack, and performs degradation processing on the second target service.

[0041] In one embodiment, the first degradation module is specifically used for:

[0042] Set the switch status of the dynamic degradation switch corresponding to each of the first target services to the on state;

[0043] The process of restoring the service to be restored includes:

[0044] Set the switch of the dynamic degradation switch corresponding to the service to be restored to the off state, and perform restoration processing on the service to be restored.

[0045] In one embodiment, the recovery module is specifically used for:

[0046] Based on the gradient recovery strategy, determine the request hit status of the service to be recovered;

[0047] Based on the success rate of the requests for the services to be restored, the services to be restored are restored.

[0048] In one embodiment, the recovery module is specifically used for:

[0049] Obtain the user request for the service to be restored, wherein the user request carries a user feature identifier;

[0050] For any of the user requests, the feature value corresponding to the user request is determined based on the user feature identifier carried in the user request;

[0051] According to the gradient recovery strategy, the proportion of each recovery gradient is determined, and the proportion of the recovery gradient is in an increasing state;

[0052] Based on the feature values ​​corresponding to each user request and the recovery gradient ratio, the hit rate of the service to be restored for each recovery gradient ratio is determined.

[0053] In one embodiment, the recovery module is specifically used for:

[0054] Determine the first recovery gradient ratio from each of the described recovery gradient ratios;

[0055] The service to be restored is restored according to the first recovery gradient ratio. After the service to be restored is restored, if the load of the operation and maintenance item is less than the load threshold, a second recovery gradient ratio is determined from each of the recovery gradient ratios. The second recovery gradient ratio is adjacent to the first recovery gradient ratio and is greater than the first recovery gradient ratio.

[0056] The second recovery gradient ratio is used as the first recovery gradient ratio, and the process jumps to the step of restoring the service to be restored according to the first recovery gradient ratio until the second recovery gradient ratio no longer exists, and then it is determined that the service to be restored has been restored.

[0057] In one embodiment, the second degradation module is specifically used for:

[0058] For each service to be restored in the degradation stack, the pop order of each service to be restored in the degradation stack is determined according to the last-in-first-out strategy;

[0059] Based on the pop order of each service to be restored in the downgrade stack, the second target service is determined from each service to be restored.

[0060] In one embodiment, the recovery module is specifically used for:

[0061] If the load of the maintenance item is less than the load threshold, determine the difference between the load of the maintenance item and the load threshold;

[0062] Determine the range of the difference between the load status of the maintenance item and the load threshold;

[0063] Obtain the target number of services to be restored corresponding to the range of differences;

[0064] Based on the downgrade priority, the target number of services to be restored are determined from each of the first target services.

[0065] In one embodiment, the recovery module is specifically used for:

[0066] Obtain the real-time load status of each of the aforementioned operation and maintenance items;

[0067] The highest real-time load among all the described real-time load conditions is taken as the load condition of the operation and maintenance item.

[0068] Thirdly, this application also provides a computer device. The computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to perform the following steps:

[0069] When a service degradation operation is triggered, a first target service is determined from multiple services, and each of the first target services is degraded.

[0070] Monitor the load of the operation and maintenance items. If the load of the operation and maintenance items is less than the load threshold, determine the service to be restored from each of the first target services according to the degradation priority, perform service restoration processing on the service to be restored, and add the service to be restored to the degradation stack after the service restoration processing is completed.

[0071] Monitor the load status of the maintenance item. If the load status of the maintenance item is greater than or equal to the load threshold, determine the second target service from the services to be restored according to the stacking order of the services to be restored in the degradation stack, and perform degradation processing on the second target service.

[0072] Fourthly, this application also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program thereon, which, when executed by a processor, performs the following steps:

[0073] When a service degradation operation is triggered, a first target service is determined from multiple services, and each of the first target services is degraded.

[0074] Monitor the load of the operation and maintenance items. If the load of the operation and maintenance items is less than the load threshold, determine the service to be restored from each of the first target services according to the degradation priority, perform service restoration processing on the service to be restored, and add the service to be restored to the degradation stack after the service restoration processing is completed.

[0075] Monitor the load status of the maintenance item. If the load status of the maintenance item is greater than or equal to the load threshold, determine the second target service from the services to be restored according to the stacking order of the services to be restored in the degradation stack, and perform degradation processing on the second target service.

[0076] Fifthly, this application also provides a computer program product. The computer program product includes a computer program that, when executed by a processor, performs the following steps:

[0077] When a service degradation operation is triggered, a first target service is determined from multiple services, and each of the first target services is degraded.

[0078] Monitor the load of the operation and maintenance items. If the load of the operation and maintenance items is less than the load threshold, determine the service to be restored from each of the first target services according to the degradation priority, perform service restoration processing on the service to be restored, and add the service to be restored to the degradation stack after the service restoration processing is completed.

[0079] Monitor the load status of the maintenance item. If the load status of the maintenance item is greater than or equal to the load threshold, determine the second target service from the services to be restored according to the stacking order of the services to be restored in the degradation stack, and perform degradation processing on the second target service.

[0080] The aforementioned business processing method, apparatus, computer equipment, storage medium, and computer program product, upon triggering a business degradation operation, determine a first target business from multiple businesses and perform degradation processing on each of the first target businesses; monitor the load of maintenance items, and if the load of the maintenance items is less than a load threshold, determine a business to be restored from each of the first target businesses according to degradation priority, perform business restoration processing on the business to be restored, and add the business to be restored to a degradation stack after the business restoration processing is completed; monitor the load of the maintenance items, and if the load of the maintenance items is greater than or equal to the load threshold, determine a second target business from each of the businesses to be restored according to the stacking order of the businesses to be restored in the degradation stack, and perform degradation processing on the second target business. Because the load of maintenance items is continuously monitored, the degradation processing of businesses and the restoration processing of businesses to be restored are dynamically implemented based on the load of the maintenance items. This achieves the effect of adaptive adjustment of business degradation and business restoration, and requires no manual operation, reducing the risk of system instability due to human error and improving the efficiency of business processing. Attached Figure Description

[0081] Figure 1 This is a flowchart illustrating a business processing method in one embodiment;

[0082] Figure 2 This is a schematic diagram of the process of downgrading a first target service and restoring a service to be restored in one embodiment.

[0083] Figure 3 This is a schematic diagram of the process for restoring services to be restored in one embodiment;

[0084] Figure 4 This is a flowchart illustrating the process of determining the request hit rate for each recovery gradient ratio of the service to be restored in one embodiment.

[0085] Figure 5 This is a schematic diagram illustrating the process of determining the recovery of a service to be restored in one embodiment;

[0086] Figure 6 This is a schematic diagram of the process for determining a second target service from various services to be restored in one embodiment;

[0087] Figure 7 This is a schematic diagram of a process for determining a target number of services to be restored from each first target service in one embodiment;

[0088] Figure 8 This is a flowchart illustrating the process of determining the load status of an operation and maintenance item in one embodiment;

[0089] Figure 9 This is a flowchart illustrating an example of the service degradation processing procedure in one embodiment;

[0090] Figure 10 This is a schematic diagram of the modules that implement various functions in the server that handles service degradation in one embodiment.

[0091] Figure 11 This is a flowchart illustrating the process of determining the request hit status of a service to be restored based on a gradient recovery strategy and user requests for the service to be restored, in one embodiment.

[0092] Figure 12 This is a schematic diagram of the process for determining the next service to be restored in one embodiment;

[0093] Figure 13 This is a structural block diagram of a service processing device in one embodiment;

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

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

[0096] In one embodiment, such as Figure 1 As shown, a business processing method is provided. This embodiment illustrates the method by applying it to a server. It is understood that this method can be applied to any server in a server cluster, or to the entire server cluster. In this embodiment, the method includes the following steps:

[0097] Step 102: When a service degradation operation is triggered, determine the first target service from multiple services and perform degradation processing on each first target service.

[0098] The application service can include multiple services, each of which can be processed by one or more servers handling user requests. Each service has its own corresponding degradation flag. Service degradation refers to disabling less important service functions through switch configuration, freeing up resources for more important services, thereby improving the server's processing capacity for more important services and ensuring stable system operation during peak traffic periods. Service degradation operations can be triggered based on a preset degradation time or in response to degradation commands from technical personnel; this application does not specify a particular trigger.

[0099] In this embodiment, the server may pre-store degradation identifiers for each service. When a service degradation operation is triggered, the server determines a first target service from among multiple services based on the degradation identifiers of each service. Then, the server performs degradation processing on each first target service.

[0100] The degradation identifier can be a numeric identifier or a character identifier; this application does not specifically limit the type of degradation identifier. The degradation identifier is used to indicate that a service is to be downgraded. The server can determine the first target service (the service to be downgraded) based on the degradation identifier. The degradation identifier for each service can be determined based on the performance usage of each service obtained through performance testing by technical personnel before the downgrade operation. This application does not specifically limit the method for determining the degradation identifier for each service.

[0101] For example, before a service degradation operation is triggered, the server assigns a degradation identifier to each degraded service. The server can deploy a scheduler (a scheduling triggering component, usually a component with timed triggering function) based on the open-source project Quartz (a task scheduling framework implemented in Java). When a degradation operation is triggered, for example, 0.5 hours before a traffic peak, the scheduler uses the degradation identifier of each service to determine multiple first target services among multiple services and performs degradation processing on the first target services.

[0102] For open-source projects, AZKBAN (a batch workflow task scheduler implemented in Java) and elastic-job-lite (a scheduled task framework) can also be used. This application embodiment does not make specific limitations on this.

[0103] Step 104: Monitor the load of the operation and maintenance items. If the load of the operation and maintenance items is less than the load threshold, determine the service to be restored from each first target service according to the degradation priority, perform service restoration processing on the service to be restored, and add the service to be restored to the degradation stack after the service restoration processing is completed.

[0104] The operation and maintenance items refer to the operation and maintenance service information of the application services. The load threshold can be preset based on the load of the application services or calculated based on the load occupancy of each service; this application does not limit the method for determining the load threshold. Degradation priority is used to record the recovery priority of each degraded service or the degradation priority of each service. The stack is a linear list that allows insertion or deletion operations only at one end. The degradation stack is used to store the service identifiers of the services to be restored. The service identifier can be a service name or a service ID; this application does not specifically limit this.

[0105] In this embodiment, the server can obtain the load status of the application service's operation and maintenance items through a load status acquisition interface. For example, the server can obtain the load status of the operation and maintenance items through load status interfaces provided by operation and maintenance platforms, such as those provided by open-source projects like disconf (Distributed Configuration Management Platform), XDiamond (open-source global configuration center), Apollo (Apollo open-source configuration management center), Qconf (distributed configuration management tool), and Spring Cloud Config (unified configuration center server and client).

[0106] Then, the server can pre-store degradation priority information, such as a degradation priority table. The server continuously monitors the load of the maintenance items. When the load of the maintenance items is less than the load threshold, it sequentially determines the services to be restored from each first target service according to the degradation priority and performs service restoration processing on the services to be restored. After the service to be restored completes the service restoration processing, the server can receive a service restoration completion identifier returned by the service to be restored. Then, after receiving the service restoration completion identifier returned by the service to be restored, the server adds the service identifier of the service to be restored to the degradation stack.

[0107] For example, the first target services (i.e., the downgraded services) are services A, B, and C, with a downgrade priority of service A > service B > service C. The server continuously monitors the load of the maintenance items. If the load of the maintenance items is less than the load threshold, service C in the first target services is selected as the service to be restored, according to the downgrade priority of service A > service B > service C. The server performs service restoration processing on service C, and after the service restoration processing of service C is completed, service C is added to the downgrade stack.

[0108] Understandably, the higher the downgrade priority of a business, the lower its importance, and the later the business can be restored.

[0109] Step 106: Monitor the load of the operation and maintenance items. If the load of the operation and maintenance items is greater than or equal to the load threshold, determine the second target service from the services to be restored according to the stacking order of each service to be restored in the degradation stack, and perform degradation processing on the second target service.

[0110] Among them, if the load of the operation and maintenance item is greater than or equal to the load threshold, it can indicate that the server cluster where the server is located is under heavy load. Therefore, it is necessary to further degrade the service to be restored in order to release service resources and thus enable the service cluster to have more service resources.

[0111] In this embodiment, the server monitors the load of the maintenance item. When the load of the maintenance item is greater than or equal to the load threshold, the server determines the push order of each service to be restored in the degradation stack according to the degradation stack corresponding to the service to be restored. The server then determines the second target service from the services to be restored according to the push order of each service to be restored and performs degradation processing on the second target service.

[0112] In the above business processing method, when a business degradation operation is triggered, a first target business is determined from multiple businesses, and degradation processing is performed on each first target business. The load of the operation and maintenance items is monitored. If the load of the operation and maintenance items is less than the load threshold, businesses to be restored are determined from the first target businesses according to the degradation priority. Business restoration processing is performed on these businesses, and after the restoration processing is completed, they are added to the degradation stack. The load of the operation and maintenance items is monitored again. If the load of the operation and maintenance items is greater than or equal to the load threshold, a second target business is determined from the businesses to be restored according to the stacking order of the businesses to be restored in the degradation stack, and degradation processing is performed on the second target business. Because this solution can continuously monitor the load of the operation and maintenance items based on the pre-defined degradation priority, it dynamically implements business degradation processing and business restoration processing based on the load of the operation and maintenance items. This achieves the effect of adaptive adjustment of business degradation and business restoration, and requires no manual operation, reducing the risk of system instability caused by human error and improving the efficiency of business processing.

[0113] In one embodiment, such as Figure 2 As shown, step 102 includes:

[0114] Step 202: Set the on / off state of the dynamic degradation switch corresponding to each first target service to the on state.

[0115] Each service can be configured with a dynamic degradation switch. The dynamic degradation switch has two states: on and off. The application logic of each service can be divided into main application logic and dynamic degradation switch request logic. When the dynamic degradation switch of a service is on, the corresponding main application logic processing of that service is skipped, thereby achieving the degradation effect.

[0116] In this embodiment of the application, after the server determines each first target service, since the first target service is a service to be downgraded, the server can set the switch state of the dynamic downgrade switch corresponding to each first target service to the on state.

[0117] For example, the server can generate a degradation configuration item containing the dynamic degradation switch being enabled, based on the on state of the dynamic degradation switch corresponding to each first target service. Then, the server sends the degradation configuration item to the dynamic degradation switch request logic of each first target service through the disconf interface, and sets the on state of the dynamic degradation switch in the dynamic degradation switch request logic of each first target service to be enabled.

[0118] Step 104 includes:

[0119] Step 204: Set the switch status of the dynamic degradation switch corresponding to the service to be restored to the off state, and perform restoration processing on the service to be restored.

[0120] In this embodiment of the application, after the server determines the service to be restored, since the service to be restored needs to be restored, the server sets the switch status of the dynamic degradation switch corresponding to the service to be restored to the off state.

[0121] For example, the server can generate a degradation configuration item containing the dynamic degradation switch being in a closed state, based on the fact that the dynamic degradation switch corresponding to the service to be restored is in a closed state. Then, the server sends the degradation configuration item to the dynamic degradation switch request logic of the service to be restored through the disconf interface, and sets the dynamic degradation switch in the dynamic degradation switch request logic of the service to be restored to a closed state.

[0122] In this embodiment, the server can automatically perform service degradation and recovery processing by setting the switch of the dynamic degradation switch corresponding to each first target service to the on state and setting the switch of the dynamic degradation switch corresponding to the service to be recovered to the off state according to the load of the operation and maintenance items, thereby improving the efficiency of service degradation and recovery processing.

[0123] In one embodiment, such as Figure 3 As shown, step 104 includes:

[0124] Step 302: Determine the request hit status of the service to be restored according to the gradient recovery strategy.

[0125] The gradient recovery strategy instructs each service to be restored to respond to user requests according to a preset gradient ratio. A user request is a request sent by a user to the server for a service to be restored when the user uses that service.

[0126] In this embodiment, after setting the dynamic degradation switch of the service to be restored to the off state, the server obtains a pre-stored gradient recovery strategy and receives user requests for the service to be restored. Then, the server determines the success rate of the requests for the service to be restored based on the gradient recovery strategy.

[0127] User requests can be resource requests sent by users through their terminals. Examples include order quantity query requests and username modification requests. This application does not specifically limit the method or device used to send user requests. A request hit indicates that a user request has been selected, and the server can process and respond to such user requests.

[0128] Step 304: Based on the hit rate of the requests for the services to be restored, perform restoration processing on the services to be restored.

[0129] In this embodiment of the application, after the server sets the dynamic degradation switch of the service to be restored to the off state, it performs gradient restoration processing on the service to be restored according to the request hit status of the service to be restored, for example, responding to the hit user requests.

[0130] In this embodiment, the server can determine the recovery ratio of requests for services to be restored through a gradient recovery strategy during service recovery processing, and then gradually restore the services to be restored according to the recovery ratio. This can fully consider the load of operation and maintenance items, realize the gradual restoration of services to be restored, and ensure the high availability of the server.

[0131] In one embodiment, such as Figure 4 As shown, step 302 includes:

[0132] Step 402: Obtain user requests for services to be restored.

[0133] The user request includes a user identifier. This user identifier may include at least one of the user's user ID (identity document) or the user's terminal's device ID.

[0134] In this embodiment of the application, the server receives user requests corresponding to the service to be restored. For example, the server can receive multiple user requests for the service to be restored, D, sent by multiple users on their respective user terminals.

[0135] Step 404: For any user request, determine the feature value corresponding to the user request based on the user feature identifier carried in the user request.

[0136] In this embodiment of the application, for any user request, the terminal calculates the feature value of the user feature identifier carried in the user request according to the feature value calculation algorithm, thereby obtaining the feature value corresponding to the user request.

[0137] For the feature value calculation algorithm, hash algorithms can be used, such as MD5 (Message-Digest Algorithm 5), SHA-1 (Secure Hash Algorithm 1), and RipeMD-160 (a 60-bit cryptographic hash function). The feature value and the feature value calculation algorithm can be selected by those skilled in the art in practical applications. Any method capable of implementing feature value calculation is used in this application, and the embodiments of this application do not impose specific limitations on this.

[0138] Step 406: Determine the proportion of each recovery gradient according to the gradient recovery strategy.

[0139] Among them, the proportion of restored gradients is increasing.

[0140] In this embodiment, the server determines the proportion of each recovery gradient according to the gradient recovery strategy. Specifically, the server obtains a pre-set initial gradient proportion and a pre-set incremental gradient proportion, and determines multiple recovery gradient proportions based on the initial gradient proportion and the incremental gradient proportion.

[0141] For example, the server pre-sets the initial gradient ratio to 0, the pre-set incremental gradient ratio to 10%, and the server determines multiple recovery gradient ratios of 10%, 20%, 30%, ..., 100%.

[0142] Step 408: Based on the feature values ​​corresponding to each user request and the recovery gradient ratio, determine the hit rate of the requests for each recovery gradient ratio for the service to be restored.

[0143] For example, the server performs modulo calculation on the feature values ​​corresponding to each user request to obtain the target feature value of each user request. Based on the target feature value and the recovery gradient ratio, the server determines the request hit rate of the service to be restored for each recovery gradient ratio.

[0144] For example, the server obtains the hash value corresponding to each user request, performs modulo calculation on the feature value corresponding to each user request, and obtains the target feature value of each user request. Then, for each recovery gradient ratio, the server determines the target feature value that is greater than the recovery gradient ratio, and the user requests that have the target feature value greater than the recovery gradient ratio are taken as the user requests that have been matched.

[0145] In this embodiment, the server can compare and process the target feature values ​​corresponding to user requests based on multiple recovery gradient ratios, thereby determining the hit status of user requests and responding to user requests that have hit the hit status. This avoids a sudden increase in the load on maintenance items and server crashes during the recovery process of services to be restored due to the direct and complete restoration of services, thus improving the high availability of the server.

[0146] In one embodiment, such as Figure 5 As shown, step 304 includes:

[0147] Step 502: Determine the first recovery gradient ratio from the recovery gradient ratios.

[0148] In this embodiment, the server determines a first recovery gradient ratio from multiple recovery gradient ratios. Specifically, the server selects the smallest recovery gradient ratio from the multiple recovery gradient ratios as the first recovery gradient ratio.

[0149] Step 504: Perform recovery processing on the service to be recovered according to the first recovery gradient ratio. After the service to be recovered is recovered, if the load of the operation and maintenance item is less than the load threshold, determine the second recovery gradient ratio from each recovery gradient ratio.

[0150] The second recovery gradient ratio is adjacent to the first recovery gradient ratio, and the second recovery gradient ratio is greater than the first recovery gradient ratio.

[0151] In this embodiment, the server performs recovery processing on the service to be recovered according to a first recovery gradient ratio. Specifically, the server responds to user requests corresponding to the first recovery gradient ratio of the service to be recovered.

[0152] After the server processes the services to be restored according to the first recovery gradient ratio, it waits for a preset adjustment time. After the preset adjustment time, it obtains the load status of the maintenance items and determines whether the load status of the maintenance items is less than the load threshold. If the load status of the maintenance items is less than the load threshold, the server determines a second recovery gradient ratio from among the recovery gradient ratios. Specifically, when the load status of the maintenance items is less than the load threshold, the server determines the recovery gradient ratio that is adjacent to the first recovery gradient ratio and is greater than the first recovery gradient ratio as the second recovery gradient ratio.

[0153] For example, the initial gradient ratio is preset to 0, the incremental gradient ratio is preset to 10%, and the server determines multiple recovery gradient ratios of 10%, 20%, 30%, ..., 100%. Then, the server uses 10% as the first recovery gradient ratio and performs recovery processing on the service to be recovered according to the 10% recovery gradient ratio. After performing recovery processing on the service to be recovered according to the 10% recovery gradient ratio, it waits for a preset adjustment time, such as 5 seconds. After 5 seconds, it obtains the load status of the operation and maintenance item and determines whether the load status of the operation and maintenance item is less than the load threshold. If the load status of the operation and maintenance item is less than the load threshold, 20% is determined from the recovery gradient ratios as the second recovery gradient ratio.

[0154] Understandably, when the server's load on maintenance items is greater than or equal to the load threshold, it indicates that the server is experiencing excessive load while attempting to restore the services to be restored. To prevent server crashes, the server can cancel the restoration process for the services to be restored and set the dynamic degradation switch for those services to the "on" state. For example... Figure 12 As shown, the server can determine the next service to be restored based on the downgrade priority, and perform gradient recovery processing steps on the next service to be restored until there are no services to be restored in the first target service.

[0155] The process of performing gradient recovery on the services to be restored has been described in the aforementioned embodiments and will not be repeated here.

[0156] Step 506: Use the second recovery gradient ratio as the first recovery gradient ratio, and jump to the step of processing the service to be restored according to the first recovery gradient ratio until there is no second recovery gradient ratio, and determine that the service to be restored has been restored.

[0157] In this embodiment, the server deletes the first recovery gradient ratio and uses the second recovery gradient ratio as the first recovery gradient ratio. Then, the server performs the step of determining the second recovery gradient ratio from each recovery gradient ratio after the service to be restored has been restored, if the load of the maintenance item is less than the load threshold, until there is no second recovery gradient ratio, and then determines that the service to be restored has been completely restored.

[0158] In this embodiment, the server sequentially determines the first recovery gradient ratio among the various recovery gradient ratios until the recovery of the service to be recovered is completed, thereby realizing the gradient recovery processing of the service to be recovered and improving the high availability of the server.

[0159] In one embodiment, such as Figure 6 As shown, step 106 includes:

[0160] Step 602: For each service to be restored in the degradation stack, determine the pop order of each service to be restored in the degradation stack according to the last-in-first-out strategy.

[0161] The Last-In-First-Out (LIFO) strategy is used to characterize the order in which data is popped from the stack, meaning that the data that enters the stack first is popped last.

[0162] In this embodiment, the server obtains the service identifier of each service to be restored in the degradation stack, and determines the pop order of each service to be restored in the degradation stack according to the first-in-last-out strategy and the service identifier of each service to be restored.

[0163] For example, the push order of the services to be restored in the degradation stack is service C, service B, and service A. For this degradation stack, the server obtains the service identifiers of services C, B, and A in the stack. Based on the last-in-first-out (LIFO) strategy and the service identifiers of services C, B, and A, the server determines the pop order of the service identifiers of services C, B, and A in the degradation stack to be service A, service B, and service C.

[0164] Step 604: Determine the second target service from the services to be restored according to the pop order of each service to be restored in the downgrade stack.

[0165] In this embodiment of the application, the server determines the second target service from each service to be restored in turn according to the pop order of each service to be restored in the degradation stack.

[0166] In this embodiment, the server can determine the service to be downgraded again among the services to be restored according to the order of the services to be restored in the downgrade stack. Due to the last-in-first-out characteristic of the stack, the efficiency of determining the service to be downgraded again (i.e. the second target service) among the services to be restored can be improved.

[0167] In one embodiment, such as Figure 7 As shown, step 104 includes:

[0168] Step 702: If the load of the maintenance item is less than the load threshold, determine the difference between the load of the maintenance item and the load threshold.

[0169] In this embodiment of the application, when the load of the maintenance item is less than the load threshold, the server subtracts the load of the maintenance item from the load threshold to obtain the difference between the load of the maintenance item and the load threshold.

[0170] Step 704: Determine the range of the difference between the load status of the maintenance item and the load threshold.

[0171] In this embodiment, the server can pre-store the mapping relationship between the load status of multiple maintenance items and the difference range of load thresholds, as well as the target number of services to be restored corresponding to each difference range. Then, the server determines the difference range to which the difference belongs based on the difference between the load status of the maintenance item and the load threshold. For example, a larger difference indicates more abundant service resources, allowing for simultaneous restoration of multiple services to be restored, improving service restoration efficiency and stability. Conversely, a smaller difference indicates more strained service resources, allowing for simultaneous restoration of fewer or even one service to be restored, ensuring the stability of more critical services. For instance, if difference range 1 is greater than difference range 2, the target number of services to be restored corresponding to difference range 1 is greater than the target number of services to be restored corresponding to difference range 2.

[0172] Step 706: Obtain the target number of services to be restored corresponding to the difference range.

[0173] In this embodiment, the server determines the target number of services to be restored corresponding to the difference range between the load status of the maintenance item and the load threshold, based on the difference range to which the difference belongs and the mapping relationship between each difference range and the target number of services to be restored corresponding to each difference range.

[0174] Step 708: Based on the downgrade priority, determine the target number of services to be restored from each of the first target services.

[0175] In this embodiment of the application, the server determines a target number of services to be restored from each first target service according to the downgrade priority.

[0176] In this embodiment, the server can identify multiple services to be restored at once based on the difference between the load status of the maintenance item and the load threshold, and perform parallel restoration processing on multiple services to be restored, thereby improving the efficiency of service restoration processing.

[0177] In one embodiment, such as Figure 8 As shown, step 104 includes:

[0178] Step 802: Obtain the real-time load status of each operation and maintenance item.

[0179] The operation and maintenance items may include, but are not limited to, the CPU utilization, memory usage and disk space of components such as cluster services, databases and caches. The operation and maintenance items and their number can be adapted by those skilled in the art, and this application does not make specific limitations.

[0180] In this embodiment of the application, the server can obtain the real-time load status of each operation and maintenance item according to the load acquisition interface provided by the operation and maintenance platform interface.

[0181] Step 804: Take the highest real-time load among all real-time load conditions as the load condition of the operation and maintenance item.

[0182] In this embodiment of the application, the highest real-time load among the real-time loads of each operation and maintenance item of the server is taken as the load of the operation and maintenance item.

[0183] For example, when the cluster service has a CPU utilization of 50%, a memory utilization of 60%, and a disk space utilization of 20%, the database has a CPU utilization of 70%, a memory utilization of 20%, and a disk space utilization of 50%, and the cache has a CPU utilization of 30%, a memory utilization of 60%, and a disk space utilization of 45%, the highest real-time load in the real-time load scenario is the database's CPU utilization. The server uses the database's CPU utilization of 70% as the load scenario for the operation and maintenance item.

[0184] In this embodiment, the server can select the highest real-time load from the real-time load of each maintenance item as the load of the maintenance item. This achieves the effect of using the load of the maintenance item with the highest load as the load of the maintenance item, ensuring that the server is in the optimal state for responding to subsequent routine business and restoring businesses that need to be restored, thus ensuring the high availability of the server.

[0185] In one embodiment, such as Figure 9 As shown, an example of a business degradation processing procedure is also provided, which includes the following:

[0186] Step A1: When a service degradation operation is triggered, the first target service is determined from multiple services.

[0187] The application service includes multiple business functions, and the modules in the server that implement each function are as follows: Figure 10 As shown.

[0188] In this embodiment of the application, when the server triggers a service degradation operation, it triggers a dynamic degradation switch through the scheduler to determine the first target service from multiple services.

[0189] Step A2: Based on the fact that the switch status of the dynamic degradation switch corresponding to each first target service is in the "on" state, generate a degradation configuration item that includes the switch status of the dynamic degradation switch being in the "on" state.

[0190] Step A3: Send the degradation configuration item, which includes the dynamic degradation switch and has its switch status set to "on", to the dynamic degradation switch request logic in the application logic of the first target service.

[0191] In this embodiment of the application, the server sends a degradation configuration item containing a dynamic degradation switch with the switch status set to "on" to the dynamic degradation switch request logic in the application logic of the first target service through the degradation adjustment module.

[0192] Step A4: Set the switch state of the dynamic degradation switch in the dynamic degradation switch request logic of the application logic of the first target business to the on state.

[0193] Step A5: Monitor the load of the operation and maintenance items of the application service. If the load of the operation and maintenance items is less than the load threshold, determine the service to be restored from each first target service according to the degradation priority.

[0194] In this embodiment of the application, the server obtains the load status of the operation and maintenance items through the load status acquisition interface (i.e., application load monitoring service).

[0195] Step A6: For the service to be restored, determine the request hit status of the service to be restored according to the gradient recovery strategy.

[0196] In this embodiment of the application, for the service to be restored, the server determines a gradient recovery strategy based on the current traffic characteristics.

[0197] like Figure 11 As shown, the server determines the request hit rate of the service to be restored based on the gradient recovery strategy and the user requests for the service to be restored.

[0198] For example, the server obtains the user ID or the device ID of the user terminal from each user request in the service to be restored, and uses the user ID or the device ID of the user terminal in the user request as the request ID. Then, for each user request, the service uses a hash algorithm to obtain the hash value corresponding to the user request based on the request ID of the user request, and performs a modulo operation on the hash value corresponding to the user request with 100 to obtain the target feature value of each user request (i.e., Figure 11 (k in the original text). Then, the server reads the pre-set incremental gradient ratio and initial gradient ratio, and determines multiple recovery gradient ratios based on the pre-set incremental gradient ratio and initial gradient ratio. The server obtains a first recovery ratio from the multiple recovery gradient ratios, and for each first recovery gradient ratio, determines the target feature value that is greater than the target feature value corresponding to that recovery gradient ratio. User requests that are greater than the target feature value corresponding to that recovery gradient ratio are taken as the user requests that have been matched, and wait for a preset adjustment time.

[0199] Step A7: After the preset adjustment time, obtain the load status of the operation and maintenance items, determine whether the load status of the operation and maintenance items is less than the load threshold, and if the load status of the operation and maintenance items is less than the load threshold, determine the second recovery gradient ratio from each recovery gradient ratio.

[0200] In this embodiment, after a preset adjustment time, the server obtains the load status of the maintenance item and determines whether the load status of the maintenance item is less than the load threshold. If the load status of the maintenance item is less than the load threshold, a second recovery gradient ratio is determined from each recovery gradient ratio. The server deletes the first recovery gradient ratio and uses the second recovery gradient ratio as the first recovery gradient ratio. After the service to be restored has undergone recovery processing, if the load status of the maintenance item is less than the load threshold, the second recovery gradient ratio is determined from each recovery gradient ratio until no second recovery gradient ratio exists, at which point the service to be restored is determined to have been fully restored.

[0201] Step A8: If the load of the maintenance item is greater than or equal to the load threshold, the server can cancel the recovery process of the service to be recovered and set the dynamic degradation switch of the service to be recovered to the on state.

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

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

[0204] In one embodiment, such as Figure 13 As shown, a service processing device 1300 is provided, including: a first degradation module 1302, a recovery module 1304, and a second degradation module 1306, wherein:

[0205] The first downgrade module 1302 is used to determine a first target service from multiple services and perform downgrade processing on each of the first target services when a service downgrade operation is triggered.

[0206] The recovery module 1304 is used to monitor the load status of the operation and maintenance items. When the load status of the operation and maintenance items is less than the load threshold, the module determines the service to be recovered from each of the first target services according to the degradation priority, performs service recovery processing on the service to be recovered, and adds the service to be recovered to the degradation stack after the service recovery processing is completed.

[0207] The second degradation module 1306 is used to monitor the load status of the operation and maintenance item. When the load status of the operation and maintenance item is greater than or equal to the load threshold, it determines the second target service from the services to be restored according to the stacking order of the services to be restored in the degradation stack, and performs degradation processing on the second target service.

[0208] The service processing apparatus provided in this embodiment can continuously monitor the load of maintenance items according to pre-defined degradation priorities, and dynamically perform service degradation processing and service recovery processing based on the load of maintenance items. This achieves adaptive adjustment of service degradation and recovery without manual operation, reducing the risk of system instability due to human error and improving service processing efficiency.

[0209] In one embodiment, the first degradation module 1302 is specifically used for:

[0210] Set the switch status of the dynamic degradation switch corresponding to each of the first target services to the on state;

[0211] The process of restoring the service to be restored includes:

[0212] Set the switch of the dynamic degradation switch corresponding to the service to be restored to the off state, and perform restoration processing on the service to be restored.

[0213] In one embodiment, the recovery module 1304 is specifically used for:

[0214] Based on the gradient recovery strategy, determine the request hit status of the service to be recovered;

[0215] Based on the success rate of the requests for the services to be restored, the services to be restored are restored.

[0216] In one embodiment, the recovery module 1304 is specifically used for:

[0217] Obtain the user request for the service to be restored, wherein the user request carries a user feature identifier;

[0218] For any of the user requests, the feature value corresponding to the user request is determined based on the user feature identifier carried in the user request;

[0219] According to the gradient recovery strategy, the proportion of each recovery gradient is determined, and the proportion of the recovery gradient is in an increasing state;

[0220] Based on the feature values ​​corresponding to each user request and the recovery gradient ratio, the hit rate of the service to be restored for each recovery gradient ratio is determined.

[0221] In one embodiment, the recovery module 1304 is specifically used for:

[0222] Determine the first recovery gradient ratio from each of the described recovery gradient ratios;

[0223] The service to be restored is restored according to the first recovery gradient ratio. After the service to be restored is restored, if the load of the operation and maintenance item is less than the load threshold, a second recovery gradient ratio is determined from each of the recovery gradient ratios. The second recovery gradient ratio is adjacent to the first recovery gradient ratio and is greater than the first recovery gradient ratio.

[0224] The second recovery gradient ratio is used as the first recovery gradient ratio, and the process jumps to the step of restoring the service to be restored according to the first recovery gradient ratio until the second recovery gradient ratio no longer exists, and then it is determined that the service to be restored has been restored.

[0225] In one embodiment, the second degradation module 1306 is specifically used for:

[0226] For each service to be restored in the degradation stack, the pop order of each service to be restored in the degradation stack is determined according to the last-in-first-out strategy;

[0227] Based on the pop order of each service to be restored in the downgrade stack, the second target service is determined from each service to be restored.

[0228] In one embodiment, the recovery module 1304 is specifically used for:

[0229] If the load of the maintenance item is less than the load threshold, determine the difference between the load of the maintenance item and the load threshold;

[0230] Determine the range of the difference between the load status of the maintenance item and the load threshold;

[0231] Obtain the target number of services to be restored corresponding to the range of differences;

[0232] Based on the downgrade priority, the target number of services to be restored are determined from each of the first target services.

[0233] In one embodiment, the recovery module 1304 is specifically used for:

[0234] Obtain the real-time load status of each of the aforementioned operation and maintenance items;

[0235] The highest real-time load among all the described real-time load conditions is taken as the load condition of the operation and maintenance item.

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

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

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

[0239] In one embodiment, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above-described method embodiments.

[0240] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the steps in the above method embodiments.

[0241] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0242] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data shall comply with the relevant laws, regulations and standards of the relevant countries and regions.

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

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

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

Claims

1. A business processing method, characterized in that, The method includes: When a service degradation operation is triggered, a first target service is determined from multiple services, and each of the first target services is degraded. Monitor the load of the operation and maintenance items. If the load of the operation and maintenance items is less than the load threshold, determine the service to be restored from each of the first target services according to the degradation priority, perform service restoration processing on the service to be restored, and add the service to be restored to the degradation stack after the service restoration processing is completed. Monitor the load status of the operation and maintenance item. If the load status of the operation and maintenance item is greater than or equal to the load threshold, determine the second target service from the services to be restored according to the stacking order of the services to be restored in the degradation stack, and perform degradation processing on the second target service. The process of restoring the service to be restored includes: Based on the gradient recovery strategy, determine the request hit status of the service to be recovered; Based on the success rate of the requests for the services to be restored, the services to be restored are restored. The step of determining the request hit status of the service to be restored according to the gradient recovery strategy includes: Obtain the user request for the service to be restored, wherein the user request carries a user feature identifier; For any of the user requests, the feature value corresponding to the user request is determined based on the user feature identifier carried in the user request; According to the gradient recovery strategy, the proportion of each recovery gradient is determined, and the proportion of the recovery gradient is in an increasing state; Based on the feature values ​​corresponding to each user request and the recovery gradient ratio, the hit rate of the service to be restored for each recovery gradient ratio is determined.

2. The method according to claim 1, characterized in that, The degradation process for each of the first target services includes: Set the switch status of the dynamic degradation switch corresponding to each of the first target services to the on state; The process of restoring the service to be restored includes: Set the switch of the dynamic degradation switch corresponding to the service to be restored to the off state, and perform restoration processing on the service to be restored.

3. The method according to claim 1, characterized in that, The step of restoring the service to be restored based on the request hit status includes: Determine the first recovery gradient ratio from each of the described recovery gradient ratios; The service to be restored is restored according to the first recovery gradient ratio. After the service to be restored is restored, if the load of the operation and maintenance item is less than the load threshold, a second recovery gradient ratio is determined from each of the recovery gradient ratios. The second recovery gradient ratio is adjacent to the first recovery gradient ratio and is greater than the first recovery gradient ratio. The second recovery gradient ratio is used as the first recovery gradient ratio, and the process jumps to the step of restoring the service to be restored according to the first recovery gradient ratio until the second recovery gradient ratio no longer exists, and then it is determined that the service to be restored has been restored.

4. The method according to claim 1, characterized in that, The step of determining the second target service from the services to be restored according to the stacking order of the services to be restored in the degradation stack includes: For each service to be restored in the degradation stack, the pop order of each service to be restored in the degradation stack is determined according to the last-in-first-out strategy; Based on the pop order of each service to be restored in the downgrade stack, the second target service is determined from each service to be restored.

5. The method according to claim 1, characterized in that, When the load of the maintenance item is less than the load threshold, the step of determining the service to be restored from each of the first target services according to the degradation priority includes: If the load of the maintenance item is less than the load threshold, determine the difference between the load of the maintenance item and the load threshold; Determine the range of the difference between the load status of the maintenance item and the load threshold; Obtain the target number of services to be restored corresponding to the range of differences; Based on the downgrade priority, the target number of services to be restored are determined from each of the first target services.

6. The method according to claim 1, characterized in that, The number of maintenance items is multiple, and the monitoring of the load of the maintenance items includes: Obtain the real-time load status of each of the aforementioned operation and maintenance items; The highest real-time load among all the described real-time load conditions is taken as the load condition of the operation and maintenance item.

7. A business processing apparatus, characterized in that, The device includes: The first degradation module is used to determine the first target service from multiple services when a service degradation operation is triggered, and to perform degradation processing on each of the first target services. The recovery module is used to monitor the load status of the operation and maintenance items. When the load status of the operation and maintenance items is less than the load threshold, the module determines the service to be recovered from each of the first target services according to the degradation priority, performs service recovery processing on the service to be recovered, and adds the service to be recovered to the degradation stack after the service recovery processing is completed. The second degradation module is used to monitor the load status of the operation and maintenance item. If the load status of the operation and maintenance item is greater than or equal to the load threshold, the module determines the second target service from the services to be restored according to the stacking order of the services to be restored in the degradation stack, and performs degradation processing on the second target service. Specifically, the recovery module is used for: Based on the gradient recovery strategy, determine the request hit status of the service to be recovered; Based on the success rate of the requests for the services to be restored, the services to be restored are restored. The recovery module is further specifically used for: Obtain the user request for the service to be restored, wherein the user request carries a user feature identifier; For any of the user requests, the feature value corresponding to the user request is determined based on the user feature identifier carried in the user request; According to the gradient recovery strategy, the proportion of each recovery gradient is determined, and the proportion of the recovery gradient is in an increasing state; Based on the feature values ​​corresponding to each user request and the recovery gradient ratio, the hit rate of the service to be restored for each recovery gradient ratio is determined.

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

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

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

Images