Fusing method and device of cloud middleware, computer equipment and storage medium

Abstract

The invention relates to a fusing method and device of cloud middleware, computer equipment and a storage medium. The method comprises the following steps: generating label information of a processing request according to the processing request sent by user equipment; the label information is used for representing the importance degree of the processing request; determining a fusing rule corresponding to the processing request according to the label information; the fusing rule comprises a fusing threshold value and a fusing scheme corresponding to the fusing threshold value; and fusing the processing request according to the fusing scheme under the condition that the fusing threshold value is met. According to the technical scheme, the label information of the processing requests is generated according to the features of the processing requests, so that the fusing rules corresponding to the processing requests are determined according to the label information, the fusing rules of the processing requests are customized in a personalized mode, the fusing rules of the processing requests with different importance degrees are different, interruption of key services is avoided, and service stability is improved.

Description

Technical Field

[0001] This application relates to the field of cloud computing technology, and in particular, to a method, device, computer device, and storage medium for fusing a cloud middleware. Background Art

[0002] In a cloud computing environment, cloud middleware plays a crucial role. Cloud middleware can provide functions such as operation support, communication collaboration, and service governance for various cloud applications. With the rapid development of cloud services, the traffic scale faced by cloud middleware is becoming increasingly large and complex. When an exception occurs in processing a processing request received by the cloud middleware, it is necessary to fuse the processing request received by the cloud middleware.

[0003] In traditional technologies, generally, when an exception occurs in processing a processing request received by the cloud middleware, global fusing is performed. However, traditional fusing methods are likely to cause the interruption of critical business services and affect business continuity. Summary of the Invention

[0004] Based on this, it is necessary to provide a method, device, computer device, and storage medium for fusing a cloud middleware that can improve the business processing stability of the cloud middleware for the above technical problems.

[0005] In a first aspect, this application provides a method for fusing a cloud middleware, including:

[0006] Generating tag information for the processing request according to the processing request sent by the user device; the tag information is used to characterize the importance level of the processing request;

[0007] Determining a fusing rule corresponding to the processing request according to the tag information; the fusing rule includes a fusing threshold and a fusing scheme corresponding to the fusing threshold;

[0008] When the fusing threshold is met, fusing the processing request according to the fusing scheme.

[0009] In one embodiment, the method further includes:

[0010] Determining processing information corresponding to the processing request within a first preset duration; the processing information is processing information of the tag type corresponding to the processing request, and the processing information includes the number of requests, and / or, the request processing duration;

[0011] Determining whether the fusing threshold is met according to the processing information; the fusing threshold may include: the number of requests is greater than a preset number threshold, and / or, the request processing duration is greater than a preset processing duration.

[0012] In one embodiment, determining the fusing rule corresponding to the processing request according to the label information includes:

[0013] Determining the target label type corresponding to the processing request according to the label information;

[0014] Determining the fusing rule corresponding to the label type from a preset fusing rule library according to the target label type.

[0015] In one embodiment, determining the target label type corresponding to the processing request according to the label information includes:

[0016] Determining the candidate label type corresponding to the processing request according to the user information in the label information;

[0017] Determining the target label type from the candidate label types according to the service information in the label information;

[0018] Wherein, the service information includes at least one of service type, service priority, and data volume information.

[0019] In one embodiment, the method further includes:

[0020] Obtaining the status monitoring information of the cloud middleware; the status monitoring information includes processing request distribution information and system resource status information;

[0021] Optimizing the fusing rule corresponding to the processing request according to the status monitoring information to obtain an optimized fusing rule; the optimized fusing rule includes an optimized fusing threshold and an optimized fusing scheme;

[0022] Fusing the processing request according to the fusing scheme when the fusing threshold is satisfied includes:

[0023] Fusing the processing request according to the optimized fusing scheme when the optimized fusing threshold is satisfied.

[0024] In one embodiment, the method further includes:

[0025] Obtaining the traffic data of the historical processing requests corresponding to each label type within a second preset duration;

[0026] Determining the traffic change trend of each label type based on the traffic data of the historical processing requests corresponding to each label type;

[0027] Updating the fusing rules corresponding to each label type in the preset fusing rule library according to the traffic change trend of each label type.

[0028] In a second aspect, the present application further provides a fusing device for cloud middleware, including:

[0029] A generating module, configured to generate tag information of the processing request according to the processing request sent by the user device; the tag information is used to characterize the importance level of the processing request;

[0030] A first determining module, configured to determine a fusing rule corresponding to the processing request according to the tag information; the fusing rule includes a fusing threshold and a fusing scheme corresponding to the fusing threshold;

[0031] A processing module, configured to fuse the processing request according to the fusing scheme when the fusing threshold is met.

[0032] In a third aspect, the present application further provides a computer device, including a memory and a processor, where the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:

[0033] Generate tag information of the processing request according to the processing request sent by the user device; the tag information is used to characterize the importance level of the processing request;

[0034] Determine a fusing rule corresponding to the processing request according to the tag information; the fusing rule includes a fusing threshold and a fusing scheme corresponding to the fusing threshold;

[0035] Fuse the processing request according to the fusing scheme when the fusing threshold is met.

[0036] In a fourth aspect, the present application further provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

[0037] Generate tag information of the processing request according to the processing request sent by the user device; the tag information is used to characterize the importance level of the processing request;

[0038] Determine a fusing rule corresponding to the processing request according to the tag information; the fusing rule includes a fusing threshold and a fusing scheme corresponding to the fusing threshold;

[0039] Fuse the processing request according to the fusing scheme when the fusing threshold is met.

[0040] In a fifth aspect, the present application further provides a computer program product, including a computer program, and when the computer program is executed by a processor, the following steps are implemented:

[0041] Generate label information for the processing request according to the processing request sent by the user device; the label information is used to characterize the importance level of the processing request;

[0042] Determine the fusing rule corresponding to the processing request according to the label information; the fusing rule includes a fusing threshold and a fusing scheme corresponding to the fusing threshold;

[0043] When the fusing threshold is met, fuse the processing request according to the fusing scheme.

[0044] The above-mentioned fusing method, device, computer device, and storage medium of the cloud middleware generate label information for the processing request according to the processing request sent by the user device; the label information is used to characterize the importance level of the processing request; determine the fusing rule corresponding to the processing request according to the label information; the fusing rule includes a fusing threshold and a fusing scheme corresponding to the fusing threshold; when the fusing threshold is met, fuse the processing request according to the fusing scheme. First, generate label information for the processing request according to the characteristics of each processing request, and then determine the fusing rule corresponding to the processing request according to each label information, customize the fusing rules for various processing requests, so that the fusing rules for processing requests with different importance levels are different, avoiding the interruption of critical services and improving service stability. Description of the Drawings

[0045] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the following will briefly introduce the drawings required for use in the description of the embodiments of the present application or related technologies. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, without creative efforts, other related drawings can also be obtained based on these drawings.

[0046] Figure 1 It is an application environment diagram of the fusing method of the cloud middleware in one embodiment;

[0047] Figure 2 It is a flowchart of the fusing method of the cloud middleware in one embodiment;

[0048] Figure 3 It is a flowchart of the fusing method of the cloud middleware in another embodiment;

[0049] Figure 4 It is a flowchart of the fusing method of the cloud middleware in another embodiment;

[0050] Figure 5 It is a flowchart of the fusing method of the cloud middleware in another embodiment;

[0051] Figure 6Schematic flowchart of the fuse method for cloud middleware in another embodiment;

[0052] Figure 7 Schematic flowchart of the fuse method for cloud middleware in another embodiment;

[0053] Figure 8 Schematic flowchart of the fuse method for cloud middleware in another embodiment;

[0054] Figure 9 Block diagram of the fuse device for cloud middleware in one embodiment;

[0055] Figure 10 Internal structure diagram of a computer device in one embodiment. Detailed implementation manners

[0056] In order to make the objectives, technical solutions and advantages of the present application clearer and more understandable, the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0057] The fuse method for cloud middleware provided by the embodiments of the present application can be applied to an application environment as Figure 1 shown. Among them, the user device 102 communicates with the cloud middleware 104 through a network. The data storage system can store the data that the cloud middleware 104 needs to process. The data storage system can be integrated on the cloud middleware 104, or placed on the cloud or other network servers. The cloud middleware 104 receives the processing request sent by the user device 102, generates label information corresponding to the processing request according to the processing request, and thus fuses the processing request according to the label information. Among them, the user device 102 can be a terminal or a server. The terminal can be, but is not limited to, various personal computers, laptop computers, smart phones, tablet computers, Internet of Things devices and portable wearable devices. The Internet of Things devices can be smart speakers, smart TVs, smart air conditioners, smart in-vehicle devices, projection devices, etc. The portable wearable devices can be smart watches, smart bracelets, head-mounted devices, etc. The head-mounted device can be a virtual reality (VR) device, an augmented reality (AR) device, a smart glasses, etc. The cloud middleware 104 can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server providing cloud computing services.

[0058] In one embodiment, as Figure 2 shown, a fuse method for cloud middleware is provided. Taking this method applied to the cloud middleware in Figure 1 as an example for description, it includes:

[0059] S201. Generate label information for the processing request according to the processing request sent by the user device; the label information is used to characterize the importance level of the processing request.

[0060] In an embodiment of the present application, the user device may send multiple processing requests to the cloud middleware. For each processing request, the cloud middleware parses the processing request to obtain the identification information of the processing request, and thus generates the label information of the processing request according to the identification information of the processing request. Exemplarily, the label information may include first level, second level, and third level, where the first level represents the highest importance level of the processing request, and the third level represents the lowest importance level of the processing request.

[0061] Optionally, the identification information may represent the importance level of the processing request; or, the identification information may represent the basic information of the processing request, for example, label type, priority of the user device, etc.

[0062] S202. Determine the fusing rule corresponding to the processing request according to the label information; the fusing rule includes a fusing threshold and a fusing scheme corresponding to the fusing threshold.

[0063] Among them, the fusing threshold is the condition required to trigger fusing; the fusing scheme includes fusing time and fusing ratio, fusing duration and fusing ratio.

[0064] In an embodiment of the present application, the corresponding relationship between the label information and the fusing rule is stored in the cloud middleware in advance, so as to determine the fusing rule corresponding to the processing request according to the label information and this corresponding relationship.

[0065] S203. When the fusing threshold is met, fuse the processing request according to the fusing scheme.

[0066] In an embodiment of the present application, all processing requests with the same label information are regarded as the same type of processing requests. According to all the processing requests corresponding to the label information, it is determined whether this type of processing requests meets the fusing threshold. When the fusing threshold is met, fuse this type of processing requests according to the fusing duration and fusing ratio. Optionally, when the fusing threshold is met, randomly return the processing requests with the fusing ratio within the fusing duration. For example, when the fusing duration is 2s and the fusing ratio is 60%, then 60% of the processing requests received within 2s are returned for processing, that is, the cloud middleware only processes 40% of the processing requests.

[0067] In the above fuse method of cloud middleware, according to the processing request sent by the user device, tag information of the processing request is generated; the tag information is used to characterize the importance level of the processing request; according to the tag information, a fuse rule corresponding to the processing request is determined; the fuse rule includes a fuse threshold and a fuse solution corresponding to the fuse threshold; when the fuse threshold is met, the processing request is fused according to the fuse solution. First, the tag information of the processing request is generated according to the characteristics of each processing request, so as to determine the fuse rule corresponding to the processing request according to each tag information, customize the fuse rules of various processing requests, make the fuse rules of processing requests with different importance levels different, avoid the interruption of key services, and improve the service stability.

[0068] In one embodiment, as Figure 3 shown, the above fuse method of cloud middleware further includes:

[0069] S204, determining the processing information corresponding to the processing request within a first preset duration; the processing information is the processing information of the tag type corresponding to the processing request, and the processing information includes the request quantity, and / or, the request processing duration.

[0070] Wherein, the request processing is the total number of processing requests within the first preset duration; the request processing duration is the average processing duration of each processing request.

[0071] In the embodiment of the present application, the first preset duration is a preset sampling duration, and the first preset durations corresponding to each tag type may be the same or different. Those with the same note information can be of the same tag type. Determine the request quantity of the processing requests of this tag type received by the cloud middleware within the first preset duration, and / or, the average processing duration of the processing requests of this tag type.

[0072] Optionally, determine the request quantity corresponding to the processing request within the first prediction duration; or, determine the request processing duration corresponding to the processing request within the first prediction duration; or, determine the request quantity and the request processing duration corresponding to the processing request within the first prediction duration.

[0073] S205, determining whether the fuse threshold is met according to the processing information; the fuse threshold may include: the request quantity is greater than a preset quantity threshold, and / or, the request processing duration is greater than a preset processing duration.

[0074] In the embodiment of the present application, when the request quantity is greater than the preset quantity threshold, it is determined that the processing information meets the fuse threshold; or, when the request processing duration is greater than the preset processing duration, it is determined that the processing information meets the fuse threshold; or, when the request quantity is greater than the preset quantity threshold and the request processing duration is greater than the preset processing duration, it is determined that the processing information meets the fuse threshold.

[0075] In the above application embodiments, all processing requests are classified according to the label information. For each type of processing request, it is determined whether the processing information meets the fuse threshold within the first preset duration, ensuring the timeliness of fusing for the processing requests corresponding to various label types.

[0076] In one embodiment, an implementation manner of the above S202 is provided. As Figure 4 shown, the above "determine the fuse rule corresponding to the processing request according to the label information" includes:

[0077] S301, according to the label information, determine the target label type corresponding to the processing request.

[0078] In the embodiments of the present application, the cloud middleware may store the first correspondence between the label information and the label class, so as to determine the target label type corresponding to the processing request according to the label information of the processing request and the first correspondence.

[0079] S302, according to the target label type, determine the fuse rule corresponding to the label type from the preset fuse rule library.

[0080] In the embodiments of the present application, the fuse rule library includes multiple fuse rules and the second correspondence between the label type and the fuse rule. Each label type corresponds to one fuse rule, and each fuse rule may correspond to multiple label types. Thus, the fuse rule corresponding to the label type can be determined from the preset fuse rule library according to the target label type and the second correspondence.

[0081] Exemplarily, for a request with label information "critical business tenant - high priority", a corresponding higher fuse threshold is queried, allowing this type of request to still execute normally when the system load is high to ensure the continuity of critical services; while for a request with label information "ordinary business tenant - low priority", a lower fuse threshold is matched, and fusing is preferentially performed in case of abnormal traffic to release resources. This process realizes differential treatment of different traffic, avoids the drawbacks of traditional global fusing strategies, and improves the utilization efficiency of cloud middleware resources and the availability of critical services.

[0082] In the above application embodiments, the target label type corresponding to the processing request is determined according to the label information, and then the fuse rule is determined according to the target label type, improving the matching degree and accuracy between the fuse rule and the processing request.

[0083] In one embodiment, an implementation manner of the above S301 is provided. As Figure 5 shown, the above "determine the target label type corresponding to the processing request according to the label information" includes:

[0084] S401. Determine the candidate label types corresponding to the processing request according to the user information in the label information.

[0085] In the embodiments of the present application, the label information includes user information and service information. The cloud middleware can pre-store the third corresponding relationship between the user information and the label types, so that the candidate label types corresponding to the processing request can be determined first according to the user information and the third corresponding relationship. Optionally, the candidate label types may include multiple label types.

[0086] S402. Determine the target label types from the candidate label types according to the service information in the label information; where the service information includes at least one of: service type, service priority, and data volume information.

[0087] In the embodiments of the present application, the cloud middleware can pre-store the fourth corresponding relationship between the service information and the candidate label types, so as to determine the target label types from the candidate label types according to the service information and the fourth corresponding relationship.

[0088] Optionally, the first candidate label types corresponding to the processing request can be determined according to the user information in the label information, and the second candidate label types corresponding to the processing request can be determined according to the service information in the label information. The same label types in the first candidate label types and the second candidate label types are determined as the target label types.

[0089] Optionally, the third candidate label types can be determined from the candidate label types according to the service type, then the fourth candidate label types can be determined from the third candidate label types according to the service priority, and finally the target label types can be determined from the fourth candidate label types according to the data volume information.

[0090] As another alternative implementation, the candidate label types corresponding to the processing request can be determined first according to the service information in the label information, and then the target label types can be determined from the candidate label types according to the user information in the label information.

[0091] In the above embodiments of the application, all label types are first screened according to the user information in the label information to determine the candidate label types corresponding to the processing request, and then the target label types are determined from the candidate label types according to the service information in the label information, making the determination process more orderly and improving the accuracy of the target label types.

[0092] In one embodiment, as Figure 6 shown, the fuse method of the above cloud middleware further includes:

[0093] S206. Obtain the status monitoring information of the cloud middleware; the status monitoring information includes the processing request distribution information and the system resource status information.

[0094] Among them, the status monitoring information includes traffic distribution, label information, and system resource status. The system resource status may include CPU utilization, memory occupancy, network bandwidth, etc.

[0095] In the embodiments of the present application, the status monitoring information of the cloud middleware can be obtained according to a preset monitoring component.

[0096] S207, optimize the fusing rule corresponding to the processing request according to the status monitoring information to obtain an optimized fusing rule; the optimized fusing rule includes an optimized fusing threshold and an optimized fusing scheme.

[0097] In the embodiments of the present application, determine the traffic change situation of the processing request within a preset duration according to the status monitoring information, that is, the traffic change situation of the processing request in a short period of time. For example, the traffic of this type of processing request increases in a short period of time. Further, optimize the fusing rule corresponding to the processing request according to the traffic change situation of the processing request within the preset duration to obtain an optimized fusing rule.

[0098] Optionally, if the label information of the processing request indicates that the processing request is of high priority and is a key user, and when the traffic of the processing request increases within the preset duration and the system resource utilization rate approaches the set threshold, the fusing threshold of this type of request can be increased or the fusing threshold of other low-priority requests can be decreased according to factors such as the proportion of current traffic in each dimension, the growth trend, and the remaining capacity of the system resources, so as to ensure the normal operation of key services and avoid system overload.

[0099] The above S203 "in the case of meeting the fusing threshold, fuse the processing request according to the fusing scheme" includes:

[0100] S208, in the case of meeting the optimized fusing threshold, fuse the processing request according to the optimized fusing scheme.

[0101] In the embodiments of the present application, all processing requests with the same label information are regarded as the same type of processing request. According to all the processing requests corresponding to the label information, determine whether this type of processing request meets the optimized fusing threshold. In the case of meeting the optimized fusing threshold, fuse this type of processing request according to the fusing duration and the fusing ratio.

[0102] In the above embodiments of the application, optimize the fusing rule corresponding to the processing request according to the status monitoring information, so that the fusing rule can adaptively adapt to the change of traffic and the fluctuation of the system state, improve the stability and reliability of the cloud middleware, be able to respond to various emergencies in a timely manner, avoid system failures or service interruptions caused by the inadaptability of the fusing rule to the current traffic situation, and improve the flexibility and robustness of the cloud middleware.

[0103] In one embodiment, as Figure 7 shown, the circuit breaker method for the cloud middleware further includes:

[0104] S209, obtaining the traffic data of the historical processing requests corresponding to each tag type within a second preset duration.

[0105] In the embodiments of the present application, the traffic data of the historical processing requests of the cloud middleware within a second preset duration can be read from a historical database; alternatively, the cloud middleware can obtain the traffic data of the historical processing requests corresponding to each tag type within a second preset duration from other storage devices.

[0106] S210, determining the traffic change trend of each tag type based on the traffic data of the historical processing requests corresponding to each tag type.

[0107] In the embodiments of the present application, the historical traffic data of the cloud middleware is analyzed to mine the long-term trends and patterns of the traffic and evaluate the effects of the circuit breaker rules for different tags. If the number of processing requests of a certain type is greater than a preset threshold within a second preset duration and greater than the number of processing requests in the previous update cycle, it is determined that the processing requests of this type show an increasing trend; if the number of processing requests of a certain type is less than a preset threshold within a second preset duration and less than the number of processing requests in the previous update cycle, it is determined that the processing requests of this type show a decreasing trend.

[0108] S211, updating the circuit breaker rules corresponding to each tag type in the preset circuit breaker rule library according to the traffic change trend of each tag type.

[0109] In the embodiments of the present application, for each tag type, if the traffic corresponding to this tag type shows an increasing trend, the circuit breaker threshold of this tag type can be increased; if the traffic corresponding to this tag type shows a decreasing trend, the circuit breaker threshold of this tag type can be decreased.

[0110] Optionally, if the number of processing requests corresponding to any tag type is 0 within a second preset duration, this tag type is deleted; if there is an unrecorded tag type within a second preset duration, a circuit breaker rule corresponding to this tag type is generated in the rule database.

[0111] In the above embodiments of the application, the rule database is updated according to the traffic data of the historical processing requests, ensuring that the circuit breaker rules can continuously adapt to the development of the business and the changes in the traffic, continuously improving the accuracy and effectiveness of the circuit breaker rules. Through regular updates and optimizations, the circuit breaker strategy can always keep up with the times and provide long-term guarantee for the stable operation of the cloud middleware.

[0112] In one embodiment, a method for fusing a complete cloud middleware is provided, as Figure 8 shown, the above method includes:

[0113] S1. Generate label information of the processing request according to the processing request sent by the user device; the label information is used to characterize the importance level of the processing request.

[0114] S2. Determine the candidate label type corresponding to the processing request according to the user information in the label information.

[0115] S3. Determine the target label type from the candidate label types according to the service information in the label information; where the service information includes at least one of: service type, service priority, and data volume information.

[0116] S4. Determine the fusing rule corresponding to the label type from the preset fusing rule library according to the target label type; the fusing rule includes a fusing threshold and a fusing scheme corresponding to the fusing threshold.

[0117] S5. Determine the processing information corresponding to the processing request within the first preset time period; the processing information is the processing information of the label type corresponding to the processing request, and the processing information includes the number of requests, and / or, the request processing duration.

[0118] S6. Determine whether the fusing threshold is met according to the processing information; the fusing threshold may include: the number of requests is greater than the preset number threshold, and / or, the request processing duration is greater than the preset processing duration.

[0119] S7. Obtain the status monitoring information of the cloud middleware; the status monitoring information includes the request distribution information and the system resource status information.

[0120] S8. Optimize the fusing rule corresponding to the processing request according to the status monitoring information to obtain an optimized fusing rule; the optimized fusing rule includes an optimized fusing threshold and an optimized fusing scheme.

[0121] S9. When the optimized fusing threshold is met, fuse the processing request according to the optimized fusing scheme.

[0122] S10. Obtain the traffic data of the historical processing requests corresponding to each label type within the second preset time period.

[0123] S11. Determine the traffic change trend of each label type based on the traffic data of the historical processing requests corresponding to each label type.

[0124] S12. Update the fusing rules corresponding to each label type in the preset fusing rule library according to the traffic change trend of each label type.

[0125] In the above-mentioned circuit breaker method for cloud middleware, label information of a processing request is generated according to a processing request sent by a user device; the label information is used to represent the importance level of the processing request; according to the label information, a circuit breaker rule corresponding to the processing request is determined; the circuit breaker rule includes a circuit breaker threshold and a circuit breaker solution corresponding to the circuit breaker threshold; when the circuit breaker threshold is met, the processing request is circuit broken according to the circuit breaker solution. First, label information of each processing request is generated according to the characteristics of each processing request, so as to determine the circuit breaker rule corresponding to the processing request according to each piece of label information, and the circuit breaker rules for various processing requests are customized individually, so that the circuit breaker rules for processing requests of different importance levels are different, avoiding interruption of critical services and improving service stability.

[0126] It should be understood that although the steps in the flowcharts involved in the above-described embodiments are shown sequentially in the direction of the arrows, these steps are not necessarily executed sequentially in the direction of the arrows. Unless there is a clear description in this article, the execution of these steps is not strictly limited in order, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-described embodiments may include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same moment, but can be executed at different moments, and the execution order of these steps or stages is not necessarily sequential, but can be executed alternately or alternately with at least a part of other steps or steps or stages in other steps.

[0127] Based on the same inventive concept, an embodiment of the present application further provides a circuit breaker device for cloud middleware for implementing the above-mentioned circuit breaker method for cloud middleware. The solution provided by this device to solve the problem is similar to the solution described in the above method. Therefore, the specific limitations in one or more embodiments of the circuit breaker device for cloud middleware provided below can refer to the limitations on the circuit breaker method for cloud middleware in the above text, and will not be repeated here.

[0128] In one embodiment, as Figure 9 shown, a circuit breaker device for cloud middleware is provided, including: a generation module 10, a first determination module 11, and a processing module 12, where:

[0129] The generation module 10 is configured to generate label information of a processing request according to a processing request sent by a user device; the label information is used to represent the importance level of the processing request.

[0130] The first determination module 11 is configured to determine a circuit breaker rule corresponding to the processing request according to the label information; the circuit breaker rule includes a circuit breaker threshold and a circuit breaker solution corresponding to the circuit breaker threshold.

[0131] The processing module 12 is configured to circuit break the processing request according to the circuit breaker solution when the circuit breaker threshold is met.

[0132] In one embodiment, the fusing device of the above cloud middleware further includes: a second determination module and a third determination module, where:

[0133] The second determination module is configured to determine the processing information corresponding to the processing request within a first preset duration; the processing information is the processing information of the label type corresponding to the processing request, and the processing information includes the request quantity and / or the request processing duration.

[0134] The third determination module is configured to determine whether the fusing threshold is met according to the processing information; the fusing threshold may include: the request quantity is greater than a preset quantity threshold, and / or the request processing duration is greater than a preset processing duration.

[0135] In one embodiment, the above first determination module 11 includes: a first determination unit and a second determination unit, where:

[0136] The first determination unit is configured to determine the target label type corresponding to the processing request according to the label information.

[0137] The second determination unit is configured to determine the fusing rule corresponding to the label type from a preset fusing rule library according to the target label type.

[0138] In one embodiment, the above first determination unit is specifically configured to determine the candidate label type corresponding to the processing request according to the user information in the label information; and determine the target label type from the candidate label types according to the service information in the label information; where the service information includes at least one of service type, service priority, and data volume information.

[0139] In one embodiment, the fusing device of the above cloud middleware further includes: a first acquisition module and an optimization module, where:

[0140] The first acquisition module is configured to acquire the status monitoring information of the cloud middleware; the status monitoring information includes the request distribution information and the system resource status information.

[0141] The optimization module is configured to optimize the fusing rule corresponding to the processing request according to the status monitoring information to obtain an optimized fusing rule; the optimized fusing rule includes an optimized fusing threshold and an optimized fusing scheme.

[0142] The processing module is specifically configured to fuse the processing request according to the optimized fusing scheme when the optimized fusing threshold is met.

[0143] In one embodiment, the fusing device of the above cloud middleware further includes: a second acquisition module, a fourth determination module, and an update module, where:

[0144] A second acquisition module, configured to acquire traffic data of historical processing requests corresponding to each tag type within a second preset duration.

[0145] A fourth determination module, configured to determine the traffic change trend of each tag type based on the traffic data of historical processing requests corresponding to each tag type.

[0146] An update module, configured to update the fuse rules corresponding to each tag type in a preset fuse rule library according to the traffic change trend of each tag type.

[0147] Each module in the above fuse device of the cloud middleware can be implemented in whole or in part by software, hardware, and their combination. The above modules can be embedded in the processor of the computer device in hardware form or be independent of it, or can be stored in the memory of the computer device in software form, so that the processor can call and execute the operations corresponding to the above respective modules.

[0148] In an exemplary embodiment, a computer device is provided. The computer device can be a server, and its internal structural diagram can be as Figure 10 shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, abbreviated as I / O), and a communication interface. Among them, the processor, the memory, and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. Among them, 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, a computer program, and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store the fuse data of the cloud middleware. The input / output interface of the computer device is used for the processor to exchange information with external devices. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, it implements a fuse method for cloud middleware.

[0149] Those skilled in the art can understand that Figure 10 the structure shown in

[0150] 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 those shown in the figure, or combine some components, or have a different component layout.

[0151] Generate label information for the processing request according to the processing request sent by the user device; the label information is used to characterize the importance level of the processing request;

[0152] Determine the fusing rule corresponding to the processing request according to the label information; the fusing rule includes a fusing threshold and a fusing scheme corresponding to the fusing threshold;

[0153] Fuse the processing request according to the fusing scheme when the fusing threshold is met.

[0154] In one embodiment, when the processor executes the computer program, the following steps are further implemented:

[0155] Determine the processing information corresponding to the processing request within the first preset duration; the processing information is the processing information of the label type corresponding to the processing request, and the processing information includes the request quantity, and / or, the request processing duration;

[0156] Determine whether the fusing threshold is met according to the processing information; the fusing threshold may include: the request quantity is greater than the preset quantity threshold, and / or, the request processing duration is greater than the preset processing duration.

[0157] In one embodiment, when the processor executes the computer program, the following steps are further implemented:

[0158] Determine the target label type corresponding to the processing request according to the label information;

[0159] Determine the fusing rule corresponding to the label type from the preset fusing rule library according to the target label type.

[0160] In one embodiment, when the processor executes the computer program, the following steps are further implemented:

[0161] Determine the candidate label type corresponding to the processing request according to the user information in the label information;

[0162] Determine the target label type from the candidate label types according to the service information in the label information;

[0163] Wherein, the service information includes at least one of: service type, service priority, and data volume information.

[0164] In one embodiment, when the processor executes the computer program, the following steps are further implemented:

[0165] Obtain the status monitoring information of the cloud middleware; the status monitoring information includes the processing request distribution information and the system resource status information;

[0166] Optimize the fusing rule corresponding to the processing request according to the status monitoring information to obtain an optimized fusing rule; the optimized fusing rule includes an optimized fusing threshold and an optimized fusing scheme;

[0167] When the fusing threshold is met, fusing the processing request according to the fusing scheme, including:

[0168] When the optimized fusing threshold is met, fusing the processing request according to the optimized fusing scheme.

[0169] In one embodiment, when the processor executes the computer program, the following steps are further implemented:

[0170] Obtain the traffic data of the historical processing requests corresponding to each tag type within a second preset duration;

[0171] Based on the traffic data of the historical processing requests corresponding to each tag type, determine the traffic change trend of each tag type;

[0172] According to the traffic change trend of each tag type, update the fusing rules corresponding to each tag type in the preset fusing rule library.

[0173] 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 following steps are implemented:

[0174] Generate tag information of the processing request according to the processing request sent by the user device; the tag information is used to characterize the importance level of the processing request;

[0175] Determine the fusing rule corresponding to the processing request according to the tag information; the fusing rule includes a fusing threshold and a fusing scheme corresponding to the fusing threshold;

[0176] When the fusing threshold is met, fuse the processing request according to the fusing scheme.

[0177] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0178] Determine the processing information corresponding to the processing request within a first preset duration; the processing information is the processing information of the tag type corresponding to the processing request, and the processing information includes the number of requests, and / or, the request processing duration;

[0179] Determine whether the fusing threshold is met according to the processing information; the fusing threshold may include: the number of requests is greater than a preset number threshold, and / or, the request processing duration is greater than a preset processing duration.

[0180] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0181] Determine the target tag type corresponding to the processing request according to the tag information;

[0182] Determine the fusing rule corresponding to the label type from a preset fusing rule library according to the target label type.

[0183] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0184] Determine the candidate label type corresponding to the processing request according to the user information in the label information;

[0185] Determine the target label type from the candidate label types according to the service information in the label information;

[0186] Among them, the service information includes at least one of the following: service type, service priority, and data volume information.

[0187] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0188] Obtain the status monitoring information of the cloud middleware; the status monitoring information includes the processing request distribution information and the system resource status information;

[0189] Optimize the fusing rule corresponding to the processing request according to the status monitoring information to obtain an optimized fusing rule; the optimized fusing rule includes an optimized fusing threshold and an optimized fusing scheme;

[0190] When the fusing threshold is met, fuse the processing request according to the fusing scheme, including:

[0191] When the optimized fusing threshold is met, fuse the processing request according to the optimized fusing scheme.

[0192] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0193] Obtain the traffic data of the historical processing requests corresponding to each label type within a second preset time period;

[0194] Based on the traffic data of the historical processing requests corresponding to each label type, determine the traffic change trend of each label type;

[0195] Update the fusing rules corresponding to each label type in the preset fusing rule library according to the traffic change trend of each label type.

[0196] In one embodiment, a computer program product is provided, including a computer program, and when the computer program is executed by a processor, the following steps are implemented:

[0197] Generate label information for the processing request according to the processing request sent by the user device; the label information is used to characterize the importance level of the processing request;

[0198] Determine the fuse rule corresponding to the processing request according to the tag information; the fuse rule includes a fuse threshold and a fuse scheme corresponding to the fuse threshold;

[0199] When the fuse threshold is met, fuse the processing request according to the fuse scheme.

[0200] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0201] Determine the processing information corresponding to the processing request within a first preset duration; the processing information is the processing information of the tag type corresponding to the processing request, and the processing information includes the number of requests, and / or, the request processing duration;

[0202] Determine whether the fuse threshold is met according to the processing information; the fuse threshold may include: the number of requests is greater than a preset number threshold, and / or, the request processing duration is greater than a preset processing duration.

[0203] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0204] Determine the target tag type corresponding to the processing request according to the tag information;

[0205] Determine the fuse rule corresponding to the tag type from the preset fuse rule library according to the target tag type.

[0206] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0207] Determine the candidate tag type corresponding to the processing request according to the user information in the tag information;

[0208] Determine the target tag type from the candidate tag types according to the service information in the tag information;

[0209] Among them, the service information includes at least one of: service type, service priority, and data volume information.

[0210] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0211] Obtain the status monitoring information of the cloud middleware; the status monitoring information includes the request distribution information and the system resource status information;

[0212] Optimize the fuse rule corresponding to the processing request according to the status monitoring information to obtain an optimized fuse rule; the optimized fuse rule includes an optimized fuse threshold and an optimized fuse scheme;

[0213] When the fuse threshold is met, fusing the processing request according to the fuse scheme includes:

[0214] When the optimized fusing threshold is satisfied, fuse the processing requests according to the optimized fusing scheme.

[0215] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0216] Obtain the traffic data of the historical processing requests corresponding to each label type within a second preset duration;

[0217] Based on the traffic data of the historical processing requests corresponding to each label type, determine the traffic change trend of each label type;

[0218] According to the traffic change trend of each label type, update the fusing rules corresponding to each label type in the preset fusing rule library.

[0219] Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be completed by instructing relevant hardware through a computer program. 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 methods. Among them, any reference to a memory, database, or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc. The databases involved in the embodiments provided in the present application can include at least one of relational databases and non-relational databases. Non-relational databases can include distributed databases based on blockchain, etc., without limitation. The processors involved in the embodiments provided in the present application can be general-purpose processors, central processors, graphics processors, digital signal processors, programmable logic devices, data processing logics based on quantum computing, artificial intelligence (AI) processors, etc., without limitation.

[0220] The technical features of the above embodiments can be combined arbitrarily. For the sake of concise description, 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, it should be considered as the scope recorded in the present application.

[0221] The above-described embodiments merely represent several implementation manners of the present application. The description thereof is relatively specific and detailed, but it should not be construed as a limitation on the patent scope of the present application. It should be noted that for those of ordinary skill in the art, without departing from the concept of the present application, several modifications and improvements can still be made, and these all fall within the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the appended claims.

Claims

1. A circuit-breaking method for cloud middleware, characterized in that The method includes: Generating tag information of the processing request according to the processing request sent by the user device; the tag information is used to characterize the importance level of the processing request; Determining a fusing rule corresponding to the processing request according to the tag information; the fusing rule includes a fusing threshold and a fusing scheme corresponding to the fusing threshold; When the fusing threshold is satisfied, fusing the processing request according to the fusing scheme.

2. The method according to claim 1, wherein The method further includes: Determining processing information corresponding to the processing request within a first preset duration; the processing information is processing information of the tag type corresponding to the processing request, and the processing information includes the number of requests and / or the request processing duration; Determining whether the fusing threshold is satisfied according to the processing information; the fusing threshold may include: the number of requests is greater than a preset number threshold, and / or the request processing duration is greater than a preset processing duration.

3. The method according to claim 1, characterized in that, The determining, according to the tag information, a fusing rule corresponding to the processing request includes: Determining a target tag type corresponding to the processing request according to the tag information; Determining a fusing rule corresponding to the tag type from a preset fusing rule library according to the target tag type.

4. The method according to claim 3, wherein The determining, according to the tag information, a target tag type corresponding to the processing request includes: Determining a candidate tag type corresponding to the processing request according to the user information in the tag information; Determining the target tag type from the candidate tag types according to the service information in the tag information; Wherein, the service information includes at least one of service type, service priority and data volume information.

5. The method according to any one of claims 1-4, characterized in that, The method further includes: Obtaining status monitoring information of the cloud middleware; the status monitoring information includes processing request distribution information and system resource status information; Optimizing the fusing rule corresponding to the processing request according to the status monitoring information to obtain an optimized fusing rule; the optimized fusing rule includes an optimized fusing threshold and an optimized fusing scheme; The fusing the processing request according to the fusing scheme when the fusing threshold is satisfied includes: When the optimized fusing threshold is satisfied, fusing the processing request according to the optimized fusing scheme.

6. The method according to any one of claims 1-4, characterized in that, The method further includes: Obtaining traffic data of historical processing requests corresponding to each tag type within a second preset duration; Determining the traffic change trend of each tag type based on the traffic data of historical processing requests corresponding to each tag type; Updating the fusing rules corresponding to each tag type in the preset fusing rule library according to the traffic change trend of each tag type.

7. A fuse device for cloud middleware, characterized in that, The apparatus includes: A generating module, configured to generate tag information of the processing request according to the processing request sent by the user device; the tag information is used to characterize the importance level of the processing request; A first determining module, configured to determine a fusing rule corresponding to the processing request according to the tag information; the fusing rule includes a fusing threshold and a fusing scheme corresponding to the fusing threshold; A processing module, configured to perform fusing on the processing request according to the fusing scheme when the fusing threshold is met.

8. A computer device, comprising a memory and a processor, the memory storing a computer program, characterized in that, When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 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 6 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 6 are implemented.

Images