A service management method, device, system and storage medium

Abstract

The application discloses a kind of management methods, device, system and storage medium of service service.It is the method comprising: in response to detecting downgrade scheduling instruction, obtain the downgrade stage data corresponding to the downgrade scheduling instruction from application configuration table;Wherein, the downgrade stage data includes target service identification and downgrade data, at least one downgrade command is contained in the downgrade data;Obtain the target instance identification corresponding to the target service identification;Each described downgrade command is respectively sent to target application instance corresponding to the target instance identification in service service center, to make the target application instance execute the downgrade operation corresponding to each described downgrade command received respectively.The embodiment of the application solves the problem that resource expansion method is not suitable for resource fixed application instance, and improves the adaptability of downgrade optimization strategy.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of Internet, and in particular to a service management method, device, system and storage medium. BACKGROUND

[0002] With the development of the Internet industry, a business requirement has gradually emerged, that is, being able to cope with high-concurrency large traffic access in a short time. To solve this problem, the common solution methods currently include resource expansion methods or technical architecture optimization, wherein the resource expansion method refers to temporarily adding resources to an application instance in a high-concurrency scenario, and the technical architecture optimization refers to using a degradation optimization algorithm to degrade and optimize the resources of the application instance.

[0003] In the process of implementing the present application, it is found that at least the following technical problems exist in the prior art:

[0004] The resource expansion method is not applicable to application instances with fixed resources, and link resource allocation is not uniform. The technical architecture optimization is implemented using a fixed degradation optimization algorithm, and cannot be adjusted in a timely manner according to the actual business scenario, and has poor adaptability. SUMMARY

[0005] The embodiments of the present application provide a service management method, device, system and storage medium to solve the problem that the resource expansion method is not applicable to application instances with fixed resources, and improve the adaptability of the degradation optimization strategy.

[0006] According to an embodiment of the present application, a service management method is provided, applied to a business management platform, and the method comprises:

[0007] In response to detecting a degradation scheduling instruction, obtaining degradation stage data corresponding to the degradation scheduling instruction from an application configuration table, wherein the degradation stage data comprises a target service identifier and degradation data, and the degradation data comprises at least one degradation command;

[0008] Obtaining a target instance identifier corresponding to the target service identifier;

[0009] Sending each degradation command to a target application instance corresponding to the target instance identifier in a business service center, so that the target application instance performs a degradation operation corresponding to each received degradation command.

[0010] According to another embodiment of the present application, a service management method is provided, applied to a business service center, and the method comprises:

[0011] Receiving at least one degradation command sent by a business management platform through a target application instance;

[0012] perform a downgrade operation corresponding to each of the downgrade commands;

[0013] The downgrade command is obtained by the service management platform from downgrade phase data corresponding to the downgrade scheduling instruction in an application configuration table in response to detecting the downgrade scheduling instruction, the downgrade phase data includes a target service identifier and downgrade data, the downgrade data includes at least one downgrade command, and the downgrade command is sent by the service management platform based on a target instance identifier obtained by the service management platform based on the target service identifier.

[0014] According to another embodiment of the present application, a device for managing service is provided, which is applied to a service management platform, and includes:

[0015] A downgrade phase data obtaining module is configured to obtain downgrade phase data corresponding to a downgrade scheduling instruction from an application configuration table in response to detecting the downgrade scheduling instruction, wherein the downgrade phase data includes a target service identifier and downgrade data, and the downgrade data includes at least one downgrade command.

[0016] A target instance identifier obtaining module is configured to obtain a target instance identifier corresponding to the target service identifier.

[0017] A downgrade command sending module is configured to send each of the downgrade commands to a target application instance corresponding to the target instance identifier in a service service center, so that the target application instance performs a downgrade operation corresponding to each of the received downgrade commands.

[0018] According to another embodiment of the present application, a device for managing service is provided, which is applied to a service service center, and includes:

[0019] A downgrade command receiving module is configured to receive at least one downgrade command sent by a service management platform through a target application instance.

[0020] A downgrade operation performing module is configured to perform a downgrade operation corresponding to each of the downgrade commands.

[0021] The downgrade command is obtained by the service management platform from downgrade phase data corresponding to the downgrade scheduling instruction in an application configuration table in response to detecting the downgrade scheduling instruction, the downgrade phase data includes a target service identifier and downgrade data, the downgrade data includes at least one downgrade command, and the downgrade command is sent by the service management platform based on a target instance identifier obtained by the service management platform based on the target service identifier.

[0022] According to another embodiment of the present application, a management system of service is provided, characterized in that the system comprises a service management platform and a service center;

[0023] The service management platform is configured to, in response to detecting a downgrade scheduling instruction, acquire downgrade stage data corresponding to the downgrade scheduling instruction from an application configuration table, acquire a target instance identifier corresponding to a target service identifier in the downgrade stage data, and send each downgrade command in the downgrade stage data to a target application instance in the service center corresponding to the target instance identifier.

[0024] The target application instance in the service center is configured to receive at least one downgrade command sent by the service management platform, and perform a downgrade operation corresponding to each of the downgrade commands.

[0025] According to another embodiment of the present application, a computer readable storage medium is provided, which stores computer instructions for causing a processor to implement the management method of service according to any of the embodiments of the present application.

[0026] The technical solution of the embodiments of the present application acquires downgrade stage data corresponding to a detected downgrade scheduling instruction from an application configuration table, acquires a target instance identifier corresponding to a target service identifier in the downgrade stage data, and sends each downgrade command in the downgrade stage data to a target application instance in the service center corresponding to the target instance identifier, so that the target application instance performs a downgrade operation corresponding to each of the received downgrade commands, thereby solving the problem that the resource expansion method is not applicable to application instances with fixed resources, and the downgrade operation performed by the application instance can achieve reasonable allocation of link resources. Moreover, the embodiments of the present application provide a service management platform, so that an operation and maintenance personnel can customize and edit the downgrade stage data in the application configuration table on the service management platform, thereby improving the adaptability between the downgrade strategy and the business scenario and the application instance, and improving the downgrade effect of the application instance.

[0027] It should be understood that the content described in this section is not intended to identify key or important features of the embodiments of the present application, nor is it used to limit the scope of the present application. Other features of the present application will become apparent from the following description. BRIEF DESCRIPTION OF DRAWINGS

[0028] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed in the embodiment description will be briefly introduced as follows. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative effort.

[0029] Figure 1 A flow chart of a method for managing a service provided by an embodiment of the present application;

[0030] Figure 2 A flow chart of another method for managing a service provided by an embodiment of the present application;

[0031] Figure 3 An architecture diagram of an application configuration table provided by an embodiment of the present application;

[0032] Figure 4 A flow chart of another method for managing a service provided by an embodiment of the present application;

[0033] Figure 5 A schematic diagram of an execution state machine policy provided by an embodiment of the present application;

[0034] Figure 6 A flow chart of a method for managing a service provided by an embodiment of the present application;

[0035] Figure 7 A flow chart of another method for managing a service provided by an embodiment of the present application;

[0036] Figure 8 A structural schematic diagram of a device for managing a service provided by an embodiment of the present application;

[0037] Figure 9 A structural schematic diagram of a device for managing a service provided by an embodiment of the present application;

[0038] Figure 10 A structural schematic diagram of a system for managing a service provided by an embodiment of the present application;

[0039] Figure 11 A flow chart of a specific example of a system for managing a service provided by an embodiment of the present application. DETAILED DESCRIPTION

[0040] In order to make the personnel in the art better understand the present application, the technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, but not all the embodiments. Based on the embodiments in the present application, all the other embodiments obtained by the personnel in the art without any creative effort should be within the protection scope of the present application.

[0041] It is to be understood that the terminology "first", "second", and the like used throughout this specification and the accompanying drawings is merely used for distinguishing between similar objects, and is not necessarily used to describe a particular sequential or chronological order. It is to be understood that the use of such terms as "first", "second", and the like, is not to be construed to specify a order of magnitude, but rather to distinguish between various components. Unless otherwise defined, all terms of estimation, such as "approximately", "substantially" or the like are used herein to mean within 10%, or within 5%, or within 1%, or within 0.5% of a value. The use of any of the following terms "comprises", "comprising", "includes", "including", "contains", "containing" or the like, is intended to be open-ended, and to mean including, but not limited to. It will be understood that any described or equivalent processes, methods, systems, or devices that include "comprising", "including", "containing", "has", "has a", or "has one or more of" any element are intended to be construed in the same manner as those "consisting of", "consisting essentially of", and those "comprising" or "including" the specifically recited elements, but not necessarily limited to those elements specifically recited. It will be further understood that terms, such as "a" or "an", or the like, are open-ended and are intended to mean one or more than one, depending on the context of the situation. It will be further understood that terms, such as "another", or the like, are intended to mean "at least one", and are not intended to be limited to "exactly one".

[0042] Figure 1 A flowchart of a method for managing a service is provided for an embodiment of the present application. The embodiment can be applicable to the case of degrading management of application instances in a service center. The method can be executed by a management device of a service, which can be implemented in the form of hardware and / or software. The management device of the service can be configured in a service management platform. As shown in Figure 1 the method includes:

[0043] S110, in response to detecting a degradation scheduling instruction, obtaining degradation stage data corresponding to the degradation scheduling instruction from an application configuration table.

[0044] In one specific embodiment, the degradation scheduling instruction is generated by the service management platform when a preset trigger condition is detected. The preset trigger condition can be that the current time meets a preset scheduling time and / or a trigger operation input by a user is received.

[0045] In another specific embodiment, the degradation scheduling instruction is sent by the scheduling center to the service management platform when a preset trigger condition is detected. The preset trigger condition includes that the current time meets a preset scheduling time and / or a trigger operation input by a user is received.

[0046] In one specific embodiment, the application configuration table contains a target service identifier, at least one degradation data, and a preset scheduling time corresponding to each degradation data. In this embodiment, the degradation stage data includes the target service identifier and the degradation data, and the degradation data contains at least one degradation command. Specifically, the degradation scheduling instruction contains the preset scheduling time, and the degradation data corresponding to the detected preset scheduling time is found in the application configuration table.

[0047] In another specific embodiment, the method further comprises: obtaining a pre-created application configuration table; wherein the application configuration table comprises target service identifiers, at least one stage data, and trigger time corresponding to each stage data, the at least one stage data comprises at least one degradation data; based on the preset operation date, the application configuration table is published to the scheduling center, so that the scheduling center determines the preset scheduling time corresponding to each degradation data in the application configuration table based on the preset operation date and the trigger time in the application configuration table, and sends a degradation scheduling instruction to the service management platform when it is detected that the current time meets the preset scheduling time corresponding to any degradation data in the application configuration table.

[0048] Specifically, the trigger time represents a specific time of the day, such as 8:00, 8:31, etc., and the preset operation date can represent a possible date of high-concurrent access traffic, such as November 11, 2022. By superimposing the preset operation date and the trigger time, the preset scheduling time can be obtained, such as 8:00 on November 11, 2022.

[0049] The advantage of this setting is that if the application configuration table contains preset scheduling times, when the next high-concurrent access traffic occurs, on December 12, 2022, at 8:00, the preset scheduling time of each stage data in the application configuration table needs to be changed, which increases the workload of modification. This embodiment separates the preset operation date from the trigger time, so when the above scenario occurs, only the preset operation date needs to be modified, thereby improving the management efficiency of the service.

[0050] It should be noted that the number of target service identifiers in the degradation stage data is not limited in this embodiment. It can be understood that the degradation stage data can contain one or more target service identifiers. The present embodiment mainly exemplarily explains and describes one target service identifier.

[0051] S120, obtaining a target instance identifier corresponding to the target service identifier.

[0052] Specifically, the service identifier can represent the type of service provided by at least one application instance, such as submitting an order, after-sales service, etc. The instance identifier represents the identification number of the application instance. For example, the target instance identifier can be composed of characters, letters, numbers or special characters. The target instance identifier is not limited here.

[0053] Corresponding to each service identifier, there is at least one instance identifier. For example, assuming that the at least one instance identifier corresponding to the service identifier A includes instance identifier 1, instance identifier 2 and instance identifier 3, when the target service identifier is the service identifier A, at least one of the instance identifier 1, the instance identifier 2 and the instance identifier 3 can be acquired.

[0054] In one embodiment, acquiring the target instance identifier corresponding to the target service identifier includes: acquiring the target instance identifier corresponding to the target service identifier from a local storage space of the service management platform.

[0055] In another embodiment, acquiring the target instance identifier corresponding to the target service identifier includes: sending an instance pulling instruction generated based on the target service identifier to the registration center, so that the registration center acquires at least one registered instance identifier corresponding to the target service identifier, and determines the target instance identifier based on an instance state parameter corresponding to each registered instance identifier; receiving the target instance identifier sent by the registration center based on the instance pulling instruction; wherein the registration center includes at least one registered instance identifier registered by the service service center under at least one preset service identifier.

[0056] For example, the registered instance identifier can be an IP (Internet Protocol) address and / or a port address of an application instance.

[0057] For example, the instance state parameter includes, but is not limited to, a resource occupancy rate, a resource idle rate, a service processing performance and a network bandwidth of an application instance, and the like, and the instance state parameter is not limited herein. Specifically, based on the instance state parameter corresponding to each registered instance identifier, the target instance identifier is determined, the registered instance identifier with the best instance state parameter is taken as the target instance identifier, or the instance state parameters are sorted in descending order, and the top two registered instance identifiers are taken as the target instance identifiers respectively.

[0058] The advantage of such a setting is that by setting the registration center, the registration information of each application instance in the service service center can be managed separately, and the code complexity of the service management platform can be reduced.

[0059] It should be noted that the number of the target instance identifiers corresponding to the target service identifier acquired by the embodiment is not limited, and the embodiment is mainly exemplarily explained and described by taking one target instance identifier.

[0060] S130, each degradation command is sent to a target application instance corresponding to the target instance identifier in the service service center, so that the target application instance performs a degradation operation corresponding to each received degradation command.

[0061] In particular, the business service center includes at least one application instance for providing different business services. For example, the instance identifier 1, the instance identifier 2 and the instance identifier 3 correspond to the application instances for providing the business service A, and the instance identifier 4 and the instance identifier 5 correspond to the application instances for providing the business service B.

[0062] In particular, the downgrade command can be used to represent a downgrade operation performed by the target application instance. For example, the downgrade operation includes, but is not limited to, a downgrade log, a downgrade cache processing or a downgrade business logic, etc.

[0063] The technical scheme of the embodiment, by obtaining the downgrade phase data corresponding to the detected downgrade scheduling instruction from the application configuration table, obtaining the target instance identifier corresponding to the target business identifier in the downgrade phase data, and sending each downgrade command in the downgrade phase data to the target application instance corresponding to the target instance identifier in the business service center, so that the target application instance performs the downgrade operation corresponding to each received downgrade command, solves the problem that the resource expansion method is not applicable to the application instance with fixed resources. The downgrade operation performed by the application instance can realize the reasonable allocation of link resources. Moreover, the business management platform is provided in the embodiment, so that the operation and maintenance personnel can customize and edit the downgrade phase data in the application configuration table on the business management platform, thereby improving the adaptability between the downgrade strategy and the business scenario and the application instance, and improving the downgrade effect of the application instance.

[0064] Figure 2 The flowchart of another business service management method provided by an embodiment of the application, the embodiment further optimizes the business service management method provided by the above-mentioned embodiment, as shown in Figure 2 The method comprises the following steps.

[0065] In S210, the application configuration table created in advance is published to the scheduling center based on a preset operation date.

[0066] In the embodiment, the application configuration table includes a target business identifier, at least two phase data and trigger time corresponding to each phase data. The at least two phase data include at least one downgrade data and recovery data corresponding to each downgrade data. The trigger time of the first recovery data in the application configuration table is later than the trigger time of the last downgrade data in the application configuration table. The command architecture between each downgrade command in the downgrade data is opposite to the command architecture between each recovery command in the recovery data.

[0067] Figure 3 The architecture diagram of the application configuration table provided by an embodiment of the application. In particular, Figure 3The upper diagram in FIG. 1 shows an application configuration table. Specifically, the degradation process in the application configuration table includes degradation data of N degradation stages, and the recovery process includes recovery data of N recovery stages corresponding to the degradation process. Each degradation command (recovery command) in the degradation data (or the recovery data) is sent to a target application instance according to a command architecture in the application configuration table, so as to Figure 3 Taking the degradation data of the first degradation stage in the degradation process as an example, the business management platform sends the degradation command 1.1 in the degradation data to the target application instance, and simultaneously sends the degradation command 1.3 and the degradation command 2.1 to the target application instance.

[0068] Figure 3 The lower diagram in FIG. 1 shows a command set composed of the degradation commands and the recovery commands in the application configuration table. Specifically, different degradation commands and corresponding recovery commands are set for different business services. For example, the application configuration table sets the degradation command 1.1 and the degradation command 1.3 corresponding to the business service A, and the recovery command 1.2 corresponding to the degradation command 1.1 and the recovery command 1.4 corresponding to the degradation command 1.3.

[0069] Specifically, the scheduling center is configured to determine preset scheduling times corresponding to each degradation data in the application configuration table based on preset operation dates and trigger times in the application configuration table. Specifically, the trigger time is used to represent a specific time of a day, such as 8:00, 8:31, and the like, and the preset operation date can represent a possible date of high-concurrency access traffic, such as November 11, 2022. By superimposing the preset operation date and the trigger time, the preset scheduling time can be obtained, such as November 11, 2022, 8:00.

[0070] S220, in response to detecting the degradation scheduling instruction, obtaining degradation stage data corresponding to the degradation scheduling instruction from the application configuration table.

[0071] In this embodiment, the degradation scheduling instruction is sent by the scheduling center to the business management platform when it is detected that the current time meets the preset scheduling time corresponding to any degradation data in the application configuration table.

[0072] S230, obtaining a target instance identifier corresponding to the target business identifier.

[0073] It should be noted that the number of target business identifiers in the degradation stage data is not limited in this embodiment. It can be understood that the degradation stage data can include one or more target business identifiers, and the present embodiment mainly exemplarily explains and describes one target business identifier. The number of target instance identifiers corresponding to the target business identifier obtained in this embodiment is not limited.

[0074] S240, respectively send each downgrade command to a target application instance corresponding to the target instance identifier in the business service center, so that the target application instance executes a downgrade operation corresponding to each received downgrade command.

[0075] Specifically, the downgrade command can be used to represent a downgrade operation performed by the target application instance. For example, the downgrade operation includes but is not limited to downgrade log, downgrade cache processing, or downgrade business logic, etc.

[0076] S250, in response to detecting the recovery scheduling instruction, obtaining recovery phase data corresponding to the recovery scheduling instruction from the application configuration table.

[0077] In this embodiment, the recovery scheduling instruction is sent by the scheduling center to the business management platform when it is detected that the current time meets the preset scheduling time corresponding to any recovery data in the application configuration table.

[0078] S260, obtaining a target instance identifier corresponding to the target business identifier.

[0079] It should be noted that the number of target business identifiers in the recovery phase data is not limited in this embodiment. It can be understood that the recovery phase data can contain one or more target business identifiers, and the present embodiment mainly exemplarily explains one target business identifier. The number of target instance identifiers corresponding to the target business identifier obtained in this embodiment is not limited.

[0080] S270, respectively send each recovery command to a target application instance corresponding to the target instance identifier in the business service center, so that the target application instance executes a recovery operation corresponding to each received recovery command.

[0081] For example, the recovery operation includes but is not limited to recovery log, recovery cache processing, or recovery business logic, etc.

[0082] After the business management platform controls the application instance to execute the downgrade operation, although the application instance has the ability to quickly respond to high-concurrent traffic access, when the high-concurrent traffic access ends, the resource configuration of the application instance at this time cannot well correspond to the traffic access situation in the daily scene, so that the adaptability to the daily scene is poor. The technical solution of the embodiment is that at least one downgrade data and the recovery data corresponding to each downgrade data are set in the application configuration table, the triggering time of the first recovery data in the application configuration table is later than the triggering time of the last downgrade data in the application configuration table, the command architecture between each downgrade command in the downgrade data is opposite to the command architecture between each recovery command in the recovery data, specifically, the recovery stage data corresponding to the detected recovery scheduling instruction is acquired from the application configuration table, the target instance identifier corresponding to the target business identifier in the recovery stage data is acquired, and each recovery command in the recovery stage data is sent to the target application instance corresponding to the target instance identifier in the business service center, so that the target application instance executes the recovery operation corresponding to each received recovery command, the problem that the application instance cannot cope with the business processing in the daily scene after executing the downgrade operation is solved, the integrity of the management process of the business service is ensured, and the adaptability between the application instance and the real business scene is further improved.

[0083] Figure 4 The flowchart of another business service management method provided by an embodiment of the application further optimizes the execution state of the application instance in the above-mentioned embodiment. As shown in Figure 4 the method comprises:

[0084] S310, in response to detecting the stage scheduling instruction, acquiring application stage data corresponding to the stage scheduling instruction from the application configuration table.

[0085] In the embodiment, the application stage data comprises a target business identifier and stage data, the stage data comprises an execution state machine strategy and at least one application command, the execution state machine strategy comprises at least one preset execution strategy, and the at least one preset execution strategy comprises a failure execution strategy corresponding to the at least one application command and / or a pause execution strategy corresponding to the stage data.

[0086] In the embodiment, when the stage scheduling instruction is a downgrade scheduling instruction, the application stage data is downgrade stage data, the stage data is downgrade data, and the application command is a downgrade command; when the stage scheduling instruction is a recovery scheduling instruction, the application stage data is recovery stage data, the stage data is recovery data, and the application command is a recovery command.

[0087] S320, acquiring a target instance identifier corresponding to the target business identifier.

[0088] S330, in the process of sending each application command to the target application instance corresponding to the target instance identifier in the service management center, obtaining an instance execution state.

[0089] In one embodiment, the instance execution state is used to represent the execution state fed back by the target application instance after executing the service operation corresponding to the application command. For example, the instance execution state is a failure execution state or a success execution state. Specifically, when the stage scheduling instruction is a downgrade scheduling instruction, the service operation is a downgrade operation, and when the stage scheduling instruction is a recovery scheduling instruction, the service operation is a recovery operation.

[0090] In another embodiment, the instance execution state is used to represent the execution state generated by the service management platform after detecting the control operation input by the user. For example, the instance execution state is a pause execution state or a pause recovery state.

[0091] S340, in the case where the instance execution state meets a preset state condition, obtaining a target execution strategy corresponding to the instance execution state in an execution state machine strategy, and executing the target execution strategy.

[0092] In this embodiment, the preset state condition includes the instance execution state being a success execution state and / or the instance execution state being a pause recovery state. Specifically, when the instance execution state is a failure execution state sent by the target application instance, the target execution strategy is a failure execution strategy, and when the instance execution state is a pause recovery state generated by the service management platform, the target execution strategy is a pause execution strategy.

[0093] In one specific embodiment, the failure execution strategy is an ignore execution strategy, a retry execution strategy, or a consistency execution strategy. The ignore execution strategy is to obtain at least one unexecuted application command in the stage data and send each unexecuted application command to the target application instance. The retry execution strategy is to send the application command corresponding to the instance execution state to the target application instance based on a preset retry number or a preset retry time range. The consistency execution strategy is to obtain recovery data corresponding to the downgrade data when the instance execution state is a failure execution state sent by the target application instance based on the received downgrade command, obtain at least one recovery command corresponding to the instance execution state in the recovery data, and send each recovery command to the target application instance.

[0094] In one embodiment, the preset execution strategy of the application command corresponding to the failure execution state in the stage data is an ignore execution strategy. Specifically, when the failure execution state is detected, at least one unexecuted application command in the stage data is obtained, and each unexecuted application command is sent to the target application instance. The at least one unexecuted application command does not include the application command corresponding to the failure execution state.

[0095] In another embodiment, the preset execution strategy of the application command corresponding to the execution failure state in the stage data is a retry execution strategy. Specifically, when the execution failure state is detected, the application command corresponding to the execution failure state is sent to the target application instance if the current retry number of the application command is less than the preset retry number. When the current retry number is equal to the preset retry number, at least one unexecuted application command in the stage data is obtained, and each unexecuted application command is sent to the target application instance. Alternatively, when the execution failure state is detected, the application command corresponding to the execution failure state is sent to the target application instance if the current time is within the preset retry time range. When the current time is out of the preset retry time range, at least one unexecuted application command in the stage data is obtained, and each unexecuted application command is sent to the target application instance.

[0096] For example, the preset retry number can be 5, which is not limited herein. Specifically, the preset retry time range is the execution time range corresponding to the stage data, the minimum time of the execution time range is the preset scheduling time of the stage data, and the maximum time is the preset end time.

[0097] In another embodiment, the preset execution strategy of the downgrade command corresponding to the execution failure state in the downgrade data is a consistency execution strategy. For example, when the execution failure state corresponding to the second downgrade command in the downgrade data A is detected, at least one recovery command corresponding to the execution failure state in the recovery data A is obtained, and each recovery command is sent to the target application instance. The at least one recovery command corresponding to the execution failure state includes the first recovery command and the second recovery command.

[0098] It should be noted that the preset execution strategies of the application commands corresponding to each application command in the same stage data can be the same or different. For example, the preset execution strategy of the first downgrade command in the stage data A is a retry execution strategy, and the preset execution strategy of the second downgrade command in the stage data A is a consistency execution strategy. The preset execution strategies of the application commands corresponding to each application command are not limited herein, and can be customized by the user according to actual needs.

[0099] In one specific embodiment, the stage data further comprises a preset time range, and correspondingly, the method further comprises: determining an execution time range corresponding to the stage data based on the preset operation date and the preset time range; wherein the suspension execution strategy comprises a downgrade execution strategy or a recovery execution strategy, the downgrade execution strategy comprises: in a case where the current time meets the execution time range of the downgrade data, obtaining at least one unexecuted downgrade command in the downgrade data, and sending each unexecuted downgrade command to the target application instance; and the recovery execution strategy comprises: in a case where the current time meets the execution time range of the recovery data, sending each recovery command in the recovery data to the target application instance.

[0100] In the process of executing the downgrade management or the recovery management by the business management platform, the user can control the business management platform to suspend the downgrade process or the recovery process according to the actual situation. Specifically, the minimum time of the preset time range is the trigger time, and the maximum time is the end time.

[0101] In one embodiment, when the stage data is downgrade data, the preset execution strategy corresponding to the downgrade data comprises a downgrade execution strategy. For example, it is assumed that the downgrade data comprises 10 downgrade commands, the execution time range is 2022-8-19 8:00-9:00, the suspension execution operation input by the user is detected after the second downgrade command is sent, and the current time corresponding to the suspension recovery operation input by the user is 2022-8-19 8:31, then the third to tenth downgrade commands in the downgrade data are sent to the target application instance.

[0102] On the basis of the above embodiment, the downgrade execution strategy further comprises: in a case where the current time does not meet the execution time range of the downgrade data, waiting for the next downgrade scheduling instruction.

[0103] In another embodiment, when the stage data is recovery data, the preset execution strategy corresponding to the recovery data comprises a recovery execution strategy. For example, it is assumed that the recovery data comprises 10 recovery commands, the execution time range is 2022-8-19 8:00-9:00, the suspension execution operation input by the user is detected after the second recovery command is sent, and the current time corresponding to the suspension recovery operation input by the user is 2022-8-19 8:31, then the first to tenth recovery commands in the recovery data are sent to the target application instance.

[0104] The advantage of such a setting is that each recovery command in the recovery data is sent to the target application instance as much as possible, so that the target application instance can be completely restored to the state between downgrades.

[0105] On the basis of the above-mentioned embodiments, the resuming execution strategy further comprises: in a case where the current time does not satisfy the execution time range of the resuming data, waiting for a next resuming scheduling instruction.

[0106] Figure 5 A schematic diagram of an execution state machine strategy provided by an embodiment of the present application is shown. Specifically, after starting to execute a current application command, if the obtained instance execution state is an execution failure state, a failure execution strategy corresponding to the execution failure state is selected by using a failure execution strategy selector corresponding to the execution failure state, wherein the failure execution strategy is an ignore execution strategy, a retry execution strategy, or a consistency execution strategy; if the obtained instance execution state is an execution success state, a next application command is executed; and if the obtained instance execution state is a pause resuming state, a pause execution strategy corresponding to the pause resuming state is selected by using a pause execution strategy selector corresponding to the pause resuming state, wherein the pause execution strategy includes a downgrade execution strategy and a resuming execution strategy.

[0107] The technical scheme of the present embodiment sets an execution state machine strategy for phase data, the execution state machine strategy includes at least one preset execution strategy, the at least one preset execution strategy includes a failure execution strategy corresponding to at least one application command and / or a pause execution strategy corresponding to the phase data, specifically, a target execution strategy corresponding to an instance execution state in the execution state machine strategy is obtained when the obtained instance execution state satisfies a preset state condition, and the target execution strategy is executed, wherein when the instance execution state is an execution failure state sent by a target application instance, the target execution strategy is the failure execution strategy, and when the instance execution state is a pause resuming state generated by a business management platform, the target execution strategy is the pause execution strategy, thereby solving the problem of management of the execution state of the application instance, further improving the management method of the business service, improving the ability of the management method of the business service to cope with unexpected situations, and further improving the intelligence of the business service management.

[0108] Figure 6 A flowchart of a management method of a business service provided by an embodiment of the present application is shown. The present embodiment can be applied to the case of downgrade management of an application instance in a business service center. The method can be executed by a business service management device, which can be realized in the form of hardware and / or software, and can be configured in the business service center. As shown in the figure, the method includes: Figure 6

[0109] S410, receiving at least one downgrade command sent by a business management platform by using a target application instance.

[0110] ​In specific, the business service center includes at least one application instance for providing different business services. For example, the instance identifier 1, the instance identifier 2 and the instance identifier 3 correspond to the application instances for providing the business service A respectively, and the instance identifier 4 and the instance identifier 5 correspond to the application instances for providing the business service B respectively.

[0111] In the embodiment, the downgrade command is obtained by the business management platform from the downgrade stage data corresponding to the downgrade scheduling instruction in the application configuration table in response to detecting the downgrade scheduling instruction, the downgrade stage data includes a target business identifier and downgrade data, and the downgrade data includes at least one downgrade command; the downgrade command is sent by the business management platform based on a target instance identifier, and the target instance identifier is obtained by the business management platform based on the target business identifier.

[0112] S420, a downgrade operation corresponding to each downgrade command is performed.

[0113] In specific, the downgrade command can be used to represent a downgrade operation performed by the target application instance, for example, the downgrade operation includes but is not limited to a downgrade log, a downgrade cache processing or a downgrade business logic, etc.

[0114] The technical scheme of the embodiment, by the target application instance in the business service center, at least one downgrade command sent by the business management platform is received, and a downgrade operation corresponding to each downgrade command is performed, the downgrade command is obtained by the business management platform from the downgrade stage data corresponding to the downgrade scheduling instruction in the application configuration table in response to detecting the downgrade scheduling instruction, the downgrade stage data includes a target business identifier and downgrade data, and the downgrade data includes at least one downgrade command; the downgrade command is sent by the business management platform based on a target instance identifier, and the target instance identifier is obtained by the business management platform based on the target business identifier, which solves the problem that the resource expansion method is not applicable to the application instance with fixed resources, and the downgrade operation performed by the application instance can realize reasonable allocation of link resources. In addition, the downgrade command received by the target application instance in the embodiment can be customized on the business management platform, thereby improving the adaptability between the application instance and the downgrade strategy and the business scene, and improving the downgrade effect of the application instance.

[0115] On the basis of the above-mentioned embodiment, the application configuration table comprises a target service identifier, at least two stage data, and a triggering time corresponding to each stage data, the at least two stage data comprises at least one degraded data and recovery data corresponding to each degraded data, and correspondingly, the method further comprises: receiving, by the target application instance, at least one recovery command sent by the service management platform; and performing a recovery operation corresponding to each recovery command; wherein the recovery command is obtained by the service management platform from recovery stage data corresponding to a recovery scheduling instruction in the application configuration table in response to detecting the recovery scheduling instruction, the recovery stage data comprises the target service identifier and recovery data, and the recovery data comprises at least one recovery command; and the recovery command is sent by the service management platform based on a target instance identifier, and the target instance identifier is obtained by the service management platform based on the target service identifier.

[0116] For example, the recovery operation comprises, but is not limited to, recovery of a log, recovery of cache processing, or recovery of service logic.

[0117] In this way, the problem that the application instance cannot cope with daily scene service processing after performing the degraded operation is solved, the integrity of the service management process is ensured, and the adaptability between the application instance and the real service scene is further improved.

[0118] It should be noted that the target application instance in the embodiment can be one or more, and the embodiment is exemplarily described by taking one target application instance.

[0119] Figure 7 A flowchart of another service management method provided by an embodiment of the application is shown in FIG. 5, and the embodiment further optimizes the sending process of the degraded command or the recovery command in the above-mentioned embodiment. Figure 7 As shown in FIG. 5, the method comprises the following steps.

[0120] S510, receiving, by the target application instance, at least one application command sent by the service management platform.

[0121] In the embodiment, the number of target application instances is one, and the application command is a degraded command or a recovery command.

[0122] S520, for each application command, performing a service operation corresponding to the application command, and obtaining a configuration center type in the application command.

[0123] In the embodiment, when the application command is a degraded command, the service operation is a degraded operation, and when the application command is a recovery command, the service operation is a recovery operation.

[0124] For example, the degraded operation comprises, but is not limited to, degradation of a log, degradation of cache processing, or degradation of service logic. Figure 3The command set in the lower part of the figure is an example. Different business services correspond to at least one downgrade command and each downgrade command corresponds to a recovery command. Further, the configuration center types in each downgrade command (or recovery command) can be the same or different. For example, business service A corresponds to downgrade command 1.1, downgrade command 1.3, and recovery command 1.2 and recovery command 1.4 corresponding to downgrade command 1.1 and downgrade command 1.3 respectively. Further, the configuration center types in downgrade command 1.1 and recovery command 1.2 are X type, and the configuration center types in downgrade command 1.3 and recovery command 1.4 are Y type.

[0125] S530, send the application command to the target configuration module corresponding to the configuration center type in the configuration center, so that the target configuration module obtains at least one registered instance identifier corresponding to the target instance identifier, and asynchronously sends the received application command to the registered application instance corresponding to each registered instance identifier in the business service center.

[0126] In this embodiment, the configuration center contains at least one preset configuration module, and the preset configuration module contains at least two registered instance identifiers registered by the business service center under at least one preset business identifier.

[0127] For example, assuming that the configuration center types in application command 1 and application command 2 are X type and Y type respectively, target application instance A sends application command 1 and application command 2 to configuration module X and configuration module Y in the configuration center respectively. Among them, at least two registered instance identifiers registered under configuration module X of the configuration center include instance identifier A and instance identifier B, and at least two registered instance identifiers registered under configuration module Y of the configuration center include instance identifier A, instance identifier C and instance identifier D, then configuration module X sends application command 1 to application instance B in the business service center, and configuration module Y sends application command 2 to application instance C and application instance D in the business service center.

[0128] Specifically, the business service center receives the application command asynchronously sent by the configuration center through the registered application instance, and executes the business operation corresponding to the application command.

[0129] If the business management platform sends the application command to the target application instances corresponding to the multiple target instance identifiers in the business service center respectively, the network resources between the business management platform and the business service center will be greatly occupied, and the sending failure of the application command is prone to occur, which brings difficulty to the management and maintenance of the business service. The technical solution of the embodiment receives the application command sent by the business management platform through one target application instance in the business service center, obtains the configuration center type in the application command, and sends the application command to the target configuration module corresponding to the configuration center type in the configuration center, so that the target configuration module obtains at least one registered instance identifier corresponding to the target instance identifier, and sends the received application command to the registered application instance corresponding to each registered instance identifier in the business service center, thereby solving the problem that the sending process of the application command greatly occupies the network resources between the business management platform and the business service center, and reducing the difficulty of the management and maintenance of the business service.

[0130] Figure 8 The structure diagram of a business service management device provided by an embodiment of the application is shown in the figure. The device can be configured in a business management platform. As shown in the figure, the device comprises a degradation stage data acquisition module 610, a target instance identifier acquisition module 620, and a degradation command sending module 630. Figure 8

[0131] The degradation stage data acquisition module 610 is configured to acquire the degradation stage data corresponding to the degradation scheduling instruction from the application configuration table in response to detecting the degradation scheduling instruction; the degradation stage data comprises a target business identifier and degradation data, and the degradation data comprises at least one degradation command.

[0132] The target instance identifier acquisition module 620 is configured to acquire the target instance identifier corresponding to the target business identifier.

[0133] The degradation command sending module 630 is configured to send each degradation command to the target application instance corresponding to the target instance identifier in the business service center, so that the target application instance performs the degradation operation corresponding to each received degradation command.

[0134] ​The technical scheme of the embodiment is characterized in that: the degraded stage data corresponding to the detected degraded scheduling instruction is acquired from the application configuration table, the target instance identifier corresponding to the target service identifier in the degraded stage data is acquired, and each degraded command in the degraded stage data is respectively sent to the target application instance corresponding to the target instance identifier in the service service center, so that the target application instance performs the degraded operation corresponding to each received degraded command, thereby solving the problem that the resource expansion method is not applicable to the application instance with fixed resources, and the degraded operation performed by the application instance can realize reasonable allocation of link resources. In addition, the service management platform is provided, so that the operation and maintenance personnel can customize and edit the degraded stage data in the application configuration table on the service management platform, thereby improving the adaptability between the degraded strategy and the business scenario and the application instance, and improving the degraded effect of the application instance.

[0135] On the basis of the above embodiment, specifically, the degraded scheduling instruction is sent by the scheduling center to the service management platform when a preset trigger condition is detected, and the preset trigger condition includes that the current time meets a preset scheduling time.

[0136] On the basis of the above embodiment, specifically, the apparatus further comprises:

[0137] The application configuration table publishing module is configured to acquire a pre-created application configuration table, wherein the application configuration table comprises a target service identifier, at least one stage data, and a trigger time corresponding to each stage data, and the at least one stage data comprises at least one degraded data.

[0138] The application configuration table is published to the scheduling center based on the preset operation date, so that the scheduling center determines the preset scheduling time corresponding to each degraded data in the application configuration table based on the preset operation date and the trigger time in the application configuration table, and sends a degraded scheduling instruction to the service management platform when it is detected that the current time meets the preset scheduling time corresponding to any degraded data in the application configuration table.

[0139] On the basis of the above embodiment, specifically, the at least two stage data in the application configuration table further comprises recovery data corresponding to each degraded data, the trigger time of the first recovery data in the application configuration table is later than the trigger time of the last degraded data in the application configuration table, and correspondingly, the apparatus further comprises:

[0140] The recovery command sending module is configured to acquire, in response to detection of a recovery scheduling instruction, recovery stage data corresponding to the recovery scheduling instruction from the application configuration table, wherein the recovery stage data comprises a target service identifier and recovery data, and the recovery data comprises at least one recovery command.

[0141] The target instance identifier corresponding to the target service identifier is acquired.

[0142] send each of the recovery commands to a target application instance corresponding to the target instance identifier in the service management platform, so that the target application instance executes a recovery operation corresponding to each of the received recovery commands.

[0143] On the basis of the above embodiment, specifically, the stage data further comprises an execution state machine strategy, the execution state machine strategy comprises at least one preset execution strategy, the at least one preset execution strategy comprises a failure execution strategy corresponding to at least one application command and / or a suspension execution strategy corresponding to the stage data, the application command is a downgrade command or a recovery command, and the stage data is downgrade data or recovery data. Correspondingly, the apparatus further comprises:

[0144] a target execution strategy execution module, configured to, in a case where the obtained instance execution state satisfies a preset state condition, obtain a target execution strategy corresponding to the instance execution state in the execution state machine strategy, and execute the target execution strategy;

[0145] wherein, when the instance execution state is a failure execution state sent by the target application instance, the target execution strategy is the failure execution strategy, and when the instance execution state is a suspension recovery state generated by the service management platform, the target execution strategy is the suspension execution strategy.

[0146] On the basis of the above embodiment, specifically, the failure execution strategy is an ignore execution strategy, a retry execution strategy or a consistency execution strategy, at least one unexecuted application command in the stage data is obtained, and each of the unexecuted application commands is sent to the target application instance; the retry execution strategy is to send an application command corresponding to the instance execution state to the target application instance based on a preset retry number or a preset retry time range; and the consistency execution strategy is to, in a case where the instance execution state is that the target application instance sends based on the received downgrade command, obtain recovery data corresponding to the downgrade data, obtain at least one recovery command corresponding to the instance execution state in the recovery data, and send each of the recovery commands to the target application instance.

[0147] On the basis of the above embodiment, specifically, the stage data further comprises a preset time range, and correspondingly, the apparatus further comprises:

[0148] an execution time range determination module, configured to determine an execution time range corresponding to the stage data based on a preset operation date and the preset time range;

[0149] The suspension execution strategy includes a downgrade execution strategy or a recovery execution strategy. The downgrade execution strategy is that, when the current time meets an execution time range of downgrade data, at least one unexecuted downgrade command in the downgrade data is acquired, and each unexecuted downgrade command is sent to the target application instance. The recovery execution strategy is that, when the current time meets an execution time range of recovery data, each recovery command in the recovery data is sent to the target application instance.

[0150] On the basis of the above embodiment, specifically, the target instance identifier acquisition module 620 is specifically configured to:

[0151] The instance pulling instruction generated based on the target service identifier is sent to the registration center, so that the registration center acquires at least one registered instance identifier corresponding to the target service identifier, and determines the target instance identifier based on the instance state parameters corresponding to each registered instance identifier;

[0152] The target instance identifier sent by the registration center based on the instance pulling instruction is received;

[0153] The registration center includes at least one registered instance identifier registered by the service service center under at least one preset service identifier.

[0154] The service service management device provided by the embodiment of the application has the corresponding function modules and beneficial effects of the service service management method provided by the above-mentioned embodiments of the application.

[0155] Figure 9 A structural schematic diagram of a service service management device provided by an embodiment of the application, which can be configured in a service service center. As shown in the figure, the device includes a downgrade command receiving module 710 and a downgrade operation execution module 720. Figure 9

[0156] The downgrade command receiving module 710 is configured to receive at least one downgrade command sent by the service management platform through the target application instance.

[0157] The downgrade operation execution module 720 is configured to execute a downgrade operation corresponding to each downgrade command.

[0158] The downgrade command is acquired by the service management platform from downgrade stage data corresponding to the downgrade scheduling instruction in the application configuration table in response to detecting the downgrade scheduling instruction. The downgrade stage data includes a target service identifier and downgrade data, and the downgrade data includes at least one downgrade command. The downgrade command is sent by the service management platform based on the target instance identifier, and the target instance identifier is acquired by the service management platform based on the target service identifier.

[0159] ​The technical scheme of the embodiment receives at least one downgrade command sent by the business management platform through the target application instance in the business service center, and executes a downgrade operation corresponding to each downgrade command. The downgrade command is obtained from downgrade stage data corresponding to the downgrade scheduling instruction in the application configuration table by the business management platform in response to detecting the downgrade scheduling instruction. The downgrade stage data includes a target business identifier and downgrade data. The downgrade data contains at least one downgrade command. The downgrade command is sent by the business management platform based on a target instance identifier. The target instance identifier is obtained by the business management platform based on the target business identifier. The problem that the resource expansion method is not applicable to the application instance with fixed resources is solved. The downgrade operation executed by the application instance can realize reasonable allocation of link resources. Moreover, the downgrade command received by the target application instance in the embodiment can be customized on the business management platform, thereby improving the adaptability between the application instance and the downgrade strategy and the business scenario and improving the downgrade effect of the application instance.

[0160] On the basis of the above embodiment, specifically, the application configuration table includes a target business identifier, at least two stage data, and a trigger time corresponding to each stage data. The at least two stage data includes at least one downgrade data and recovery data corresponding to each downgrade data. Correspondingly, the device further includes:

[0161] A recovery operation execution module for receiving at least one recovery command sent by the business management platform through the target application instance.

[0162] Executing a recovery operation corresponding to each recovery command.

[0163] The recovery command is obtained from recovery stage data corresponding to the recovery scheduling instruction in the application configuration table by the business management platform in response to detecting the recovery scheduling instruction. The recovery stage data includes a target business identifier and recovery data. The recovery data contains at least one recovery command. The recovery command is sent by the business management platform based on a target instance identifier. The target instance identifier is obtained by the business management platform based on the target business identifier.

[0164] On the basis of the above embodiment, specifically, the device further includes:

[0165] An application command sending module for obtaining a configuration center type in the received application command. The application command is a downgrade command or a recovery command.

[0166] The application command is sent to a target configuration module corresponding to the configuration center type in the configuration center, so that the target configuration module acquires at least one registered instance identifier corresponding to the target instance identifier, and the received application command is sent to a registered application instance corresponding to each registered instance identifier in the business service center in an asynchronous manner.

[0167] The management device for the business service provided by the embodiment of the application has the corresponding function modules and beneficial effects of the management method for the business service provided by the above-mentioned embodiments of the application.

[0168] Figure 10 A structural schematic diagram of a management system for a business service provided by an embodiment of the application is shown in FIG. 8. The system can provide services for the management method for the business service provided by the above-mentioned embodiments. Specifically, as shown in FIG. 8, the system includes a business management platform 810 and a business service center 820. Figure 10

[0169] The business management platform 810 is configured to acquire, in response to detecting a downgrade scheduling instruction, downgrade stage data corresponding to the downgrade scheduling instruction from an application configuration table, acquire a target instance identifier corresponding to a target business identifier in the downgrade stage data, and send each downgrade command in the downgrade stage data to the business service center 820 based on the target instance identifier. The business service center 820 includes at least one preset application instance, and a target application instance corresponding to the target instance identifier in the business service center 820 is configured to receive at least one downgrade command sent by the business management platform 810 and perform a downgrade operation corresponding to each downgrade command.

[0170] The business management platform 810 can be used by a user to customize and set the application configuration table and send the downgrade command to the target application instance in the business service center 820. For example, the downgrade operation includes but is not limited to a downgrade log, a downgrade cache processing, or a downgrade business logic.

[0171] In a specific embodiment, the application configuration table includes the target business identifier, at least one downgrade data, and a trigger time corresponding to each downgrade data. The system further includes a scheduling center configured to send a downgrade scheduling instruction to the business management platform 810 when a preset trigger condition is detected. The preset trigger condition includes that the current time meets a preset stage scheduling time.

[0172] ​In one specific embodiment, the business management platform 810 is further configured to publish the application configuration table to the dispatch center based on the preset operation date, and the dispatch center is specifically configured to determine preset dispatch times corresponding to each degradation data in the application configuration table based on the preset operation date and the trigger time in the application configuration table, and send a degradation dispatch instruction to the business management platform 810 when detecting that the current time meets the preset dispatch time corresponding to any degradation data in the application configuration table.

[0173] In one specific embodiment, the application configuration table includes a target service identifier, at least two stage data, and trigger times corresponding to each stage data, the at least two stage data includes at least one degradation data and recovery data corresponding to each degradation data, the trigger time of the first recovery data in the application configuration table is later than the trigger time of the last degradation data in the application configuration table, the command architecture between each degradation command in the degradation data is opposite to the command architecture between each recovery command in the recovery data, and the dispatch center is specifically configured to determine preset dispatch times corresponding to each stage data in the application configuration table based on the preset operation date and the trigger time in the application configuration table, and send a stage dispatch instruction to the business management platform 810 when detecting that the current time meets the preset dispatch time corresponding to any stage data in the application configuration table; wherein the stage dispatch instruction is a degradation dispatch instruction or a recovery dispatch instruction.

[0174] On the basis of the above-mentioned embodiments, specifically, the business management platform 810 is further configured to, in response to detecting the recovery dispatch instruction, acquire the recovery stage data corresponding to the recovery dispatch instruction from the application configuration table, acquire the target instance identifier corresponding to the target service identifier in the recovery stage data, and send each recovery command in the recovery stage data to the business service center 820 based on the target instance identifier, and the target application instance is further configured to receive at least one recovery command sent by the business management platform 810 and perform a recovery operation corresponding to each recovery command. Wherein, for example, the recovery operation includes but is not limited to recovery log, recovery cache processing or recovery business logic, etc.

[0175] On the basis of the above-mentioned embodiments, specifically, the system further includes a registration center, the registration center is configured to, in response to receiving an instance pulling instruction sent by the business management platform 810, acquire at least one registered instance identifier corresponding to the target service identifier in the instance pulling instruction, determine the target instance identifier based on the instance state parameter corresponding to each registered instance identifier, and send the target instance identifier to the business management platform 810; wherein the registration center includes at least one registered instance identifier registered by the business service center 820 under at least one preset service identifier.

[0176] Among them, the example instance state parameters include but are not limited to the resource occupancy rate, resource idle rate, service processing performance and network bandwidth of the application instance, and the instance state parameters are not limited here. Among them, based on the instance state parameters corresponding to each registered instance identifier, the target instance identifier is determined, and the registered instance identifier with the best instance state parameter is taken as the target instance identifier.

[0177] On the basis of the above embodiment, specifically, the system further comprises a configuration center, and the target application instance is further configured to obtain the configuration center type in the received downgrade command (or recovery command), and send the downgrade command (or recovery command) to the target configuration module in the configuration center corresponding to the configuration center type based on the configuration center type. The target configuration module in the configuration center is configured to, in response to receiving the downgrade command (or recovery command) sent by the target application instance, obtain at least one registered instance identifier corresponding to the target instance identifier, and asynchronously send the received downgrade command (or recovery command) to the registered application instance in the business service center 820 corresponding to each registered instance identifier.

[0178] Figure 11 A flowchart of a specific example of a business service management system provided by an embodiment of the application. Specifically, the business service center contains application instances corresponding to different business services, such as application instance 1 and application instance 2 belonging to business service A, and application instance 3 and application instance 4 belonging to business service B. The business service center registers the instance identifiers corresponding to each application instance to the registration center.

[0179] The user can customize and create an application configuration table on the business management platform, and publish the application configuration table to the scheduling center based on the preset operation date. The scheduling center delays the scheduling of the stage data in the business management platform according to the preset scheduling time corresponding to each stage data in the application configuration table. Specifically, the business management platform responds to the detection of the stage scheduling instruction, pulls the target instance identifier from the registration center, and sends the application command to the target application instance corresponding to the target instance identifier in the business service center.

[0180] The target application instance executes the business operation corresponding to the received application command, and parses the configuration center type in the application command. The application command is notified to the target configuration module in the configuration center corresponding to the configuration center type by broadcast notification, and the target configuration module asynchronously sends the obtained application command to at least one registered application instance in the business service center under the same business service as the target application instance. Each registered application instance executes the business operation corresponding to the received application command.

[0181] The technical scheme of the embodiment solves the problem that the resource expansion method is not applicable to the application instance with fixed resources, and the degradation operation performed by the application instance can realize reasonable allocation of link resources, and the operation and maintenance personnel can customize the degradation stage data in the application configuration table on the business management platform, thereby improving the adaptability between the degradation strategy and the business scenario and the application instance, and improving the degradation effect of the application instance.

[0182] The fifth embodiment of the application also provides a computer readable storage medium, which stores computer instructions, and the computer instructions are used for causing a processor to execute a management method of a business service.

[0183] In response to detecting the degradation scheduling instruction, degradation stage data corresponding to the degradation scheduling instruction is acquired from the application configuration table, wherein the degradation stage data comprises target business identification and degradation data, and the degradation data comprises at least one degradation command;

[0184] The target instance identification corresponding to the target business identification is acquired.

[0185] Each degradation command is sent to a target application instance corresponding to the target instance identification in the business service center, so that the target application instance performs a degradation operation corresponding to each received degradation command.

[0186] Alternatively, the computer instructions are used for causing the processor to execute another management method of a business service, and the method comprises:

[0187] At least one degradation command is received by the target application instance and sent by the business management platform;

[0188] A degradation operation corresponding to each degradation command is performed.

[0189] The degradation command is acquired by the business management platform from degradation stage data corresponding to the degradation scheduling instruction in the application configuration table in response to detecting the degradation scheduling instruction, the degradation stage data comprises target business identification and degradation data, and the degradation data comprises at least one degradation command; the degradation command is sent by the business management platform based on the target instance identification, and the target instance identification is acquired by the business management platform based on the target business identification.

[0190] In the context of the present application, a computer-readable storage medium can be a tangible medium that can contain or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. A computer-readable storage medium can include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium can be a machine-readable signal medium. More specific examples of a machine-readable storage medium will include one or more lines of a program of instructions in a transitory signal, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0191] To provide for interaction with a user, the systems and techniques described here can be implemented on an electronic device having a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user and a keyboard and a pointing device (e.g., a mouse or a trackball) by which the user can provide input to the electronic device. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form, including acoustic, speech, or tactile input.

[0192] The systems and techniques described here can be implemented in a computing system that includes a back end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front end component (e.g., a user computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back end, middleware, or front end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.

[0193] The computing system can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system, to solve the defects of large management difficulty and weak business scalability in traditional physical host and VPS service.

[0194] It should be understood that the various forms of flow shown above can be reordered, added to, or have steps deleted. For example, the steps described in the present application can be performed in parallel, in series, or in a different order, as long as the desired results of the technical solutions of the present application can be achieved, and this is not limited herein.

[0195] The above detailed description does not constitute a limitation on the protection scope of the present application. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent replacements, and improvements made within the spirit and principles of the present application shall be included in the protection scope of the present application.

Claims

1. A management method of a service, characterized by, The application is applied to a service management platform, and comprises: In response to detecting a downgrade scheduling instruction, obtaining downgrade stage data corresponding to the downgrade scheduling instruction from an application configuration table; wherein the application configuration table contains target service identifiers, at least one downgrade data, and preset scheduling times or trigger moments corresponding to each downgrade data, the downgrade scheduling instruction contains a preset scheduling time, the downgrade stage data comprises target service identifiers and downgrade data, and the downgrade data contains at least one downgrade command; Obtaining target instance identifiers corresponding to the target service identifiers; wherein the target service identifiers represent the types of service services provided by at least one application instance; Sending each downgrade command to a target application instance corresponding to the target instance identifiers in a service service center, so that the target application instance performs a downgrade operation corresponding to each received downgrade command.

2. The method of claim 1, wherein, The downgrade scheduling instruction is sent by a scheduling center to the service management platform when a preset trigger condition is detected, and the preset trigger condition comprises a current time satisfying a preset scheduling time.

3. The method of claim 2, wherein, The method further comprises: Obtaining an application configuration table created in advance; wherein the application configuration table comprises target service identifiers, at least one stage data, and trigger moments corresponding to each stage data, and the at least one stage data comprises at least one downgrade data; Based on a preset operation date, publishing the application configuration table to the scheduling center, so that the scheduling center determines preset scheduling times corresponding to each downgrade data in the application configuration table based on the preset operation date and each trigger moment in the application configuration table, and sends a downgrade scheduling instruction to the service management platform when it is detected that a current time satisfies a preset scheduling time corresponding to any downgrade data in the application configuration table.

4. The method of claim 3, wherein, At least two stage data in the application configuration table further comprises recovery data corresponding to each downgrade data, the trigger moment of the first recovery data in the application configuration table is later than the trigger moment of the last downgrade data in the application configuration table, and correspondingly, the method further comprises: In response to detecting a recovery scheduling instruction, obtaining recovery stage data corresponding to the recovery scheduling instruction from an application configuration table; wherein the recovery stage data comprises target service identifiers and recovery data, and the recovery data contains at least one recovery command; Obtaining target instance identifiers corresponding to the target service identifiers; Sending each recovery command to a target application instance corresponding to the target instance identifiers in a service service center, so that the target application instance performs a recovery operation corresponding to each received recovery command.

5. The method of claim 4, wherein, The stage data further comprises an execution state machine strategy, the execution state machine strategy comprising at least one preset execution strategy, the at least one preset execution strategy comprising a failure execution strategy corresponding to at least one application command respectively and / or a suspension execution strategy corresponding to the stage data, the application command being a downgrade command or a recovery command, the stage data being downgrade data or recovery data, and correspondingly, the method further comprises: In a case where the obtained instance execution state satisfies a preset state condition, obtaining a target execution strategy corresponding to the instance execution state in the execution state machine strategy, and executing the target execution strategy; Wherein, when the instance execution state is a failure execution state sent by the target application instance, the target execution strategy is a failure execution strategy, and when the instance execution state is a suspension recovery state generated by the business management platform, the target execution strategy is a suspension execution strategy.

6. The method of claim 5, wherein, The failure execution strategy is an ignore execution strategy, a retry execution strategy or a consistency execution strategy, the method further comprising: obtaining at least one unexecuted application command in the stage data, and sending each unexecuted application command to the target application instance respectively; The retry execution strategy comprises: based on a preset retry number or a preset retry time range, sending an application command corresponding to the instance execution state to the target application instance; The consistency execution strategy comprises: in a case where the instance execution state is sent by the target application instance based on a received downgrade command, obtaining recovery data corresponding to the downgrade data, obtaining at least one recovery command corresponding to the instance execution state in the recovery data, and sending each recovery command to the target application instance respectively.

7. The method of claim 5, wherein, The stage data further comprises a preset time range, and correspondingly, the method further comprises: Based on a preset operation date and the preset time range, determining an execution time range corresponding to the stage data; Wherein, the suspension execution strategy comprises a downgrade execution strategy or a recovery execution strategy, the downgrade execution strategy comprising: in a case where a current time satisfies an execution time range of the downgrade data, obtaining at least one unexecuted downgrade command in the downgrade data, and sending each unexecuted downgrade command to the target application instance respectively; and the recovery execution strategy comprising: in a case where a current time satisfies an execution time range of the recovery data, sending each recovery command in the recovery data to the target application instance respectively.

8. The method according to any one of claims 1 to 7, characterized in that, The obtaining of the target instance identifier corresponding to the target business identifier comprises: Sending an instance pulling instruction generated based on the target business identifier to a registration center, so that the registration center obtains at least one registered instance identifier corresponding to the target business identifier, and determines a target instance identifier based on an instance state parameter corresponding to each registered instance identifier; Receiving the target instance identifier sent by the registration center based on the instance pulling instruction; Wherein, the registration center comprises at least one registered instance identifier registered by the business service center under at least one preset business identifier.

9. A management method of a service, characterized by, Applied to a business service center, comprising: receive at least one downgrade command sent by the service management platform through the target application instance; perform a downgrade operation corresponding to each of the downgrade commands; wherein the downgrade command is obtained by the service management platform from downgrade stage data corresponding to a downgrade scheduling instruction in an application configuration table, the downgrade stage data including a target service identifier and downgrade data, the downgrade data including at least one downgrade command, the application configuration table including the target service identifier, at least one downgrade data, and a preset scheduling time or a trigger time corresponding to each of the downgrade data, the downgrade scheduling instruction including a preset scheduling time, and the target instance identifier being obtained by the service management platform based on the target service identifier.

10. The method of claim 9, wherein, The application configuration table includes a target service identifier, at least two stage data, and a trigger time corresponding to each of the stage data, the at least two stage data including at least one downgrade data and recovery data corresponding to each of the downgrade data, and the method further includes: receive at least one recovery command sent by the service management platform through the target application instance; perform a recovery operation corresponding to each of the recovery commands; wherein the recovery command is obtained by the service management platform from recovery stage data corresponding to a recovery scheduling instruction in an application configuration table, the recovery stage data including a target service identifier and recovery data, the recovery data including at least one recovery command, and the recovery command being sent by the service management platform based on a target instance identifier obtained by the service management platform based on the target service identifier.

11. The method according to claim 9 or 10, characterized in that, The method further includes: obtain a configuration center type in the received application command; wherein the application command is a downgrade command or a recovery command; send the application command to a target configuration module corresponding to the configuration center type in the configuration center, so that the target configuration module obtains at least one registered instance identifier corresponding to the target instance identifier, and asynchronously sends the received application command to a registered application instance corresponding to each of the registered instance identifiers in the service service center; wherein the configuration center includes at least one preset configuration module, and the preset configuration module includes at least two registered instance identifiers registered by the service service center under at least one preset service identifier.

12. A management apparatus of a service, characterized by comprising: application to a service management platform, including: The degradation stage data acquisition module is configured to acquire, in response to detecting the degradation scheduling instruction, degradation stage data corresponding to the degradation scheduling instruction from an application configuration table; wherein the application configuration table contains a target service identifier, at least one degradation data, and preset scheduling time or a triggering moment corresponding to each degradation data, the degradation scheduling instruction contains the preset scheduling time, the degradation stage data includes the target service identifier and the degradation data, and the degradation data contains at least one degradation command; The target instance identifier acquisition module is configured to acquire a target instance identifier corresponding to the target service identifier; wherein the target service identifier represents a type of service provided by each of the at least one application instance; The degradation command sending module is configured to send each degradation command to a target application instance corresponding to the target instance identifier in the service center, so that the target application instance performs a degradation operation corresponding to each received degradation command.

13. A management apparatus of a service, characterized by comprising: The application is applied to a service center and includes: The degradation command receiving module is configured to receive, by a target application instance, at least one degradation command sent by a service management platform; The degradation operation execution module is configured to perform a degradation operation corresponding to each degradation command; The degradation command is acquired by the service management platform from degradation stage data corresponding to a degradation scheduling instruction in an application configuration table in response to detecting the degradation scheduling instruction, the application configuration table contains a target service identifier, at least one degradation data, and preset scheduling time or a triggering moment corresponding to each degradation data, the degradation scheduling instruction contains the preset scheduling time, the degradation stage data includes the target service identifier and the degradation data, and the degradation data contains at least one degradation command; the degradation command is sent by the service management platform based on a target instance identifier, the target instance identifier is acquired by the service management platform based on the target service identifier, and the target service identifier represents a type of service provided by each of the at least one application instance.

14. A management system of a service, characterized by, The system includes a service management platform and a service center; The service management platform is configured to acquire, in response to detecting a degradation scheduling instruction, degradation stage data corresponding to the degradation scheduling instruction from an application configuration table, acquire a target instance identifier corresponding to a target service identifier in the degradation stage data, and send each degradation command in the degradation stage data to the service center based on the target instance identifier. The service center contains at least one preset application instance, and a target application instance corresponding to the target instance identifier in the service center is configured to receive at least one degradation command sent by the service management platform and perform a degradation operation corresponding to each degradation command. The application configuration table contains target service identification, at least one degraded data, and preset scheduling time or trigger time corresponding to each degraded data. The degraded scheduling instruction contains preset scheduling time. The target service identification represents the type of service provided by at least one application instance.

15. The system of claim 14, wherein, The system further includes a scheduling center. When a preset trigger condition is detected, the scheduling center sends a degraded scheduling instruction to the service management platform. The preset trigger condition includes a preset stage scheduling time.

16. The system of claim 14, wherein, The system further includes a registration center. In response to receiving an instance pulling instruction sent by the service management platform, the registration center obtains at least one registered instance identification corresponding to the target service identification in the instance pulling instruction, determines a target instance identification based on an instance state parameter corresponding to each registered instance identification, and sends the target instance identification to the service management platform. The registration center contains at least one registered instance identification registered by the service service center under at least one preset service identification.

17. The system of claim 14, wherein, The system further includes a configuration center. The target application instance obtains the configuration center type in the received degraded command, and sends the degraded command to the configuration center based on the configuration center type. A target configuration module corresponding to the configuration center type in the configuration center obtains at least one registered instance identification corresponding to the target instance identification in response to receiving the degraded command sent by the target application instance, and sends the received degraded command to the registered application instance corresponding to each registered instance identification in the service service center. The configuration center contains at least one preset configuration module. The preset configuration module contains at least two registered instance identifications registered by the service service center under at least one preset service identification.

18. A computer-readable storage medium, characterized in that, The computer readable storage medium stores computer instructions for making the processor execute the management method of the service service in any one of claims 1-8 or claims 9-11.

Images