Service degradation method, system, device, computer equipment and storage medium

Abstract

The present application relates to a service degradation method, system, device, computer equipment and storage medium, and relates to the field of intelligent operation and maintenance, and can be used in the financial field or other fields. The method includes: obtaining the call information of each business, the call information includes the business label of the business, the target service called by the business and the target system to which the target service belongs, and determining the degradation strategy corresponding to each business according to the call information of each business, and the degradation strategy is used to trigger the flow control of the business. For any business, according to the call information of the business, the degradation strategy corresponding to the business is issued to the target system in the call information, so that when the target service in the target system is called by the business, the target system performs corresponding degradation processing on the business according to the degradation strategy corresponding to the business. The use of this method can avoid the mutual influence of each business in the traditional degradation method, and maximize the normal operation of each business.

Description

Technical Field

[0001] The present application relates to the field of intelligent operation and maintenance, and in particular to a service degradation method, system, device, computer equipment and storage medium. Background Art

[0002] With the development of diverse banking services and distributed systems, an application system can be called by multiple businesses simultaneously. However, the number of calls supported by the application system per unit time is limited. When the total number of calls to the application system by multiple businesses is too large, it will affect the normal operation of the entire banking system. To improve the high availability of the banking system, service degradation, interface current limiting, and service circuit breaking are used to protect the banking system.

[0003] In traditional technology, the service of the called application system is downgraded to avoid the collapse of the entire banking system and ensure that other application systems can operate normally. That is, when the total call volume of the called application system exceeds the threshold, the service of the application system is downgraded.

[0004] However, in the current service degradation method, an application system often needs to be called by multiple businesses at the same time. When the call volume of a business surges, causing the total call volume of the application system to exceed the threshold, it will trigger service degradation for the application system, limiting the total call volume of the application system to less than the threshold, thereby limiting the number of calls to other businesses and affecting the normal operation of other businesses. Summary of the Invention

[0005] Based on this, it is necessary to provide a service degradation method, system, apparatus, computer equipment, computer-readable storage medium and computer program product that can perform service degradation processing for each business in order to address the above technical problems.

[0006] In a first aspect, the present application provides a method for service degradation. The method comprises:

[0007] Acquire call information of each service, the call information including a service tag of the service, a target service called by the service, and a target system to which the target service belongs;

[0008] Determining, based on the call information of each of the services, a degradation strategy corresponding to each of the services, wherein the degradation strategy is used to trigger flow limiting for the services;

[0009] For any of the services, based on the calling information of the service, the downgrade policy corresponding to the service is sent to the target system in the calling information, so that when the target service in the target system is called by the service, the target system performs corresponding downgrade processing on the service according to the downgrade policy corresponding to the service.

[0010] In one embodiment, determining the degradation strategy corresponding to each of the services according to the call information of each of the services includes:

[0011] For any of the services, determining a transaction attribute of the service according to the service tag in the call information of the service, where the transaction attribute is used to indicate the importance of the service;

[0012] A degradation strategy corresponding to the business is determined according to the transaction attribute of the business and the target service in the call information of the business.

[0013] In one embodiment, determining the degradation strategy corresponding to the business according to the transaction attributes of the business and the target service in the call information of the business includes:

[0014] For any of the businesses, determining an estimated transaction peak value of the business based on historical transaction data of the business;

[0015] Obtaining a maximum transaction processing volume (TPS) value supported by the target service in the call information of the business;

[0016] Determining a TPS threshold corresponding to the business according to the transaction attributes of the business, the estimated transaction peak of the business, and the maximum TPS value supported by the target service;

[0017] A degradation strategy corresponding to the service is generated according to the TPS threshold corresponding to the service.

[0018] In one embodiment, determining the TPS threshold corresponding to the business based on the transaction attributes of the business, the estimated transaction peak of the business, and the maximum TPS value supported by the target service includes:

[0019] When the transaction attribute indicates that the business is of the first business type, determining a TPS threshold for the business according to the estimated transaction peak and a maximum TPS value supported by the target service;

[0020] Alternatively, when the transaction attribute indicates that the business is of the second business type, a target TPS value is determined according to a preset ratio and a maximum TPS value supported by the target service;

[0021] Determining the TPS threshold of the business based on the estimated transaction peak and the target TPS value;

[0022] The importance of the first business type is higher than the importance of the second business type.

[0023] In a second aspect, the present application further provides a service degradation method, the method comprising:

[0024] Receive a degradation policy corresponding to each service issued by a service label service degradation system, wherein the degradation policy is determined by the service label service degradation system according to the call information of the service, and the degradation policy is used to trigger flow control of the service;

[0025] When the target service is called by the target business, the degradation policy corresponding to the target business is matched;

[0026] According to the degradation policy corresponding to the target service, the target service is subjected to corresponding degradation processing to limit the number of times the target service calls the target service.

[0027] In one embodiment, performing corresponding downgrade processing on the target service according to the downgrade policy corresponding to the target service to limit the number of times the target service calls the target service includes:

[0028] Determining whether the target service satisfies the corresponding degradation policy based on the unit call volume of the target service, where the unit call volume is the number of times the target service calls the target service within a unit time;

[0029] When the target service satisfies the corresponding degradation policy, the target service is subjected to corresponding degradation processing to limit the number of times the target service calls the target service.

[0030] In one embodiment, the degradation policy corresponding to the target service includes a TPS threshold, and judging whether the target service satisfies the corresponding degradation policy based on the unit call volume of the target service includes:

[0031] Counting the unit call volume of the target service by the target business within the unit time;

[0032] When the unit call volume is greater than the TPS threshold, determining that the target service satisfies the corresponding degradation policy; or

[0033] When the unit call volume is less than or equal to the TPS threshold, it is determined that the target service does not satisfy the corresponding degradation policy.

[0034] In a third aspect, the present application further provides a service degradation system, the system comprising: a first system, a service label service degradation system and a target system; wherein,

[0035] The first system is configured to obtain call information of each service through a proxy module, and upload the call information of each service to the service label service degradation system, wherein the call information includes the service label of the service, the target service called by the service, and the target system to which the target service belongs;

[0036] The service tag service degradation system is used to determine the degradation policy corresponding to each of the services based on the received call information of each of the services, and for any of the services, send the degradation policy corresponding to the service to the target system in the call information of the service, wherein the degradation policy is used to trigger flow control of the service;

[0037] The target system is used to receive the downgrade policy corresponding to each of the services issued by the service tag service downgrade system, match the downgrade policy corresponding to the target service when the target service is called by the target service, and perform corresponding downgrade processing on the target service according to the downgrade policy corresponding to the target service to limit the number of times the target service calls the target service.

[0038] In a fourth aspect, the present application further provides a service degradation device. The device includes:

[0039] An acquisition module is used to acquire call information of each service, wherein the call information includes a service tag of the service, a target service called by the service, and a target system to which the target service belongs;

[0040] A determination module, configured to determine a degradation strategy corresponding to each of the services based on the call information of each of the services, wherein the degradation strategy is used to trigger current limiting for the services;

[0041] The sending module is used to send the downgrade policy corresponding to the business to the target system in the calling information for any of the businesses, based on the calling information of the business, so that when the target service in the target system is called by the business, the target system performs corresponding downgrade processing on the business according to the downgrade policy corresponding to the business.

[0042] In one embodiment, the determining module is further configured to:

[0043] For any of the services, determining a transaction attribute of the service according to the service tag in the call information of the service, where the transaction attribute is used to indicate the importance of the service;

[0044] A degradation strategy corresponding to the business is determined according to the transaction attribute of the business and the target service in the call information of the business.

[0045] In one embodiment, the determining module is further configured to:

[0046] For any of the businesses, determining an estimated transaction peak value of the business based on historical transaction data of the business;

[0047] Obtaining a maximum transaction processing volume (TPS) value supported by the target service in the call information of the business;

[0048] Determining a TPS threshold corresponding to the business according to the transaction attributes of the business, the estimated transaction peak of the business, and the maximum TPS value supported by the target service;

[0049] A degradation strategy corresponding to the service is generated according to the TPS threshold corresponding to the service.

[0050] In one embodiment, the determining module is further configured to:

[0051] When the transaction attribute indicates that the business is of the first business type, determining a TPS threshold for the business according to the estimated transaction peak and a maximum TPS value supported by the target service;

[0052] Alternatively, when the transaction attribute indicates that the business is of the second business type, a target TPS value is determined according to a preset ratio and a maximum TPS value supported by the target service;

[0053] Determining the TPS threshold of the business based on the estimated transaction peak and the target TPS value;

[0054] The importance of the first business type is higher than the importance of the second business type.

[0055] In a fifth aspect, the present application further provides a service degradation device, the device comprising:

[0056] A receiving module, configured to receive a degradation policy corresponding to each service issued by a service label service degradation system, wherein the degradation policy is determined by the service label service degradation system according to the call information of the service, and the degradation policy is used to trigger flow control of the service;

[0057] A matching module, configured to match a degradation policy corresponding to a target service when a target service is called by the target service;

[0058] The degradation module is configured to perform corresponding degradation processing on the target service according to the degradation policy corresponding to the target service, so as to limit the number of times the target service calls the target service.

[0059] In one embodiment, the downgrade module is further configured to:

[0060] Determining whether the target service satisfies the corresponding degradation policy based on the unit call volume of the target service, where the unit call volume is the number of times the target service calls the target service within a unit time;

[0061] When the target service satisfies the corresponding degradation policy, the target service is subjected to corresponding degradation processing to limit the number of times the target service calls the target service.

[0062] In one embodiment, the downgrade module is further configured to:

[0063] Counting the unit call volume of the target service by the target business within the unit time;

[0064] When the unit call volume is greater than the TPS threshold, determining that the target service satisfies the corresponding degradation policy; or

[0065] When the unit call volume is less than or equal to the TPS threshold, it is determined that the target service does not satisfy the corresponding degradation policy.

[0066] In a sixth aspect, the present application further provides a computer device. The computer device includes a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:

[0067] Acquire call information of each service, the call information including a service tag of the service, a target service called by the service, and a target system to which the target service belongs;

[0068] Determining, based on the call information of each of the services, a degradation strategy corresponding to each of the services, wherein the degradation strategy is used to trigger flow limiting for the services;

[0069] For any of the services, based on the calling information of the service, the downgrade policy corresponding to the service is sent to the target system in the calling information, so that when the target service in the target system is called by the service, the target system performs corresponding downgrade processing on the service according to the downgrade policy corresponding to the service.

[0070] In a seventh aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the following steps:

[0071] Acquire call information of each service, the call information including a service tag of the service, a target service called by the service, and a target system to which the target service belongs;

[0072] Determining, based on the call information of each of the services, a degradation strategy corresponding to each of the services, wherein the degradation strategy is used to trigger flow limiting for the services;

[0073] For any of the services, based on the calling information of the service, the downgrade policy corresponding to the service is sent to the target system in the calling information, so that when the target service in the target system is called by the service, the target system performs corresponding downgrade processing on the service according to the downgrade policy corresponding to the service.

[0074] In an eighth aspect, the present application further provides a computer program product. The computer program product includes a computer program that, when executed by a processor, implements the following steps:

[0075] Acquire call information of each service, the call information including a service tag of the service, a target service called by the service, and a target system to which the target service belongs;

[0076] Determining, based on the call information of each of the services, a degradation strategy corresponding to each of the services, wherein the degradation strategy is used to trigger flow limiting for the services;

[0077] For any of the services, based on the calling information of the service, the downgrade policy corresponding to the service is sent to the target system in the calling information, so that when the target service in the target system is called by the service, the target system performs corresponding downgrade processing on the service according to the downgrade policy corresponding to the service.

[0078] The above-mentioned service degradation method, system, device, computer equipment, storage medium and computer program product obtain the calling information of each business, and the calling information includes the business tag of the business, the target service called by the business and the target system to which the target service belongs, and determines the degradation strategy corresponding to each business based on the calling information of each business. The degradation strategy is used to trigger the flow control of the business. For any business, based on the calling information of the business, the degradation strategy corresponding to the business is issued to the target system in the calling information, so that when the target service in the target system is called by the business, the target system performs corresponding degradation processing on the business according to the degradation strategy corresponding to the business. Based on the above-mentioned service degradation method, system, device, computer equipment, storage medium and computer program product, the degradation strategy corresponding to each business is determined through the calling information of each business, and the degradation strategy corresponding to the business is issued to the target system in the calling information. When the target service in the target system is called by the business, the business can be downgraded accordingly according to the degradation strategy corresponding to the business. That is, the target system can downgrade each business accordingly according to the degradation strategy corresponding to each business, that is, the corresponding business can be downgraded in a targeted manner without downgrading the service of the application system, thereby avoiding mutual influence between businesses, maximizing the normal operation of each business, and improving the stability of the business. BRIEF DESCRIPTION OF THE DRAWINGS

[0079] Figure 1 A diagram illustrating an application environment of a service degradation method in one embodiment;

[0080] Figure 2 A flowchart of a service degradation method in one embodiment;

[0081] Figure 3 Schematic diagram of a flow chart of a service degradation method in another embodiment;

[0082] Figure 4 Schematic diagram of a flow chart of a service degradation method in another embodiment;

[0083] Figure 5 Schematic diagram of a flow chart of a service degradation method in another embodiment;

[0084] Figure 6 Schematic diagram of a flow chart of a service degradation method in another embodiment;

[0085] Figure 7 Schematic diagram of a flow chart of a service degradation method in another embodiment;

[0086] Figure 8 Schematic diagram of a flow chart of a service degradation method in another embodiment;

[0087] Figure 9is a schematic structural diagram of a service degradation device in one embodiment;

[0088] Figure 10 is a structural diagram of a service degradation device in another embodiment;

[0089] Figure 11 FIG. 1 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0090] In order to make the purpose, technical solutions and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.

[0091] The service degradation method provided in the embodiment of the present application can be applied to Figure 1 In the service degradation system shown in FIG. , the first system 102 includes various businesses, and the target system 106 includes various target services. When any business in the first system 102 starts running, the business will call the target service in the target system 106. The business tag service degradation system 104 is respectively connected to the first system 102 and the target system 106. The first system 102 is deployed with an agent, which uses the agent to intercept the call information of each business and upload the call information of each business to the business tag service degradation system 104. The business tag service degradation system 104 determines the degradation strategy corresponding to each business based on the call information of each business, and sends the degradation strategy corresponding to the business to the target system 106 based on the target system in the call information of the business. When the target service in the target system 106 is called by the business, the target system 106 will determine whether to downgrade the business based on the degradation strategy corresponding to the business.

[0092] In one embodiment, Figure 2 As shown, a service degradation method is provided. This method can be applied to a service tag service degradation system. The service tag service degradation system can be implemented by a terminal or a server. In this embodiment, the method includes the following steps:

[0093] Step 202: Acquire the calling information of each service. The calling information includes the service tag of the service, the target service called by the service, and the target system to which the target service belongs.

[0094] In an embodiment of the present application, for each business, the call information of the business can be obtained separately. For example, by deploying an agent in the system to which the business belongs, the agent can be used to intercept the call information of each business, and the call information of each business can be uploaded to the business tag service degradation system. Among them, the call information of the business can represent the call relationship of calling related services when the business is running normally. The call information includes the business tag of the business, the target service called by the business, and the target system to which the target service belongs. Different businesses correspond to different business tags. The business tag is the identification information of the business to which it corresponds. In the embodiment of the present application, there is no specific limitation on the business tag. Any identification information that can identify the business can be used as a business tag. For example, in the case of "querying account balance", the corresponding business tag can be set to a1. In the case of "changing account password", the corresponding business tag is a2. In the case of "querying loan conditions", the corresponding business tag is b1.

[0095] When a business is running, it needs to call its corresponding target service and perform corresponding processing or operations to obtain the running results of the business. Therefore, the target services called by different businesses are also different. For example, taking the above example, when the business "query account balance" is running, it is necessary to call the target service c1 to read the account balance from the database. When the business "change account password" is running, it is necessary to call the target service c2 to change the account password and save the new password to the database. At the same time, in actual applications, there are situations where the business and the target service called by the business belong to different application systems respectively. Therefore, the call information also needs to include the target system to which the target service belongs. In subsequent processing, the downgrade policy corresponding to the generated business can be sent to the corresponding target system based on the target system in the call information, so that each target system can perform subsequent operations according to the downgrade policy corresponding to each business.

[0096] Taking the above example again, when the business "Query Account Balance" calls service c1, its corresponding call information includes business tag: a1, target service: service c1, target system: system C; the call information of the business "Change Account Password" includes business tag: a2, target service: service c2, target system: system C; the call information of the business "Query Loan Terms" includes business tag: b1, target service: service c1, target system: system C.

[0097] Step 204: Determine the degradation strategy corresponding to each service based on the call information of each service. The degradation strategy is used to trigger flow control for the service.

[0098] In an embodiment of the present application, for any business, the degradation strategy corresponding to the business can be determined based on the business tag in the business call information and the target service called by the business, wherein the degradation strategy is used to trigger the flow limiting of the business, that is, when a certain business meets the degradation strategy, the target system will limit the flow of the business according to the degradation strategy. When the business does not meet the degradation strategy, the target system will not perform special processing on the business, that is, no flow limiting will be performed on the business. In an exemplary embodiment, the degradation of the business can be achieved by limiting the number of times the business calls the target service, that is, the flow limiting of the business can be achieved.

[0099] Step 206: For any business, according to the calling information of the business, the corresponding degradation policy of the business is issued to the target system in the calling information, so that when the target service in the target system is called by the business, the target system performs corresponding degradation processing on the business according to the corresponding degradation policy of the business.

[0100] In an embodiment of the present application, for any business, a downgrade policy corresponding to the business can be issued to the target system based on the target system in the call information of the business. When any target service in the target system is called by the business, the target system will perform corresponding downgrade processing on the business according to the downgrade policy corresponding to the matched business calling the target service, wherein the downgrade processing will limit the number of calls to the target service by the business, that is, in the process of downgrading the business, if the number of calls to the target service by the business exceeds the limit value within a unit time, the target system will intercept the call request of the business to the target service, so as to achieve the purpose of limiting the number of calls to the target service by the business.

[0101] For example, still taking the above example, the downgrade strategy 1 corresponding to when the business "Query Account Balance" calls service c1, the downgrade strategy 2 corresponding to when the business "Change Account Password" calls service c2, and the downgrade strategy 3 corresponding to when the business "Query Loan Conditions" calls service c1 are determined in sequence. The target system in the call information of the above three businesses is system C, so downgrade strategy 1, downgrade strategy 2 and downgrade strategy 3 are sent to system C. When service c1 in system C is called by the business "Query Account Balance", it is necessary to determine whether the business "Query Account Balance" meets downgrade strategy 1. If it meets the requirements, the business "Query Account Balance" will be downgraded and the number of calls to service c1 by the business "Query Account Balance" will be limited; if it does not meet the requirements, the business "Query Account Balance" will not be downgraded.

[0102] In the above service degradation method, the degradation strategy corresponding to each business is determined through the calling information of each business, and the degradation strategy corresponding to the business is issued to the target system in the calling information. When the target service in the target system is called by the business, the business can be downgraded accordingly according to the degradation strategy corresponding to the business. That is, the target system can downgrade each business accordingly according to the degradation strategy corresponding to each business, that is, the corresponding business can be downgraded in a targeted manner without downgrading the service of the application system, thereby avoiding mutual influence between businesses, maximizing the normal operation of each business, and improving the stability of the business.

[0103] In one embodiment, Figure 3 As shown, step 202 includes:

[0104] Step 302: For any business, determine the transaction attribute of the business according to the business tag in the calling information of the business. The transaction attribute is used to indicate the importance of the business.

[0105] In the embodiment of the present application, the transaction attributes are used to represent the importance of the business. For any business, the importance of the business can be determined based on the business tag in the call information of the business, and then the transaction attributes of the business can be obtained. For example, in the embodiment of the present application, the importance of the business can be divided into important and unimportant according to the importance of the business, and then the transaction attributes of the business can include a first business type that characterizes the importance of the business as important and a second business type that characterizes the importance of the business as unimportant. In fact, the above division of importance into important and unimportant, and the transaction attributes corresponding to the first business type and the second type are only used as an example of transaction attributes in the embodiment of the present application. In the embodiment of the present application, there is no specific limitation on the division method of business importance. In fact, the importance can be divided more finely as needed.

[0106] In an embodiment of the present application, the importance of a business can be determined based on information such as the business's domain, attributes, and transaction volume. That is, the business's domain, attributes, and transaction volume can be determined through the business's business tag, and then the importance of the business can be determined to obtain the transaction attributes of the business.

[0107] For example, the importance of a business can be determined by whether the business involves customer accounts, whether it involves customer account security, whether it is a top-level transaction, and the actual transaction volume of the business. When the business meets any of the above conditions of "involving customer accounts, involving customer account security, and belonging to top-level transactions", the business is an important business; when the business does not meet any of the above conditions, the actual transaction volume of the business is greater than the preset transaction volume, or the actual transaction volumes of various businesses in the system are sorted from high to low, and the ranking of the business is before the preset ranking, then the business is also an important business; the remaining businesses in the system are non-important businesses.

[0108] The business tag in the business call information can represent the business. In the banking system, the business tags of the business can be classified according to the content of the business. Taking the above example, the business "query account balance" involves customer accounts, so the business type involving customer accounts includes business tag a1. The business "change account password" involves customer account security, so the business type involving customer accounts includes business tag a2.

[0109] Therefore, the process of determining the transaction attributes of a business based on the business tag in the business call information is as follows: First, the business type to which the business tag belongs can be obtained. If the business tag exists in any of the business types of "involving customer accounts, involving customer account security, and belonging to top-level transactions", the transaction attribute of the business is important. If the business tag does not match any of the above items, the actual transaction volume of the business is obtained based on the business tag, and then the transaction attributes of the business are determined based on the actual transaction volume.

[0110] For example, still taking the above example, the business tag of the business "Query Account Balance" is a1, the business tag of the business "Change Account Password" is a2, and the business tag of the business "Query Loan Conditions" is b1. Based on the business tags of each business, it can be determined that the transaction attributes of the business "Query Account Balance" and the business "Change Account Password" are both important. The business tag b1 does not belong to any of the aforementioned business types of "involving customer accounts, involving customer account security, and belonging to top-level transactions", and the actual transaction volume obtained according to the business tag b1 is not greater than the preset transaction volume. Therefore, the transaction attribute of the business "Query Loan Conditions" is unimportant.

[0111] Step 304: Determine a degradation strategy corresponding to the business based on the transaction attributes of the business and the target service in the calling information of the business.

[0112] In the embodiment of the present application, the target service in the service call information is the target service called by the service. Therefore, a degradation policy corresponding to the service is determined based on the transaction attributes of the service and the target service in the service call information. Specifically, the degradation policy corresponding to the service is determined based on the importance represented by the service transaction attributes and the target service called by the service. For example, the degradation policy may include the maximum number of times the target service can be called within a service unit time. Based on the importance of the service and the target service, the maximum number of times the target service can be called within a service unit time is determined. Furthermore, a degradation policy corresponding to the service is constructed based on the maximum number of times the target service can be called within a service unit time.

[0113] In this embodiment, by determining the transaction attributes of the business, and based on the transaction attributes of the business and the target service in the business call information, the downgrade strategy corresponding to the business is determined and sent to the target system, so that the target system can downgrade the business according to the downgrade strategy corresponding to the above business, which can give priority to ensuring the stability of important businesses and avoid the situation where the surge in non-important business volume causes the important business to stop running.

[0114] In one embodiment, Figure 4 As shown, step 304 includes:

[0115] Step 402: For any business, determine the estimated transaction peak value of the business based on the historical transaction data of the business.

[0116] In this embodiment of the present application, for any business, historical transaction data for the business is first obtained. The historical transaction data refers to the transaction volume of the business within a preset period, which can be determined based on actual needs. An estimated transaction peak value for the business can then be determined based on the historical transaction data. For example, the transaction volume of a business with a business tag a1 is obtained: the transaction peak value (i.e., the maximum transaction volume) of the business within the past day. Based on this transaction peak value, an estimated transaction peak value for the business can be determined.

[0117] In actual applications, the estimated transaction peak of a business can be determined based on its historical transaction peak and future promotion plan. For example, if the historical transaction peak of a business is 1,000 times / second and it is planned that the number of customers for the business will reach 200,000 in the future, and to meet the daily transactions of 200,000 customers, the transaction peak of the business needs to reach 1,100 times / second, then the estimated transaction peak of the business is 1,100 times / second.

[0118] Step 404: Obtain the maximum transaction processing volume (TPS) value supported by the target service in the service call information.

[0119] In the embodiments of the present application, transactions per second (TPS) represents the instantaneous service capability of a system service, that is, the number of service call requests processed by the target service within one second. Obtaining the maximum TPS value supported by the target service in the service call information indicates the maximum number of call requests that the target service can process within one second. In actual application, an agent can be deployed in the target system to which the target service belongs. The service tag service degradation system communicates with the agent in the target system. The agent can obtain the maximum TPS value of the target service and upload the maximum TPS value to the service tag service degradation system.

[0120] Step 406 : Determine the TPS threshold corresponding to the business based on the transaction attributes of the business, the estimated transaction peak of the business, and the maximum TPS value supported by the target service.

[0121] In the embodiment of the present application, the transaction volume of the business will change over time. At a certain moment, the transaction volume of the business can reach the maximum value within a time period. The maximum value of the above transaction volume is the transaction peak of the business. For example, within an hour, the maximum transaction volume of the business is 1000 transactions / second, then the transaction peak of the business is 1000 transactions / second. The estimated transaction peak is the maximum transaction volume of the business in the future period. The TPS threshold corresponding to the business to be confirmed is the maximum number of calls made by the business to the target service in unit time (per second). In the banking system, the number of calls made by the business to the target service is positively correlated with the transaction volume of the business. For example, when completing a transaction of the business, the business will make a call to the target service once. Then the estimated transaction peak of the business (transaction volume / second) is also positively correlated with the TPS threshold corresponding to the business. Therefore, the TPS threshold corresponding to the business can be determined based on the estimated transaction peak of the business, combined with the importance of the business and the maximum TPS value supported by the target service.

[0122] For example, based on the estimated transaction peak of the business, the estimated number of calls to the target service by the business can be determined while meeting the daily transactions of the business. At the same time, based on the importance of the business and the maximum TPS value supported by the target service, the maximum call volume that the target service can provide for the business can be determined. Finally, based on the estimated number of calls to the target service by the business and the maximum call volume that the target service can provide for the business, the TPS threshold corresponding to the business is determined. When the number of calls to the target service by the business per unit time is greater than its corresponding TPS threshold, downgrade processing of the business is triggered.

[0123] Step 408: Generate a degradation strategy corresponding to the service based on the TPS threshold corresponding to the service.

[0124] In an embodiment of the present application, a degradation strategy corresponding to the business is generated according to the TPS threshold corresponding to the business, wherein the degradation strategy corresponding to the business includes: a business label of the business, a target service called by the business, and a TPS threshold corresponding to the business.

[0125] In an embodiment of the present application, the TPS threshold corresponding to the business is determined based on the transaction attributes of the business, the estimated transaction peak of the business, and the maximum TPS value supported by the target service, and the degradation strategy corresponding to the business is determined based on the TPS threshold corresponding to the business, and the degradation strategy corresponding to the business is issued to the target system in the call information. When the target service in the target system is called by the business, the business can be downgraded accordingly according to the downgrade strategy corresponding to the business. That is, the target system can downgrade each business according to the downgrade strategy corresponding to each business, that is, the corresponding business can be downgraded in a targeted manner without downgrading the service of the application system, thereby avoiding mutual influence between businesses, maximizing the guarantee of normal operation of each business, and improving the stability of the business.

[0126] In one embodiment, step 406 includes:

[0127] When the transaction attribute characterizes the service as the first service type, the TPS threshold of the service is determined according to the estimated transaction peak and the maximum TPS value supported by the target service.

[0128] In the embodiment of the present application, the transaction attributes of the business include a first business type and a second business type. The importance of the first business type is higher than that of the second business type. Therefore, for the business with the transaction attribute of the first business type, the TPS value of the business is determined according to the estimated transaction peak and the maximum TPS value supported by the target service. First, the first TPS threshold of the business is determined according to the estimated transaction peak. For example, the estimated transaction peak can be used as the first TPS threshold of the business, or the first TPS threshold of the business can be determined according to the estimated transaction peak and the historical transaction fluctuation of the business, wherein the estimated transaction peak can be determined by The historical transaction volume in the first time range is used to determine the historical transaction volume, and the historical transaction fluctuation is determined by the historical transaction volume in the second time range. The second time range is much larger than the first time range. For example, if the estimated transaction peak of a business is 100 transactions per second, that is, the business will make a maximum of 100 calls to the target service in one second, then the first TPS threshold of the business can be determined to be 100 times per second; or, if the estimated transaction peak of a business is 100 transactions per second, and the historical transaction fluctuation of the business is: the transaction peak increases by 5 transactions per second, then the first TPS threshold of the business can be determined to be 105 times per second.

[0129] It should be noted that the above process of determining the first TPS threshold of a business based on the estimated transaction peak is only an example in the embodiment of the present application. In actual applications, when determining the first TPS threshold of a business based on the estimated transaction peak, the first TPS threshold of the business can be determined based on the needs of the target system, the estimated transaction peak and other basis. In this embodiment, the process of determining the first TPS threshold of a business based on the estimated transaction peak is not specifically limited.

[0130] Afterwards, the first TPS threshold is compared with the maximum TPS value supported by the target service. When the first TPS threshold is greater than the maximum TPS value, the maximum TPS value is set as the TPS threshold of the service; when the first TPS threshold is less than or equal to the maximum TPS value, the first TPS threshold is set as the TPS threshold of the service.

[0131] For example, still taking the above example, case 1: the estimated transaction peak of the business is 1100 times / second, and the transaction attribute of the business is the first business type, the maximum TPS value supported by the target service is 1200 times / second, and the first TPS threshold determined based on the estimated transaction peak of 1100 times / second is 1100 times / second, and the first TPS threshold is less than the maximum TPS value, then the TPS threshold of the business is 1100 times / second; case 2: the estimated transaction peak of the business is 1300 times / second, and the transaction attribute of the business is the first business type, the maximum TPS value supported by the target service is 1200 times / second, and the first TPS threshold determined based on the estimated transaction peak of 1300 times / second is 1300 times / second, and the first TPS threshold is greater than the maximum TPS value, then the TPS threshold of the business is 1200 times / second.

[0132] Or, as Figure 5 As shown, in step 502, when the transaction attribute characterizes the business as the second business type, the target TPS value is determined according to the preset ratio and the maximum TPS value supported by the target service.

[0133] In an embodiment of the present application, when the transaction attribute of a business is the second business type, the preset ratio and the maximum TPS value supported by the target service can be multiplied to obtain the target TPS value, wherein the preset ratio (which can be a pre-set value) is less than 1, and the preset ratios corresponding to different businesses can be the same or different. Exemplarily, the preset ratio can be determined based on the system operation status, actual application needs, and the importance of the business. For example, if the transaction attributes of business 1 and business 2 are both the second business type, and business 1 is more important than business 1, then the preset ratio corresponding to business 2 can be set to 1 / 5, and the preset ratio corresponding to business 1 can be set to 1 / 10.

[0134] Still taking the above example, the preset ratio of business 1 is 1 / 10, and the maximum TPS value supported by the target service is 1200 times / second. It can be obtained that the target TPS value of business 1 is 120 times / second.

[0135] Step 504: Determine the TPS threshold of the business based on the estimated transaction peak and the target TPS value.

[0136] The importance of the first service type is higher than the importance of the second service type.

[0137] In an embodiment of the present application, the TPS value of the business is determined based on the estimated transaction peak and the target TPS value, wherein, first, the first TPS threshold of the business is determined based on the estimated transaction peak, and then the first TPS threshold is compared with the target TPS value. When the first TPS threshold is greater than the target TPS value, the target TPS value is set as the TPS threshold of the business; when the first TPS threshold is less than or equal to the target TPS value, the first TPS threshold is set as the TPS threshold of the business.

[0138] For example, still taking the above example, case 1: the estimated transaction peak of business 1 is 110 times / second, and the transaction attribute of the business is the second business type, the target TPS value is 120 times / second, and the first TPS threshold determined based on the estimated transaction peak of 110 times / second is 110 times / second. The first TPS threshold is less than the target TPS value, then the TPS threshold of the business is 110 times / second; case 2: the estimated transaction peak of business 1 is 130 times / second, and the transaction attribute of the business is the second business type, the maximum TPS value supported by the target service is 120 times / second, and the first TPS threshold determined based on the estimated transaction peak of 130 times / second is 130 times / second. The first TPS threshold is greater than the target TPS value, then the TPS threshold of the business is 120 times / second.

[0139] In an embodiment of the present application, the downgrade strategy corresponding to each business is determined through the calling information of each business, and the downgrade strategy corresponding to the business is issued to the target system in the calling information. When the target service in the target system is called by the business, the business can be downgraded accordingly according to the downgrade strategy corresponding to the business. That is, the target system can downgrade each business accordingly according to the downgrade strategy corresponding to each business, that is, the corresponding business can be downgraded in a targeted manner without downgrading the service of the application system, thereby avoiding mutual influence between businesses, maximizing the normal operation of each business, and improving the stability of the business.

[0140] In one embodiment, Figure 6 As shown, a service degradation method is provided. This method can be applied to a target system. The target system can be implemented by a terminal or a server. In this embodiment, the method includes the following steps:

[0141] Step 602: Receive the degradation policy corresponding to each service issued by the service label service degradation system. The degradation policy is determined by the service label service degradation system according to the calling information of the service. The degradation policy is used to trigger the flow control of the service.

[0142] In an embodiment of the present application, the business tag service degradation system generates a degradation strategy corresponding to each business based on the calling information of the business, and then sends the degradation strategy corresponding to each business to the target system. The target system then receives the degradation strategy corresponding to each business sent by the business tag service degradation system. The specific process of generating and sending the degradation strategy can be referred to the relevant description of the aforementioned embodiment, and will not be repeated here in the embodiment of the present disclosure.

[0143] Step 604: When the target service is called by the target business, the degradation policy corresponding to the target business is matched.

[0144] In an embodiment of the present application, when the target service is called by the target business, a call message from the target business can be received first. The call message includes the business tag of the target business and the called target service. The downgrade strategy includes the business tag of the business and the target service. Therefore, the information in the call message can be matched with the various downgrade strategies in the target system. That is, the business tag and target service of the target business in the call message can be obtained, and the downgrade strategy that includes both the above-mentioned business tag and the above-mentioned target service can be matched.

[0145] Step 606: Perform corresponding downgrade processing on the target service according to the downgrade policy corresponding to the target service, so as to limit the number of calls of the target service by the target service.

[0146] In an embodiment of the present application, after matching the downgrade policy corresponding to the target service, the service is downgraded accordingly according to the downgrade policy corresponding to the target service to limit the number of calls made by the target service to the target service. Specifically, downgrading the service means limiting the number of calls made by the target service to the target service within a range specified by the downgrade policy. If the number of calls made by the target service to the target service exceeds the specified range within a unit of time, the target system will intercept the call request made by the target service to the target service, thereby achieving the purpose of limiting the number of calls made by the target service to the target service.

[0147] In an embodiment of the present application, the downgrade strategy corresponding to each business is determined through the calling information of each business, and the downgrade strategy corresponding to the business is issued to the target system in the calling information. When the target service in the target system is called by the business, the business can be downgraded accordingly according to the downgrade strategy corresponding to the business. That is, the target system can downgrade each business accordingly according to the downgrade strategy corresponding to each business, that is, the corresponding business can be downgraded in a targeted manner without downgrading the service of the application system, thereby avoiding mutual influence between businesses, maximizing the normal operation of each business, and improving the stability of the business.

[0148] In one embodiment, Figure 7 As shown, step 606 includes:

[0149] Step 702: Determine whether the target service satisfies its corresponding degradation policy based on the unit call volume of the target service. The unit call volume is the number of times the target service calls the target service within a unit time.

[0150] In an embodiment of the present application, the degradation policy can be used to specify the maximum number of calls to the target service within a unit time of the target business. The unit call volume is the number of times the target business calls the target service within a unit time, and then the unit call volume of the target service within the unit time of the target business can be used to determine whether it satisfies its corresponding degradation policy. For example: when the unit call volume of the target business is greater than the maximum number of calls indicated by its corresponding degradation policy, the target business satisfies its corresponding degradation policy, and the target system will downgrade the target business according to its corresponding degradation policy. Otherwise, the target business does not satisfy its corresponding degradation policy, and the target system will not perform special processing on the target business.

[0151] Step 704: When the target service meets its corresponding degradation policy, the target service is subjected to corresponding degradation processing to limit the number of times the target service calls the target service.

[0152] In an embodiment of the present application, when the target business meets its corresponding downgrade policy, the target system will perform corresponding downgrade processing on the target business according to the downgrade policy, that is, the target system will limit the number of calls made by the target business to the target service according to the downgrade policy, and limit the number of calls made by the target business to the target service within the TPS threshold range. The maximum number of calls made by the target business to the target service is the TPS threshold. When the target business does not meet its corresponding downgrade policy, the target system will not perform special processing on the business, that is, it will not limit the number of calls made by the target business to the target service.

[0153] In an embodiment of the present application, the downgrade strategy corresponding to each business is determined through the calling information of each business, and the downgrade strategy corresponding to the business is issued to the target system in the calling information. When the target service in the target system is called by the business, the business can be downgraded accordingly according to the downgrade strategy corresponding to the business. That is, the target system can downgrade each business accordingly according to the downgrade strategy corresponding to each business, that is, the corresponding business can be downgraded in a targeted manner without downgrading the service of the application system, thereby avoiding mutual influence between businesses, maximizing the normal operation of each business, and improving the stability of the business.

[0154] In one embodiment, Figure 8 As shown, the degradation policy corresponding to the target service includes a TPS threshold, and step 702 includes:

[0155] Step 802: Count the unit call volume of the target service by the target business within a unit time.

[0156] In the embodiment of the present application, when a target service is called by a target business, the target system begins counting the call requests from the target business to the target service, and calculates the number of call requests from the target business to the target service per unit time, thereby obtaining the unit call volume of the target service by the target business per unit time. The degradation policy corresponding to the target business includes a TPS threshold, and the TPS threshold is the maximum number of calls to the target service by the business per unit time (per second). The specific process for determining the TPS threshold can be referred to the relevant description of the aforementioned embodiment, and will not be repeated here in the present embodiment.

[0157] Step 804: When the unit call volume is greater than the TPS threshold, determine whether the target service meets its corresponding degradation policy.

[0158] In an embodiment of the present application, when the unit call volume is greater than the TPS threshold, the unit call volume of the target business is too large, which will have a negative impact on the normal operation of the target service and the target system. In order to ensure the normal operation of the target service and the target system, the target business satisfies its corresponding degradation strategy at this time, and the target system should limit the unit call volume of the target business according to the degradation strategy.

[0159] Step 806: When the unit call volume is less than or equal to the TPS threshold, it is determined that the target service does not meet its corresponding degradation policy.

[0160] In an embodiment of the present application, when the unit call volume is less than or equal to the TPS threshold, it will not have a negative impact on the normal operation of the target service and the target system. At this time, the target business does not meet its corresponding degradation strategy and the unit call volume of the target business is not restricted.

[0161] In the embodiment of the present application, the target system can perform corresponding downgrade processing on each business according to the downgrade strategy corresponding to each business, that is, the corresponding business can be downgraded in a targeted manner without downgrading the service of the application system, thereby avoiding mutual influence between businesses, maximizing the normal operation of each business, and improving the stability of the business.

[0162] In an exemplary embodiment, the service degradation system is as follows: Figure 1 As shown, taking the services "Query Account Balance", "Change Account Password" and "Query Loan Conditions" as examples, first, the call information of each service is obtained. The call information of the service "Query Account Balance" includes the service tag: a1, target service: service c1, and target system: system C; the call information of the service "Change Account Password" includes the service tag: a2, target service: service c2, and target system: system C; the call information of the service "Query Loan Conditions" includes the service tag: b1, target service: service c1, and target system: system C.

[0163] The transaction attributes of the business are determined based on the business tags in the call information of each business. Among them, if the business tag a1 belongs to the business type involving customer accounts, then the transaction attribute of the business "Query account balance" is the first business type. If the business tag a2 belongs to the business type involving customer account security, then the transaction attribute of the business "Change account password" is the first business type. If the business tag b1 does not belong to any of the aforementioned business types of "involving customer accounts, involving customer account security, and belonging to top-level transactions", and the actual transaction volume obtained according to the business tag b1 is not greater than the preset transaction volume, then the transaction attribute of the business "Query loan conditions" is the second business type.

[0164] Next, the estimated transaction peak for each business is determined based on its historical transaction volume. In the following process, each business is represented by a business label. For business a1, the historical transaction volume of business a1 is obtained: the historical transaction peak is 1000 times / second. It is planned that the number of customers for this business will reach 200,000 in the future. To meet the daily transactions of 200,000 customers, the transaction peak of this business needs to reach 1100 times / second. Therefore, the estimated transaction peak for this business is 1100 times / second. The estimated transaction peak for each business is determined in the same way as above.

[0165] For business a1, its target service is service c1. The maximum TPS value supported by service c1 is 1200 times / second. The transaction attribute of business a1 is the first business type. The first TPS threshold determined based on the estimated transaction peak of 1100 times / second is 1100 times / second. At this time, the first TPS threshold is less than the maximum TPS value, so the TPS threshold of this business is 1100 times / second.

[0166] For business b1, its target service is service c1. The maximum TPS value supported by service c1 is 1200 times / second. The transaction attribute of business b1 is the second business type. The preset ratio corresponding to business b1 is 1 / 10. At this time, the target TPS value is 120 times / second. The first TPS threshold determined based on the estimated transaction peak of 110 times / second is 110 times / second. The first TPS threshold is less than the maximum TPS value, so the TPS threshold of this business is 110 times / second.

[0167] Using the above method, we can obtain the corresponding downgrade policies for the three services. Downgrade Policy 1 includes: a1, service c1, and TPS threshold 1; downgrade Policy 2 includes: a2, service c2, and TPS threshold 2; and downgrade Policy 3 includes: b1, service c1, and TPS threshold 3. Since the target system for all three services is System C, downgrade policies 1, 2, and 3 are delivered to System C.

[0168] System C receives degradation policies 1, 2, and 3 issued by the business label service degradation system. Taking service c1 being called by business a1 as an example, degradation policy 1 is first matched, and the number of times business a1 calls service c1 per second is counted as 1150. At this time, 1150 is greater than the TPS threshold of 1100 times / second for business a1. Business a1 meets degradation policy 1, then system C will intercept business a1's call request for service c1 to make the unit call volume of business a1 less than or equal to the TPS threshold of 1100 times / second. At the same time, the business label service degradation system will receive the corresponding degradation information and push the degradation information to the corresponding system and rule maintenance personnel.

[0169] The business tag service degradation system will also display the call information of each business, historical transaction peak, the maximum TPS value of the target service of the business, and the TPS threshold of the business on the front-end degradation policy setting page, so that rule maintenance personnel can maintain and modify the degradation policy.

[0170] It should be understood that, although the various steps in the flowcharts involved in the various embodiments described above are displayed in sequence according to the instructions of the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps can be executed in other orders. Moreover, at least a portion of the steps in the flowcharts involved in the various embodiments described above can include multiple steps or multiple stages, and these steps or stages are not necessarily executed and completed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a portion of steps or stages in other steps.

[0171] In one embodiment, Figure 1 As shown, a service degradation system is also provided, the system comprising: a first system, a service label service degradation system and a target system; wherein,

[0172] The first system is used to obtain the call information of each business through the proxy module and upload the call information of each business to the business label service degradation system. The call information includes the business label of the business, the target service called by the business, and the target system to which the target service belongs;

[0173] The service tag service degradation system is used to determine the degradation policy corresponding to each service based on the call information received from each service, and for any service, send the corresponding degradation policy to the target system in the service call information. The degradation policy is used to trigger the flow control of the service;

[0174] The target system is used to receive the degradation policies corresponding to each business issued by the business label service degradation system. When the target service is called by the target business, it matches the degradation policy corresponding to the target business and performs corresponding degradation processing on the target business according to the degradation policy corresponding to the target business to limit the number of times the target business calls the target service.

[0175] In an embodiment of the present application, an agent system can be set up in the first system, which includes various businesses. When the business starts to call the target service, the agent system can obtain the calling information of the business and upload the calling information of each business to the business label service degradation system. The calling information includes the business label of the business, the target service called by the business, and the target system to which the target service belongs.

[0176] The business tag service degradation system receives the call information of each business uploaded by the first system, and determines the degradation strategy corresponding to each business based on the call information of each business, and for any business, sends the degradation strategy corresponding to the business to the target system in the call information of the business.

[0177] Afterwards, the target system receives the degradation policy corresponding to each business. When the target service in the target system is called by the target business, subsequent processing is performed according to the degradation policy corresponding to the target business. The process is as follows: match the degradation policy corresponding to the target business, and perform corresponding degradation processing on the target business according to the degradation policy corresponding to the target business to limit the number of times the target business calls the target service.

[0178] In the embodiment of the present disclosure, the specific process of the business label service degradation system and the target system generating the degradation policy and applying the degradation policy can be referred to the relevant description of the above embodiment, and will not be repeated here in the embodiment of the present disclosure.

[0179] In an embodiment of the present application, the downgrade strategy corresponding to each business is determined through the calling information of each business, and the downgrade strategy corresponding to the business is issued to the target system in the calling information. When the target service in the target system is called by the business, the business can be downgraded accordingly according to the downgrade strategy corresponding to the business. That is, the target system can downgrade each business accordingly according to the downgrade strategy corresponding to each business, that is, the corresponding business can be downgraded in a targeted manner without downgrading the service of the application system, thereby avoiding mutual influence between businesses, maximizing the normal operation of each business, and improving the stability of the business.

[0180] Based on the same inventive concept, embodiments of the present application also provide a service degradation device for implementing the aforementioned service degradation method. The solution provided by this device is similar to the solution described in the aforementioned method. Therefore, the specific limitations of one or more service degradation device embodiments provided below can be found in the aforementioned limitations of the service degradation method and will not be further elaborated here.

[0181] In one embodiment, Figure 9 As shown, a service degradation device is provided, including: an acquisition module 902, a determination module 904 and a delivery module 906, wherein:

[0182] The acquisition module 902 is used to obtain the call information of each business, the call information including the business tag of the business, the target service called by the business, and the target system to which the target service belongs;

[0183] Determination module 904, used to determine the degradation strategy corresponding to each service based on the call information of each service, and the degradation strategy is used to trigger the flow control of the service;

[0184] The sending module 906 is used to send the corresponding degradation policy of any business to the target system in the calling information according to the calling information of the business, so that when the target service in the target system is called by the business, the target system will perform corresponding degradation processing on the business according to the corresponding degradation policy of the business.

[0185] In an embodiment of the present application, the downgrade strategy corresponding to each business is determined through the calling information of each business, and the downgrade strategy corresponding to the business is issued to the target system in the calling information. When the target service in the target system is called by the business, the business can be downgraded accordingly according to the downgrade strategy corresponding to the business. That is, the target system can downgrade each business accordingly according to the downgrade strategy corresponding to each business, that is, the corresponding business can be downgraded in a targeted manner without downgrading the service of the application system, thereby avoiding mutual influence between businesses, maximizing the normal operation of each business, and improving the stability of the business.

[0186] In one embodiment, the determining module 904 is further configured to:

[0187] For any business, the transaction attributes of the business are determined based on the business tag in the business call information. The transaction attributes are used to indicate the importance of the business.

[0188] Determine the downgrade strategy corresponding to the business based on the transaction attributes of the business and the target service in the business call information.

[0189] In one embodiment, the determining module 904 is further configured to:

[0190] For any business, determine the estimated transaction peak based on the business's historical transaction data;

[0191] Get the maximum transaction processing volume (TPS) value supported by the target service in the business call information;

[0192] Determine the TPS threshold for the business based on its transaction attributes, estimated transaction peak, and the maximum TPS value supported by the target service.

[0193] Generate a degradation strategy for the business based on the TPS threshold corresponding to the business.

[0194] In one embodiment, the determining module 904 is further configured to:

[0195] When the transaction attribute indicates that the business is of the first business type, the TPS threshold of the business is determined based on the estimated transaction peak and the maximum TPS value supported by the target service;

[0196] Alternatively, when the transaction attribute indicates that the service is of the second service type, the target TPS value is determined according to the preset ratio and the maximum TPS value supported by the target service;

[0197] Determine the TPS threshold for the business based on the estimated transaction peak and target TPS value;

[0198] The importance of the first service type is higher than the importance of the second service type.

[0199] In one embodiment, Figure 10 As shown, a service degradation device is provided, including: a receiving module 1002, a matching module 1004 and a degradation module 1006, wherein:

[0200] Receiving module 1002, used to receive the degradation policy corresponding to each service issued by the service label service degradation system. The degradation policy is determined by the service label service degradation system based on the call information of the service. The degradation policy is used to trigger the flow control of the service;

[0201] The matching module 1004 is used to match the degradation policy corresponding to the target business when the target service is called by the target business;

[0202] The degradation module 1006 is configured to perform corresponding degradation processing on the target service according to the degradation policy corresponding to the target service, so as to limit the number of calls of the target service by the target service.

[0203] In the embodiment of the present application, the target system can perform corresponding downgrade processing on each business according to the downgrade strategy corresponding to each business, that is, the corresponding business can be downgraded in a targeted manner without downgrading the service of the application system, thereby avoiding mutual influence between businesses, maximizing the normal operation of each business, and improving the stability of the business.

[0204] In one embodiment, the degradation module 1006 is further configured to:

[0205] Determine whether the target service meets its corresponding degradation policy based on the target service's unit call volume. The unit call volume is the number of times the target service calls the target service within a unit time.

[0206] When the target service meets its corresponding degradation policy, the target service is downgraded accordingly to limit the number of times the target service calls the target service.

[0207] In one embodiment, the degradation module 1006 is further configured to:

[0208] Count the number of target services called by the target business per unit time.

[0209] When the unit call volume is greater than the TPS threshold, determine that the target business meets its corresponding degradation strategy; or,

[0210] When the unit call volume is less than or equal to the TPS threshold, it is determined that the target service does not meet its corresponding degradation strategy.

[0211] Each module in the above-mentioned service degradation device can be implemented in whole or in part through software, hardware, or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in the computer device in the form of software, so that the processor can call and execute the corresponding operations of each module.

[0212] In one embodiment, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as follows: Figure 11As shown. The computer device includes a processor, a memory, a communication interface, a display screen and an input device connected via a system bus. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be achieved through WIFI, a mobile cellular network, NFC (near field communication) or other technologies. When the computer program is executed by the processor, a service degradation method is implemented. The display screen of the computer device can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covering the display screen, or a button, trackball or touchpad provided on the computer device housing, or an external keyboard, touchpad or mouse.

[0213] Those skilled in the art will understand that Figure 11 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0214] In one embodiment, a computer device is further provided, including a memory and a processor. The memory stores a computer program, and the processor implements the steps in the above method embodiments when executing the computer program.

[0215] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

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

[0217] The service degradation method, system and apparatus, computer equipment and storage medium provided in this application can be used in the financial field and the field of intelligent operation and maintenance, and can also be used in any field other than the financial field. This application does not limit the application field of the service degradation method, system and apparatus, computer equipment and storage medium.

[0218] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties.

[0219] Those skilled in the art will appreciate that all or part of the processes in the above-mentioned embodiment methods can be implemented by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, database or other media used in the embodiments provided in this application may include at least one of non-volatile and volatile memory. Non-volatile memory may include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory may include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in the various embodiments provided herein may include at least one of a relational database and a non-relational database. Non-relational databases may include, but are not limited to, distributed databases based on blockchains. The processor involved in the various embodiments provided herein may be, but are not limited to, a general-purpose processor, a central processing unit, a graphics processing unit, a digital signal processor, a programmable logic unit, a data processing logic unit based on quantum computing, and the like.

[0220] The technical features of the above embodiments can be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0221] The above-described embodiments merely represent several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present application. It should be noted that a person of ordinary skill in the art may make various modifications and improvements without departing from the spirit of the present application, and these modifications and improvements fall within the scope of protection of the present application. Therefore, the scope of protection of the present application shall be determined by the appended claims.

Claims

1. A service degradation method, characterized in that: The method comprises: Obtaining call information for each service, including the service tag of the service, the target service called by the service, and the target system to which the target service belongs. The call information is obtained by intercepting an agent deployed in the system to which the service belongs; For any of the services, determining a transaction attribute of the service according to the service tag in the call information of the service, where the transaction attribute is used to indicate the importance of the service; Determining an estimated transaction peak for the business based on historical transaction data of the business; Obtaining a maximum transaction processing volume (TPS) value supported by the target service in the call information of the business; When the transaction attribute indicates that the business is of the first business type, determining a TPS threshold for the business according to the estimated transaction peak and a maximum TPS value supported by the target service; Alternatively, when the transaction attribute indicates that the business is of the second business type, a target TPS value is determined according to a preset ratio and a maximum TPS value supported by the target service; Determining the TPS threshold of the business according to the estimated transaction peak and the target TPS value; wherein the importance of the first business type is higher than the importance of the second business type; Generating a degradation policy corresponding to the service according to the TPS threshold corresponding to the service, wherein the degradation policy is used to trigger flow limiting of the service to limit the number of calls of the service to the target service; For any of the services, based on the calling information of the service, the downgrade policy corresponding to the service is sent to the target system in the calling information, so that when the target service in the target system is called by the service, the target system performs corresponding downgrade processing on the service according to the downgrade policy corresponding to the service.

2. A service degradation method, characterized in that: The method comprises: Receive the degradation strategy corresponding to each business issued by the business tag service degradation system. For any of the businesses, the degradation strategy is determined by the business tag service degradation system based on the business tag in the call information of the business, and the transaction attribute of the business is used to indicate the importance of the business. The call information is obtained by intercepting the agent deployed in the system to which the business belongs; determine the estimated transaction peak of the business based on the historical transaction data of the business; obtain the maximum transaction processing volume TPS value supported by the target service in the call information of the business; when the transaction attribute indicates that the business is of the first business type, determine the estimated transaction peak value based on the estimated transaction peak value. The TPS threshold of the business is determined based on the transaction peak and the maximum TPS value supported by the target service; or, when the transaction attribute indicates that the business is a second business type, the target TPS value is determined based on a preset ratio and the maximum TPS value supported by the target service; the TPS threshold of the business is determined based on the estimated transaction peak and the target TPS value; wherein the importance of the first business type is higher than that of the second business type; and a degradation policy corresponding to the business is generated based on the TPS threshold corresponding to the business, wherein the degradation policy is used to trigger flow limiting of the business to limit the number of times the business calls the target business; When the target service is called by the target business, the degradation policy corresponding to the target business is matched; According to the degradation policy corresponding to the target service, the target service is subjected to corresponding degradation processing to limit the number of times the target service calls the target service.

3. The method according to claim 2, characterized in that The performing corresponding downgrading processing on the target service according to the downgrading policy corresponding to the target service to limit the number of times the target service calls the target service includes: Determining whether the target service satisfies the corresponding degradation policy based on the unit call volume of the target service, where the unit call volume is the number of times the target service calls the target service within a unit time; When the target service satisfies the corresponding degradation policy, the target service is subjected to corresponding degradation processing to limit the number of times the target service calls the target service.

4. The method according to claim 3, characterized in that The degradation policy corresponding to the target service includes a TPS threshold, and judging whether the target service satisfies the corresponding degradation policy according to the unit call volume of the target service includes: Counting the unit call volume of the target service by the target business within the unit time; When the unit call volume is greater than the TPS threshold, determining that the target service satisfies the corresponding degradation policy; or When the unit call volume is less than or equal to the TPS threshold, it is determined that the target service does not satisfy the corresponding degradation policy.

5. A service degradation system, wherein the service degradation system is used to implement the service degradation method according to any one of claims 1 to 4, characterized in that: The system includes: a first system, a service label service degradation system and a target system; wherein, The first system is configured to obtain call information of each service through a proxy module, and upload the call information of each service to the service label service degradation system, wherein the call information includes the service label of the service, the target service called by the service, and the target system to which the target service belongs; For any of the services, the service tag service degradation system is configured to determine the transaction attributes of the service based on the service tag in the call information of the service, where the transaction attributes are used to indicate the importance of the service; determine the TPS threshold corresponding to the service based on the transaction attributes of the service, the historical transaction data of the service, and the maximum transaction processing volume per second (TPS) value supported by the target service in the call information of the service; generate a degradation policy corresponding to the service based on the TPS threshold corresponding to the service to limit the number of calls made by the service to the target service, and for any of the services, send the degradation policy corresponding to the service to the target system in the call information of the service, where the degradation policy is used to trigger flow control for the service; The target system is used to receive the downgrade policy corresponding to each of the services issued by the service tag service downgrade system, match the downgrade policy corresponding to the target service when the target service is called by the target service, and perform corresponding downgrade processing on the target service according to the downgrade policy corresponding to the target service to limit the number of times the target service calls the target service.

6. A service degradation device, configured to implement the service degradation method according to any one of claims 1 to 4, characterized in that: The device comprises: An acquisition module is used to acquire call information of each service, wherein the call information includes a service tag of the service, a target service called by the service, and a target system to which the target service belongs; a determination module configured to determine, for any of the services, a transaction attribute of the service based on the service tag in the service call information, the transaction attribute being used to indicate the importance of the service; determine a TPS threshold corresponding to the service based on the transaction attribute of the service, historical transaction data of the service, and a maximum transaction processing per second (TPS) value supported by the target service in the service call information; generate a degradation strategy corresponding to the service based on the TPS threshold corresponding to the service, and determine a degradation strategy corresponding to each service, the degradation strategy being used to trigger flow limiting for the service to limit the number of times the service calls the target service; The sending module is used to send the downgrade policy corresponding to the business to the target system in the calling information for any of the businesses, based on the calling information of the business, so that when the target service in the target system is called by the business, the target system performs corresponding downgrade processing on the business according to the downgrade policy corresponding to the business.

7. A service degradation device, configured to implement the service degradation method according to any one of claims 1 to 4, characterized in that: The device comprises: A receiving module is configured to receive a degradation policy corresponding to each service issued by a service tag service degradation system. For any of the services, the degradation policy is determined by the service tag service degradation system based on the service tag in the call information of the service, wherein the transaction attribute of the service is used to indicate the importance of the service; a TPS threshold corresponding to the service is determined based on the transaction attribute of the service, the historical transaction data of the service, and the maximum transaction processing volume per second (TPS) value supported by the target service in the call information of the service; and the degradation policy is used to trigger flow limiting of the service based on the TPS threshold corresponding to the service, so as to limit the number of calls made by the service to the target service. A matching module, configured to match a degradation policy corresponding to a target service when a target service is called by the target service; The degradation module is configured to perform corresponding degradation processing on the target service according to the degradation policy corresponding to the target service, so as to limit the number of times the target service calls the target service.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 4 are implemented.

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

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

Images