Service interface traffic control method, apparatus, device, medium, and program product

Abstract

The present disclosure provides a service interface traffic control method, which can be applied to the technical field of computers and the technical field of financial technology. The service interface traffic control method comprises the following steps: obtaining interface information of a plurality of service interfaces respectively configured on different service nodes and having the same function, and resource consumption data of the service nodes respectively, wherein the interface information at least comprises response time length of the service interface and requested data; determining abnormal interfaces and normal interfaces from the plurality of service interfaces according to the response time length; determining a target service node from a second service node according to first resource consumption data of a first service node and second resource consumption data of the second service node, wherein the first service node corresponds to the abnormal interfaces, and the second service node corresponds to the normal interfaces; calculating allocated traffic to be migrated to each target service node according to the requested data of the abnormal interfaces and target resource consumption data of the target service node; and migrating part or all of the requested data on the first service node to the target service node according to the allocated traffic. The present disclosure further provides a service interface traffic control device, equipment, a storage medium and a program product.

Description

Service interface flow control methods, devices, equipment, media and program products Technical Field

[0001] This disclosure relates to the fields of computer technology and financial technology, specifically to a service interface traffic control method, apparatus, device, medium, and program product. Background Technology

[0002] In a microservices architecture, a complete business transaction typically requires the collaboration of multiple independent microservice nodes. These microservice nodes interact with other service nodes through interfaces with specific functions to provide diverse services to the entire system. Different functional interfaces correspond to different business capabilities of the service nodes, and the design and implementation of these interfaces directly affect the accessibility and availability of the service nodes.

[0003] In the process of realizing the present invention, the inventors discovered the following problems in the related technology: when a certain interface of a certain node in the transaction chain becomes a bottleneck, the time for that interface to process requests increases, resulting in a slower execution speed of the entire transaction; and the throughput of that interface is limited, which may prevent it from processing a large number of concurrent requests in a timely manner, resulting in requests accumulating in the queue. Summary of the Invention

[0004] In view of the above problems, this disclosure provides a service interface traffic control method, apparatus, device, medium and program product.

[0005] According to a first aspect of this disclosure, a service interface traffic control method is provided, comprising: acquiring interface information of multiple service interfaces configured on different service nodes and having the same function, and resource consumption data of each service node, wherein the interface information includes at least the response time and requested data of the service interface; determining abnormal interfaces and normal interfaces from the multiple service interfaces based on the response time; determining target service nodes from the second service nodes based on the first resource consumption data of the first service node and the second resource consumption data of the second service node, wherein the first service node corresponds to the abnormal interface and the second service node corresponds to the normal interface; calculating the allocated traffic to be migrated to each target service node based on the requested data of the abnormal interface and the target resource consumption data of the target service node; and migrating part or all of the requested data on the first service node to the target service node based on the allocated traffic.

[0006] According to embodiments of this disclosure, the resource consumption data includes at least the resource consumption amount. Determining a target service node from the second service nodes based on the first resource consumption data of the first service node and the second resource consumption data of the second service node includes: calculating the resource consumption amount corresponding to each service node based on the resource consumption data; and determining the second service node whose second resource consumption amount is less than or equal to the first threshold as the target service node when the average value of the first resource consumption amount is greater than a first threshold and the first resource consumption amount is greater than the second resource consumption amount.

[0007] According to embodiments of this disclosure, the allocation traffic to be migrated to each target service node is calculated based on the requested data of the abnormal interface and the target resource consumption data of the target service node, including: determining the allocation ratio to be migrated to the target service node based on the requested data of the abnormal interface; and calculating the allocation traffic to be migrated to each target service node based on the allocation ratio and the second resource consumption data.

[0008] According to embodiments of this disclosure, calculating the allocated traffic to be migrated to each target service node based on the allocation ratio and the second resource consumption data includes: calculating the resource ratio of each target service node among multiple target service nodes based on the target resource consumption data; and determining the allocated traffic to be migrated to each target service node based on the allocation ratio and the resource ratio.

[0009] According to embodiments of this disclosure, determining abnormal interfaces and normal interfaces from multiple service interfaces based on response duration includes: determining service interfaces that meet a first predetermined discrimination condition as abnormal interfaces and service interfaces that do not meet the first predetermined discrimination condition as normal interfaces, wherein the first predetermined discrimination condition includes: under predetermined time conditions, the first response duration of the abnormal interface is greater than a second threshold, and the first response duration is greater than or equal to the second response duration of each normal interface.

[0010] According to embodiments of this disclosure, after migrating some or all of the requested data on the first service node to the target service node, the method further includes: monitoring the response time of the abnormal interface; if the abnormal interface does not recover to a normal interface, recalculating the allocated traffic to be migrated to each target service node; and if the abnormal interface recovers to a normal interface, switching some or all of the requested data back to the first service node.

[0011] According to embodiments of this disclosure, when an abnormal interface recovers to a normal interface, some or all of the requested data is switched back to the first service node, including: switching back some or all of the requested data that has been migrated from the first service node to the first service node in batches and generating a switchback result; and determining, based on the switchback result, that the abnormal interface maintains a normal interface state.

[0012] A second aspect of this disclosure provides a service interface traffic control device, comprising: an acquisition module, configured to acquire interface information of multiple service interfaces configured on different service nodes and having the same function, and resource consumption data of each service node, wherein the interface information includes at least the response time and requested data of the service interface; a first determination module, configured to determine abnormal interfaces and normal interfaces from the multiple service interfaces based on the response time; a second determination module, configured to determine target service nodes from the second service nodes based on the first resource consumption data of the first service node and the second resource consumption data of the second service node, wherein the first service node corresponds to the abnormal interface and the second service node corresponds to the normal interface; a first calculation module, configured to calculate the allocated traffic to be migrated to each target service node based on the requested data of the abnormal interface and the target resource consumption data of the target service node; and a migration module, configured to migrate part or all of the requested data on the first service node to the target service node based on the allocated traffic.

[0013] A third aspect of this disclosure provides an electronic device comprising: one or more processors; and a memory for storing one or more computer programs, wherein the one or more processors execute the one or more computer programs to implement the steps of the method described above.

[0014] A fourth aspect of this disclosure also provides a computer-readable storage medium having a computer program or instructions stored thereon, which, when executed by a processor, implement the steps of the above-described method.

[0015] The fifth aspect of this disclosure also provides a computer program product, including a computer program or instructions that, when executed by a processor, implement the steps of the above-described method.

[0016] According to embodiments of this disclosure, by monitoring the response time of service interfaces, abnormal interfaces and their respective service nodes can be accurately located. Furthermore, since the processing time for requests from abnormal interfaces increases, the allocation of system resources can be dynamically adjusted by migrating the request volume from abnormal interfaces to target service nodes of other interfaces capable of receiving a portion of the request volume. This avoids performance degradation or unavailability of the entire system due to problems with a single node, achieving interface-level load balancing while improving the response speed of each interface to meet user needs and experience.

[0017] On the other hand, traditional service interface traffic control uses mechanisms such as rate limiting, degradation, and circuit breaking to restrict requests. This is achieved by rejecting requests exceeding a threshold or simply returning responses without processing them, thus ensuring interface normal operation under high concurrency. However, when the number of interface requests surges, methods like circuit breaking, rate limiting, and degradation can prevent requests exceeding the threshold from proceeding, leading to transaction failures. To avoid these technical problems, this disclosure adopts a more flexible and dynamic approach. When an anomaly is detected in an interface, instead of simply limiting the request volume, it remotely calls an upper-level node via an RPC framework to send instructions. The upper-level node can then quickly transfer some requests from the abnormal interface to other normal nodes based on this information. Compared to the traditional methods of limiting and ignoring requests through rate limiting, degradation, and circuit breaking, this disclosure can process more business requests in the same amount of time while ensuring system stability and proactively mitigating the risk of abnormal interface failures without the user's awareness. Attached Figure Description

[0018] The foregoing contents, as well as other objects, features, and advantages of this disclosure, will become clearer from the following description of embodiments with reference to the accompanying drawings, in which:

[0019] Figure 1 schematically illustrates an exemplary system architecture that can be applied to the service interface traffic control method and apparatus of this disclosure;

[0020] Figure 2 schematically illustrates a flowchart of a service interface traffic control method according to an embodiment of the present disclosure;

[0021] Figure 3 schematically illustrates a flowchart of a method for requesting data rollback according to an embodiment of the present disclosure;

[0022] Figure 4 schematically illustrates a flowchart of a service interface traffic control method according to another embodiment of the present disclosure;

[0023] Figure 5 schematically illustrates a structural block diagram of a service interface traffic control device according to an embodiment of the present disclosure;

[0024] Figure 6 schematically illustrates a block diagram of an electronic device suitable for implementing a service interface flow control method according to an embodiment of the present disclosure. Detailed Implementation

[0025] The embodiments of the present disclosure will now be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the disclosure. In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the embodiments of the present disclosure for ease of explanation. However, it will be apparent that one or more embodiments may be practiced without these specific details. Furthermore, descriptions of well-known structures and techniques are omitted in the following description to avoid unnecessarily obscuring the concepts of the present disclosure.

[0026] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit this disclosure. The terms “comprising,” “including,” etc., as used herein indicate the presence of the stated features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.

[0027] All terms used herein (including technical and scientific terms) have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein are to be interpreted in a manner consistent with the context of this specification, and not in an idealized or overly rigid way.

[0028] When using expressions such as "at least one of A, B and C", they should generally be interpreted in accordance with the meaning that is commonly understood by those skilled in the art (e.g., "a system having at least one of A, B and C" should include, but is not limited to, a system having A alone, a system having B alone, a system having C alone, a system having A and B, a system having A and C, a system having B and C, and / or a system having A, B and C, etc.).

[0029] In the embodiments disclosed herein, user authorization or consent is obtained before acquiring or collecting user personal information.

[0030] The service interface flow control method and apparatus disclosed herein can be used in the fields of computer technology and financial technology, and can also be used in any field other than the fields of computer technology and financial technology. The application fields of the service interface flow control method and apparatus disclosed herein are not limited.

[0031] It should be noted that in the embodiments disclosed herein, certain software, components, models, and other existing solutions in the industry may be mentioned. These should be considered as exemplary and are intended only to illustrate the feasibility of implementing the technical solutions disclosed herein. However, they do not mean that the applicant has used or necessarily used such solutions.

[0032] In the technical solution disclosed herein, the user information (including but not limited to user personal information, user image information, user device information, such as location information) and data (including but not limited to data used for analysis, stored data, and displayed data) involved are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, storage, use, processing, transmission, provision, disclosure, and application of related data all comply with relevant laws, regulations, and standards, necessary confidentiality measures have been taken, and they do not violate public order and good morals. Corresponding operation entry points are provided for users to choose to authorize or refuse.

[0033] In scenarios involving automated decision-making using personal information, the methods, devices, and systems provided in this disclosure all offer users corresponding entry points for choosing to agree to or reject the automated decision-making results. If the user chooses to reject, the process proceeds to the expert decision-making stage. Here, "automated decision-making" refers to the activity of automatically analyzing and evaluating an individual's behavioral habits, interests, or economic, health, and credit status through computer programs, and then making a decision. Here, "expert decision-making" refers to the activity of making decisions by personnel who specialize in a particular field, possess specialized experience, knowledge, and skills, and have reached a certain level of professional expertise.

[0034] In a transaction chain, for example, interface A on node 1 experiences a bottleneck for a certain period of time, meaning that the interface's resource consumption approaches or reaches its maximum capacity during this time. For instance, the service corresponding to interface A might be handling a large number of requests, with CPU utilization consistently above 90%, memory usage nearing the physical memory limit, or network bandwidth being heavily consumed, all leading to slower data transmission speeds. However, because the system's monitoring and protection mechanisms fail to detect this problem in time, or because the trigger threshold is set too high, the interface remains available, and no service degradation or rate limiting mechanisms are triggered. Meanwhile, the same interface A on other nodes (nodes 2 and 2) responds normally, and resource usage is also normal.

[0035] Because interface A on node 1 is experiencing a bottleneck, while the same interface on other nodes is functioning normally, this creates a risk of service interfaces becoming unavailable even when idle resources exist. Due to the locality of the problem and the lack of triggered protection mechanisms, the system cannot accurately identify and handle this situation, making it difficult to manage service interfaces in a granular manner. In other words, the system cannot automatically redirect some requests to the same interface on other nodes, or adjust the resource allocation of the interface according to the actual situation to alleviate the bottleneck problem.

[0036] To at least partially solve the above-mentioned technical problems, embodiments of this disclosure provide a service interface traffic control method, comprising: acquiring interface information of multiple service interfaces configured on different service nodes and having the same function, and resource consumption data of each service node, wherein the interface information includes at least the response time and requested data of the service interface; determining abnormal interfaces and normal interfaces from the multiple service interfaces based on the response time; determining target service nodes from the second service nodes based on the first resource consumption data of the first service node and the second resource consumption data of the second service node, wherein the first service node corresponds to the abnormal interface and the second service node corresponds to the normal interface; calculating the allocated traffic to be migrated to each target service node based on the requested data of the abnormal interface and the target resource consumption data of the target service node; and migrating part or all of the requested data on the first service node to the target service node based on the allocated traffic.

[0037] Figure 1 schematically illustrates an application scenario diagram of service interface traffic control according to an embodiment of the present disclosure.

[0038] As shown in Figure 1, the application scenario 100 according to this embodiment may include terminal devices 101, 102, and 103, a network 104, and a server 105. The network 104 serves as a medium for providing communication links between the first terminal device 101, the second terminal device 102, the third terminal device 103, and the server 105. The network 104 may include various connection types, such as wired or wireless communication links, or fiber optic cables, etc.

[0039] Users can interact with server 105 via network 104 using at least one of the first terminal device 101, second terminal device 102, and third terminal device 103 to receive or send messages, etc. Various communication client applications can be installed on the first terminal device 101, second terminal device 102, and third terminal device 103, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social media platform software, etc. (for example only).

[0040] The first terminal device 101, the second terminal device 102, and the third terminal device 103 can be various electronic devices with displays and support web browsing, including but not limited to smartphones, tablets, laptops, and desktop computers.

[0041] Server 105 can be a server that provides various services, such as a backend management server that supports websites browsed by users using the first terminal device 101, the second terminal device 102, and the third terminal device 103 (this is just an example). The backend management server can analyze and process data such as received user requests, and feed back the processing results (such as web pages, information, or data obtained or generated according to user requests) to the terminal devices.

[0042] It should be noted that the test data generation method provided in this embodiment can generally be executed by server 105. Correspondingly, the test data generation device provided in this embodiment can generally be located in server 105. The test data generation method provided in this embodiment can also be executed by a server or server cluster that is different from server 105 and capable of communicating with the first terminal device 101, the second terminal device 102, the third terminal device 103, and / or server 105. Correspondingly, the test data generation device provided in this embodiment can also be located in a server or server cluster that is different from server 105 and capable of communicating with the first terminal device 101, the second terminal device 102, the third terminal device 103, and / or server 105.

[0043] It should be understood that the number of terminal devices, networks, and servers shown in Figure 1 is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0044] The test data generation method of the disclosed embodiment will be described in detail below based on the scenario described in Figure 1, with reference to Figures 2 to 6.

[0045] Figure 2 schematically illustrates a flowchart of a service interface traffic control method according to an embodiment of the present disclosure.

[0046] As shown in Figure 2, the service interface traffic control in this embodiment includes operations S210 to S250.

[0047] In operation S210, the interface information of multiple service interfaces configured on different service nodes and having the same function, as well as the resource consumption data of each service node, are obtained. The interface information includes at least the response time of the service interface and the requested data.

[0048] According to embodiments of this disclosure, a full-link application monitoring platform is used to continuously monitor and evaluate the performance, status, and resource usage of interfaces, and to obtain interface information. The interface information includes at least the requested data for the interface, the name of the current-level interface, the request path of the current-level interface, the response time of the current-level interface, the Internet Protocol address (IP address) of the current-level interface node; the Internet Protocol address (IP address) of the peer node of the interface; the name of the parent interface; and the Internet Protocol address (IP address) of the parent node of the interface.

[0049] According to embodiments of this disclosure, resource consumption data of service nodes are obtained through a bypass monitoring device. Data indicators include: CPU utilization; memory utilization; disk I / O utilization, etc.

[0050] According to embodiments of this disclosure, after obtaining interface information and resource consumption data, the aforementioned information and data are persisted to the storage module in the form of time-series data.

[0051] When operating S220, based on the response time, the abnormal and normal interfaces are determined from multiple service interfaces.

[0052] According to embodiments of this disclosure, before determining abnormal and normal interfaces based on response duration, the requested quantity and requested quantity threshold in the requested data of the interface can be compared. When the requested quantity is greater than the requested quantity threshold, the abnormal and normal interfaces can be determined based on response duration.

[0053] According to an embodiment of this disclosure, one implementation method may be to set a response duration threshold, and determine the interface as an abnormal interface if the response duration of the interface is greater than the response duration threshold; and determine the interface as an abnormal interface if the response duration of the interface is less than or equal to the response duration threshold.

[0054] According to embodiments of this disclosure, an abnormal interface is defined as an interface that, although experiencing longer response times and increased resource consumption, does not reach the state where preset service mechanisms such as rate limiting, degradation, or circuit breaking are triggered. Furthermore, through embodiments of this disclosure, traffic control can be performed on the interface in advance during this abnormal state to avoid triggering rate limiting, degradation, or circuit breaking mechanisms, which could lead to the inability to process requests. This reduces the risk of service unavailability and improves service robustness.

[0055] In operation S230, based on the first resource consumption data of the first service node and the second resource consumption data of the second service node, the target service node is determined from the second service node, wherein the first service node corresponds to the abnormal interface and the second service node corresponds to the normal interface.

[0056] According to embodiments of this disclosure, the service node corresponding to the abnormal interface is a first service node, and the service node corresponding to the normal interface is a second service node. Either the first service node or the second service node can be one or more. Embodiments of this disclosure use one first service node (one abnormal interface) and multiple second service nodes (multiple normal interfaces) as an example for illustration.

[0057] According to embodiments of this disclosure, the second service node is used to indicate that the interface configured on the service node is in a normal state and does not require abnormal monitoring. However, not all normal interfaces are idle, that is, not all normal interfaces can share the request volume of abnormal interfaces.

[0058] According to embodiments of this disclosure, a target service node is used to characterize an interface that can share some or all of the request volume on an abnormal interface among normal nodes, and its idle state can be preliminarily determined based on second resource consumption data. Specifically, one implementation method may determine the target service node by comparing the second resource consumption data with a set resource consumption threshold.

[0059] In operation S240, based on the requested data of the abnormal interface and the target resource consumption data of the target service node, the allocated traffic to be migrated to each target service node is calculated.

[0060] According to embodiments of this disclosure, after determining the target service nodes that can share the request volume on the abnormal interface, it is necessary to determine the amount of requests that each target service node can receive, i.e., the traffic allocation.

[0061] According to the embodiments of this disclosure, even when there is only one target service node, the entire amount of requests to be allocated cannot be directly migrated to one target service node. Instead, it is necessary to determine whether the target service node can receive requests or to determine the amount of requests that can be received based on the target service resources of the target service node.

[0062] In operation S250, based on the allocated traffic, some or all of the requested data on the first service node is migrated to the target service node.

[0063] According to embodiments of this disclosure, based on the calculated allocated traffic to be migrated to each target service node, some or all of the requested data on the first service node is migrated to the target service nodes. Specifically, this includes steps 11 to 13.

[0064] In step 11, obtain the IP address of the local interface node where the abnormal interface is located, the IP address of the target service node, and the IP address of the parent interface node.

[0065] In step 12, an instruction containing the IP address of the abnormal interface node, the IP address of the target service node, the allocated traffic, and the interface request path is sent to the IP address of the superior interface node.

[0066] In step 13, after receiving this instruction, the upper-level interface node IP can make decisions and coordinate based on the information in the instruction.

[0067] For example, the upstream interface node IP can determine the specific location of the problem based on the IP of the abnormal interface node. Then, based on the target service node IP and traffic allocation, a portion of the requests are transferred from the abnormal interface to the target service node. Simultaneously, the interface request path is used to ensure that requests are correctly routed to the corresponding interface on the target service node. This effectively handles interface anomalies without affecting the normal operation of the entire system, improving system reliability and performance.

[0068] According to embodiments of this disclosure, instructions are sent to the superior node via a remote procedure call (RPC) framework.

[0069] According to embodiments of this disclosure, by monitoring the response time of service interfaces, abnormal interfaces and their respective service nodes can be accurately located. Furthermore, since the processing time for requests from abnormal interfaces increases, the allocation of system resources can be dynamically adjusted by migrating the request volume from abnormal interfaces to target service nodes of other interfaces capable of receiving a portion of the request volume. This avoids performance degradation or unavailability of the entire system due to problems with a single node, achieving interface-level load balancing while improving the response speed of each interface to meet user needs and experience.

[0070] On the other hand, traditional service interface traffic control uses mechanisms such as rate limiting, degradation, and circuit breaking to restrict requests. This is achieved by rejecting requests exceeding a threshold or simply returning responses without processing them, thus ensuring interface normal operation under high concurrency. However, when the number of interface requests surges, methods like circuit breaking, rate limiting, and degradation can prevent requests exceeding the threshold from proceeding, leading to transaction failures. To avoid these technical problems, this disclosure adopts a more flexible and dynamic approach. When an anomaly is detected in an interface, instead of simply limiting the request volume, it remotely calls an upper-level node via an RPC framework to send instructions. The upper-level node can then quickly transfer some requests from the abnormal interface to other normal nodes based on this information. Compared to the traditional methods of limiting and ignoring requests through rate limiting, degradation, and circuit breaking, this disclosure can process more business requests in the same amount of time while ensuring system stability and proactively mitigating the risk of abnormal interface failures without the user's awareness.

[0071] According to embodiments of this disclosure, abnormal interfaces and normal interfaces are determined from multiple service interfaces based on response duration, including:

[0072] Based on the response duration, service interfaces that meet the first predetermined discrimination condition are identified as abnormal interfaces, and service interfaces that do not meet the first predetermined discrimination condition are identified as normal interfaces. The first predetermined discrimination condition includes: under predetermined time conditions, the first response duration of the abnormal interface is greater than a second threshold, and the first response duration is greater than or equal to the second response duration of each normal interface.

[0073] According to embodiments of this disclosure, the predetermined time condition can be a predetermined time period or a predetermined time interval, etc. The predetermined time period can be a continuous and fixed time interval, such as the same time interval for three consecutive days, in which case the predetermined period is 3. The predetermined time period or predetermined time interval can be set based on experience, and will not be elaborated further.

[0074] According to embodiments of this disclosure, under predetermined time conditions, the first response duration of the abnormal interface exceeds a second threshold. Specifically, a time sliding window is used to calculate the response duration of each service interface within a continuous time period to determine whether the second threshold is exceeded, referring to formula (1):

[0075] (Tn-Tavg) / Tavg>Pt Formula (1)

[0076] Where Tn is the response time of any interface in the nth time window; Tavg is the average response time of the interfaces within the n time windows; and Pt is the percentage of response times that are higher than the average.

[0077] Specifically, various parameters can be set based on experience. For example, n is set to 10 by default, each window duration is 1 minute, Pt is set to 300%, and the scheduled time period is 3.

[0078] According to embodiments of this disclosure, a preliminary abnormal interface is determined based on the calculation result of formula (1), and further,

[0079] According to embodiments of this disclosure, under predetermined time conditions, the first response duration is greater than or equal to the second response duration of each normal interface. Specifically, refer to formula (2):

[0080] Tp*w1 > Ti Formula (2)

[0081] Where Tp is the response time of the initial exception interface; w1 is the weight of the initial exception interface response time, which is predefined as 50%; and Ti is the response time of any interface other than the initial exception interface.

[0082] According to an embodiment of this disclosure, based on the calculation result of formula (2), when the response time of the initial abnormal node is greater than the response time of the interface on each of the other nodes, the initial abnormal node is determined to be the final abnormal node.

[0083] According to embodiments of this disclosure, calculating interface response time using a sliding window method allows for continuous data updates, reflecting the latest situation. As time progresses, the window slides forward, incorporating new data and discarding older data, thus enabling timely capture of changes in interface performance. For example, calculating only the average over a fixed time period might miss recent performance fluctuations. A sliding window, however, can react more quickly to emerging issues. By calculating the average across multiple windows, the impact of individual outliers on the overall evaluation can be reduced, making the evaluation results more stable and reliable.

[0084] According to embodiments of this disclosure, abnormal nodes are located more accurately through multi-dimensional judgment conditions, so as to identify the abnormal node that most needs traffic migration from multiple nodes.

[0085] According to an embodiment of this disclosure, the resource consumption data includes at least the amount of resource consumption. The target service node is determined from the second service node based on the first resource consumption data of the first service node and the second resource consumption data of the second service node, including steps 21 to 22.

[0086] Step 21: Calculate the resource consumption of each service node based on the resource consumption data.

[0087] According to the embodiments of this disclosure, the resource consumption data includes indicators such as CPU utilization, memory utilization, and disk I / O utilization. A weight is assigned to each indicator, and the resource consumption of each service node is calculated using an exponential decay method, referring to formula (3):

[0088] L=(Lc*w2 + Lm*w3 + Ld*w4)* (a n ) / 100 formula (3)

[0089] Where Lc, Lm, and Ld represent CPU utilization, memory utilization, and disk I / O utilization, respectively, and w2, w3, and w4 represent the respective weights of the above metrics, with predefined weights of 40%, 40%, and 20%, respectively.

[0090] Step 22: If the average value of the first resource consumption is greater than the first threshold and the first resource consumption is greater than the second resource consumption, then the second service node whose second resource consumption is less than or equal to the first threshold is determined as the target service node from the second service nodes.

[0091] According to an embodiment of this disclosure, within a predetermined time period, the average value of the first resource consumption is greater than a first threshold, referring to formula (4):

[0092] ∑Ln / n > Pl Formula (4)

[0093] Where ∑Ln is the sum of resource consumption of the first service node (the node where the abnormal interface is located) from the first period to the nth period; Pl is the percentage by which the sum of node resource consumption is higher than the average value.

[0094] According to an embodiment of this disclosure, within a predetermined time period, the first resource consumption is greater than the second resource consumption, referring to formula (5):

[0095] Lp*w5 > Li Formula (5)

[0096] Where Lp is the first resource consumption of the first service node corresponding to the abnormal interface, w5 is the weight corresponding to the first resource consumption, which is predefined as 50%, and Li is the second resource consumption of the second service node corresponding to the normal interface.

[0097] According to an embodiment of this disclosure, the allocated traffic to be migrated to each target service node is calculated based on the requested data of the abnormal interface and the target resource consumption data of the target service node, including steps 31 to 32.

[0098] Step 31: Determine the allocation ratio to be migrated to the target service node based on the requested data of the abnormal interface.

[0099] For example, if an abnormal interface is requested 1000 times, it can be determined based on experience to migrate 80%, 50%, or 30% of the requests to other target service nodes.

[0100] Step 32: Calculate the allocated traffic to be migrated to each target service node based on the allocation ratio and the second resource consumption data, specifically including steps 311 to 312.

[0101] In step 311, based on the target resource consumption data, calculate the resource proportion of each target service node among multiple target service nodes, referring to formula (6):

[0102] Resource percentage = Lj / ∑LJ Formula (6)

[0103] Where Lj is the resource consumption of any target service node, and ∑LJ is the sum of the resource consumption of multiple target service nodes.

[0104] In step 312, based on the allocation ratio and resource ratio, determine the allocation ratio of traffic to be migrated to each target service node, referring to formula (7):

[0105] Offset1 =Lj / ∑LJ*w6 Formula (7)

[0106] Where offset1 represents the proportion of allocated traffic to be migrated to each target service node, Lj is the resource consumption of any target service node, ∑LJ is the sum of the resource consumption of multiple target service nodes, and w6 is the allocation proportion.

[0107] According to an embodiment of this disclosure, based on the calculation result of formula (7) and the amount of requested data, the requested data that needs to be migrated from the first service node to the target service node is migrated to the target service node.

[0108] According to embodiments of this disclosure, by notifying the upstream service node, requests sent to the abnormal interface are directly migrated to the target service node based on allocated traffic. This disclosure does not limit the specific method of migrating request volume to the target service node. For example, bytecode enhancement technology can be used to insert code at specific method call points to intercept request packets, allowing the upstream node to transfer traffic originally allocated to the abnormal interface to the target service node's interface based on node IP, allocated traffic, and other information, thereby achieving load balancing across service interfaces.

[0109] According to embodiments of this disclosure, after migrating some or all of the requested data on the first service node to the target service node, the method further includes steps 41 to 43.

[0110] In step 41, monitor the response time of the abnormal interface.

[0111] According to the embodiments of this disclosure, the response time of the abnormal interface is calculated according to formulas (1) and (2) in the above embodiments within each predetermined time period, and the abnormal interface is re-determined according to the first predetermined discrimination condition to determine whether the abnormal interface is still in an abnormal state or has been restored to a normal interface.

[0112] In step 42, if the abnormal interface does not recover to a normal interface, the allocated traffic to be migrated to each target service node is recalculated.

[0113] According to the embodiments of this disclosure, the response time of the target service interface is calculated according to formulas (1) and (2) in the above embodiments, and each target service interface is determined to be in a normal state according to the first predetermined discrimination condition, so as to ensure that the target service node receiving the migration request volume is normal.

[0114] In step 43, if the abnormal interface is restored to a normal interface, some or all of the requested data will be switched back to the first service node, including steps 431 to 432.

[0115] In step 431, some or all of the requested data that has been migrated from the first service node will be switched back to the first service node in batches, and the switchback result will be generated.

[0116] In step 432, based on the back-switch result, it is determined that the abnormal interface maintains the normal interface state.

[0117] Figure 3 schematically illustrates a flowchart of a method for requesting data rollback according to an embodiment of the present disclosure.

[0118] As shown in Figure 3, a predefined time period is defined. If it is determined that the abnormal interface has been restored to a normal interface in several consecutive periods, some or all of the requested data will be switched back to the first service node, referring to formula (8):

[0119] Offset2 =Lj / ∑LJ*w7 Formula (8)

[0120] Here, offset2 represents the total percentage of traffic that will be switched back to the first service node, and w7 represents the percentage of traffic that needs to be switched back each time.

[0121] According to embodiments of this disclosure, the sum of the current cutback percentages should be equal to the allocation percentage, i.e., the total cutback percentage equals the allocation percentage. For example, if the predefined allocation percentage is 50%, the cutback percentage can be determined based on the number of cutbacks, or the number of cutbacks can be determined based on the cutback percentage. For instance, three cutbacks can be set, with each cutback percentage being 30%, 10%, and 10%.

[0122] According to the embodiments of this disclosure, after each back-switch, the response time of the abnormal interface is recalculated according to formulas (1) and (2), and the abnormal interface is re-determined according to the first predetermined discrimination condition to determine whether the abnormal interface is still in an abnormal state or has been restored to a normal interface.

[0123] Figure 4 schematically illustrates a flowchart of a service interface traffic control method according to another embodiment of the present disclosure.

[0124] As shown in Figure 4, the service interface traffic control method specifically includes operations S410 to S430.

[0125] While operating S410, calculate the response time of any service interface;

[0126] In operation S420, if the response time of the service interface is greater than the second threshold, it is determined whether the response time of the abnormal node interface exceeds a certain proportion of the normal node. At the same time, operation S430 is executed to calculate the first resource consumption of the first service node corresponding to the initial abnormal interface.

[0127] In operation S431, if the first resource consumption is greater than the first threshold, operation S432 is executed to check if the first resource consumption exceeds the second resource consumption by a certain percentage. If it does, operation S422 is executed.

[0128] In operation S421, if the response time of the abnormal node interface exceeds a certain proportion of that of the normal node, the preliminary abnormal interface is identified as an abnormal interface.

[0129] In operation S422, the requested data on the abnormal interface is migrated;

[0130] In operation S423, traffic is switched back to the requested data being migrated.

[0131] Based on the above-described service interface traffic control method, this disclosure also provides a service interface traffic control device. The device will be described in detail below with reference to Figure 5.

[0132] Figure 5 schematically illustrates a structural block diagram of a service interface traffic control device according to an embodiment of the present disclosure.

[0133] As shown in Figure 5, the service interface traffic control device 500 of this embodiment includes an acquisition module 510, a first determination module 520, a second determination module 530, a first calculation module 540, and a migration module 550.

[0134] The system comprises the following modules: an acquisition module for acquiring interface information and resource consumption data of multiple service interfaces configured on different service nodes and having the same function, wherein the interface information includes at least the response time and requested data of the service interface; a first determination module for determining abnormal and normal interfaces from the multiple service interfaces based on the response time; a second determination module for determining target service nodes from the second service nodes based on the first resource consumption data of the first service node and the second resource consumption data of the second service node, wherein the first service node corresponds to the abnormal interface and the second service node corresponds to the normal interface; a first calculation module for calculating the allocated traffic to be migrated to each target service node based on the requested data of the abnormal interface and the target resource consumption data of the target service node; and a migration module for migrating some or all of the requested data on the first service node to the target service node based on the allocated traffic.

[0135] According to embodiments of this disclosure, the resource consumption data includes at least the amount of resource consumption, and the second determining module includes: a first calculation submodule and a first determining submodule.

[0136] The first calculation submodule is used to calculate the resource consumption of each service node based on the resource consumption data; the first determination submodule is used to determine the second service node whose second resource consumption is less than or equal to the first threshold as the target service node when the average value of the first resource consumption is greater than the first threshold and the first resource consumption is greater than the second resource consumption.

[0137] According to embodiments of this disclosure, the first calculation module includes: a second determining submodule and a second calculation submodule.

[0138] The second determination submodule is used to determine the allocation ratio to be migrated to the target service node based on the requested data of the abnormal interface; the second calculation submodule is used to calculate the allocated traffic to be migrated to each target service node based on the allocation ratio and the second resource consumption data.

[0139] According to embodiments of this disclosure, the second calculation submodule includes a calculation unit and a determination unit.

[0140] The calculation unit is used to calculate the resource ratio of each target service node among multiple target service nodes based on the target resource consumption data; the determination unit is used to determine the allocated traffic to be migrated to each target service node based on the allocation ratio and resource ratio.

[0141] According to embodiments of this disclosure, the first determining module includes a third determining submodule.

[0142] The third determining submodule is used to determine service interfaces that meet the first predetermined discrimination conditions as abnormal interfaces and service interfaces that do not meet the first predetermined discrimination conditions as normal interfaces based on the response duration. The first predetermined discrimination conditions include: under predetermined time conditions, the first response duration of the abnormal interface is greater than the second threshold, and the first response duration is greater than or equal to the second response duration of each normal interface.

[0143] According to embodiments of this disclosure, after the migration module migrates some or all of the requested data on the first service node to the target service node, the apparatus further includes: a monitoring module, a second calculation module, and a traffic rollback module.

[0144] The monitoring module is used to monitor the response time of abnormal interfaces; the second calculation module is used to recalculate the allocated traffic to be migrated to each target service node if the abnormal interface has not recovered to a normal interface; the traffic rollback module is used to roll back some or all of the requested data to the first service node if the abnormal interface has recovered to a normal interface.

[0145] According to embodiments of this disclosure, the traffic back-cutting module includes a back-cutting submodule and a fourth determination submodule.

[0146] The rollback submodule is used to roll back some or all of the requested data that has been migrated from the first service node to the first service node in batches and generate rollback results; the fourth determination submodule is used to determine whether the abnormal interface should maintain the normal interface state based on the rollback results.

[0147] According to embodiments of this disclosure, any plurality of modules among the acquisition module 510, the first determination module 520, the second determination module 530, the first calculation module 540, and the migration module 550 may be combined into one module, or any one of these modules may be split into multiple modules. Alternatively, at least part of the functionality of one or more of these modules may be combined with at least part of the functionality of other modules and implemented in one module. According to embodiments of this disclosure, at least one of the acquisition module 510, the first determination module 520, the second determination module 530, the first calculation module 540, and the migration module 550 may be at least partially implemented as hardware circuitry, such as a field-programmable gate array (FPGA), a programmable logic array (PLA), a system-on-a-chip, a system-on-a-substrate, a system-on-package, an application-specific integrated circuit (ASIC), or any other reasonable means of integrating or packaging circuitry, or implemented in any one of software, hardware, and firmware methods, or in a suitable combination of any of these methods. Alternatively, at least one of the acquisition module 510, the first determination module 520, the second determination module 530, the first calculation module 540, and the migration module 550 may be implemented at least partially as a computer program module, which can perform corresponding functions when the computer program module is run.

[0148] Figure 6 schematically illustrates a block diagram of an electronic device suitable for implementing a service interface flow control method according to an embodiment of the present disclosure.

[0149] As shown in FIG6, an electronic device 600 according to an embodiment of the present disclosure includes a processor 601, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 602 or a program loaded from a storage portion 608 into a random access memory (RAM) 603. The processor 601 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or an associated chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 601 may also include onboard memory for caching purposes. The processor 601 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0150] RAM 603 stores various programs and data required for the operation of electronic device 600. Processor 601, ROM 602, and RAM 603 are interconnected via bus 604. Processor 601 performs various operations of the method flow according to embodiments of the present disclosure by executing programs in ROM 602 and / or RAM 603. It should be noted that the programs may also be stored in one or more memories other than ROM 602 and RAM 603. Processor 601 may also perform various operations of the method flow according to embodiments of the present disclosure by executing programs stored in said one or more memories.

[0151] According to embodiments of this disclosure, the electronic device 600 may further include an input / output (I / O) interface 605, which is also connected to a bus 604. The electronic device 600 may also include one or more of the following components connected to the input / output (I / O) interface 605: an input section 606 including a keyboard, mouse, etc.; an output section 607 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 608 including a hard disk, etc.; and a communication section 609 including a network interface card such as a LAN card, modem, etc. The communication section 609 performs communication processing via a network such as the Internet. A drive 610 is also connected to the input / output (I / O) interface 605 as needed. A removable medium 611, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 610 as needed so that computer programs read from it can be installed into the storage section 608 as needed.

[0152] This disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or it may exist independently and not assembled into the device / apparatus / system. The computer-readable storage medium carries one or more programs that, when executed, implement the method according to the embodiments of this disclosure.

[0153] According to embodiments of this disclosure, the computer-readable storage medium can be a non-volatile computer-readable storage medium, such as including, but not limited to: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this disclosure, the computer-readable storage medium can be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. For example, according to embodiments of this disclosure, the computer-readable storage medium may include ROM 602 and / or RAM 603 and / or one or more memories other than ROM 602 and RAM 603 described above.

[0154] Embodiments of this disclosure also include a computer program product comprising a computer program containing program code for performing the methods shown in the flowchart. When the computer program product is run on a computer system, the program code enables the computer system to implement the service interface flow control method provided in the embodiments of this disclosure.

[0155] When the computer program is executed by the processor 601, it performs the functions defined in the system / apparatus of this disclosure embodiments. According to embodiments of this disclosure, the systems, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0156] In one embodiment, the computer program may rely on a tangible storage medium such as an optical storage device or a magnetic storage device. In another embodiment, the computer program may also be transmitted and distributed in the form of signals over a network medium, and downloaded and installed via the communication section 609, and / or installed from the removable medium 611. The program code contained in the computer program can be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination thereof.

[0157] In such an embodiment, the computer program can be downloaded and installed from a network via the communication section 609, and / or installed from the removable medium 611. When the computer program is executed by the processor 601, it performs the functions defined in the system of this disclosure embodiment. According to embodiments of this disclosure, the systems, devices, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0158] According to embodiments of this disclosure, program code for executing the computer programs provided in embodiments of this disclosure can be written in any combination of one or more programming languages. Specifically, these computational programs can be implemented using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, languages ​​such as Java, C++, Python, "C", or similar programming languages. The program code can execute entirely on a user's computing device, partially on a user's device, partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0159] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0160] Those skilled in the art will understand that the features described in the various embodiments of this disclosure can be combined and / or combined in various ways, even if such combinations or combinations are not explicitly described in this disclosure. In particular, the features described in the various embodiments of this disclosure can be combined and / or combined in various ways without departing from the spirit and teachings of this disclosure. All such combinations and / or combinations fall within the scope of this disclosure.

[0161] The embodiments of this disclosure have been described above. However, these embodiments are for illustrative purposes only and are not intended to limit the scope of this disclosure. Although various embodiments have been described above, this does not mean that the measures in the various embodiments cannot be used advantageously in combination. Various substitutions and modifications can be made by those skilled in the art without departing from the scope of this disclosure, and all such substitutions and modifications should fall within the scope of this disclosure.

Claims

1. A service interface traffic control method, characterized in that, The method includes: acquiring interface information of multiple service interfaces configured on different service nodes and having the same function, as well as resource consumption data of each service node, wherein the interface information includes at least the response time and requested data of the service interface; determining abnormal interfaces and normal interfaces from the multiple service interfaces based on the response time; determining target service nodes from the second service nodes based on the first resource consumption data of the first service node and the second resource consumption data of the second service node, wherein the first service node corresponds to the abnormal interface and the second service node corresponds to the normal interface; calculating the allocated traffic to be migrated to each of the target service nodes based on the requested data of the abnormal interface and the target resource consumption data of the target service node; and migrating part or all of the requested data on the abnormal interface to the target service node based on the allocated traffic, wherein the target service node is used to characterize an interface in the second service node that can share part or all of the request volume on the abnormal interface, and the target service node has the same function as the abnormal interface.

2. The method according to claim 1, characterized in that, The resource consumption data includes at least the resource consumption amount. Determining the target service node from the second service nodes based on the first resource consumption data of the first service node and the second resource consumption data of the second service node includes: calculating the resource consumption amount corresponding to each service node based on the resource consumption data; and determining the second service node whose second resource consumption amount is less than or equal to the first threshold as the target service node when the average value of the first resource consumption amount is greater than a first threshold and the first resource consumption amount is greater than the second resource consumption amount.

3. The method according to claim 1, characterized in that, Based on the requested data of the abnormal interface and the target resource consumption data of the target service node, calculate the allocated traffic to be migrated to each of the target service nodes, including: determining the allocation ratio to be migrated to the target service node based on the requested data of the abnormal interface; and calculating the allocated traffic to be migrated to each of the target service nodes based on the allocation ratio and the second resource consumption data.

4. The method according to claim 3, characterized in that, Based on the allocation ratio and the second resource consumption data, the allocated traffic to be migrated to each of the target service nodes is calculated, including: based on the target resource consumption data, calculating the resource ratio of each of the target service nodes among the multiple target service nodes; and based on the allocation ratio and the resource ratio, determining the allocated traffic to be migrated to each of the target service nodes.

5. The method according to claim 1, characterized in that, Determining abnormal and normal interfaces from multiple service interfaces based on the response duration includes: determining service interfaces that meet a first predetermined discrimination condition as abnormal interfaces and service interfaces that do not meet the first predetermined discrimination condition as normal interfaces, wherein the first predetermined discrimination condition includes: under predetermined time conditions, the first response duration of the abnormal interface is greater than a second threshold, and the first response duration is greater than or equal to the second response duration of each of the normal interfaces.

6. The method according to any one of claims 1 to 5, wherein after migrating part or all of the requested data on the first service node to the target service node, the method further comprises: Monitor the response duration of the abnormal interface; If the abnormal interface fails to recover to the normal interface, the allocated traffic to be migrated to each of the target service nodes will be recalculated. If the abnormal interface is restored to the normal interface, some or all of the requested data will be switched back to the first service node.

7. The method according to claim 6, characterized in that, When the abnormal interface is restored to the normal interface, the partial or all of the requested data is switched back to the first service node, including: switching back the partial or all of the requested data that has been migrated from the first service node to the first service node in batches, and generating a switchback result; and determining that the abnormal interface maintains the normal interface state based on the switchback result.

8. A service interface flow control device, characterized in that, The apparatus includes: an acquisition module, configured to acquire interface information of multiple service interfaces configured on different service nodes and having the same function, and resource consumption data of each service node, wherein the interface information includes at least the response time and requested data of the service interface; a first determination module, configured to determine abnormal interfaces and normal interfaces from the multiple service interfaces based on the response time; a second determination module, configured to determine target service nodes from the second service nodes based on the first resource consumption data of the first service node and the second resource consumption data of the second service node, wherein the first service node corresponds to the abnormal interface and the second service node corresponds to the normal interface; a first calculation module, configured to calculate the allocated traffic to be migrated to each of the target service nodes based on the requested data of the abnormal interface and the target resource consumption data of the target service node; and a migration module, configured to migrate part or all of the requested data on the abnormal interface to the target service node based on the allocated traffic, wherein the target service node is used to characterize an interface in the second service node that can share part or all of the request volume on the abnormal interface, and the target service node has the same function as the abnormal interface.

9. An electronic device, comprising: One or more processors; A memory for storing one or more computer programs, characterized in that the one or more processors execute the one or more computer programs to implement the steps of the method according to any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program or instructions stored thereon, characterized in that, When the computer program or instructions are executed by a processor, they implement the steps of the method according to any one of claims 1 to 7.

11. A computer program product, comprising a computer program or instructions, characterized in that, When the computer program or instructions are executed by a processor, they implement the steps of the method according to any one of claims 1 to 7.

Images