CN116489103A - Service flow limiting method, device and service processing system - Google Patents

Service flow limiting method, device and service processing system Download PDF

Info

Publication number
CN116489103A
CN116489103A CN202310457952.5A CN202310457952A CN116489103A CN 116489103 A CN116489103 A CN 116489103A CN 202310457952 A CN202310457952 A CN 202310457952A CN 116489103 A CN116489103 A CN 116489103A
Authority
CN
China
Prior art keywords
target
state
service
rule
server
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202310457952.5A
Other languages
Chinese (zh)
Inventor
管怡成
李模楷
王佳捷
陈冠颖
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Industrial and Commercial Bank of China Ltd ICBC
Original Assignee
Industrial and Commercial Bank of China Ltd ICBC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Industrial and Commercial Bank of China Ltd ICBC filed Critical Industrial and Commercial Bank of China Ltd ICBC
Priority to CN202310457952.5A priority Critical patent/CN116489103A/en
Publication of CN116489103A publication Critical patent/CN116489103A/en
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/215—Flow control; Congestion control using token-bucket
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2425—Traffic characterised by specific attributes, e.g. priority or QoS for supporting services specification, e.g. SLA
    • H04L47/2433—Allocation of priorities to traffic types
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/29—Flow control; Congestion control using a combination of thresholds
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/50—Queue scheduling
    • H04L47/62—Queue scheduling characterised by scheduling criteria
    • H04L47/625—Queue scheduling characterised by scheduling criteria for service slots or service orders
    • H04L47/6275—Queue scheduling characterised by scheduling criteria for service slots or service orders based on priority
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer And Data Communications (AREA)

Abstract

The application discloses a business flow limiting method, a business flow limiting device and a business processing system, and relates to the field of financial science and technology. The method comprises the following steps: intercepting a target service request aiming at a target service, which is sent to a server by a client; acquiring target state information and determining a matching state of the target state information and a target current limiting rule, wherein the target state information at least comprises: the method comprises the steps of accessing a flow state, a service priority of a target service, a resource use state of a server side and a service connection state with the server side at present; and under the condition that the target state information is matched with the target flow limiting rule, performing flow limiting processing on the target service request, wherein the flow limiting processing comprises one of the following steps: queuing and refusing; and under the condition that the target state information is not matched with the target current limiting rule, a token is issued to the client, wherein the token is the basis for processing the target service request by the server. By the method and the device, the technical problems of single service current limiting mode and poor effect in the related technology are solved.

Description

Service flow limiting method, device and service processing system
Technical Field
The present application relates to the field of financial science and technology, and in particular, to a service flow limiting method, device and service processing system.
Background
With the continuous upgrade of application systems and network architecture, the access service volume and external traffic of the application system are continuously and rapidly increased, and because the whole service resources of the application system are limited, when the external traffic is suddenly increased or the internal of the application system has defects, one or more service functions are easily abnormal, and the conditions of logic interaction, resource exhaustion and the like can further cause that other service functions of the application system cannot be normally used, and even cause global faults of the whole application system.
In order to avoid the above situation, a certain current limiting treatment needs to be performed on the service accessed to the application system, and the service current limiting treatment mode in the related technology often has the characteristics of single mode, poor application applicability, low service differentiation degree and the like, so that the practical application requirement cannot be met.
Aiming at the technical problems of single service current limiting mode and poor effect in the related technology, no effective solution is proposed at present.
Disclosure of Invention
The main purpose of the present application is to provide a service flow limiting method, device and service processing system, so as to solve the technical problems of single service flow limiting mode and poor effect in the related art.
According to one aspect of the present application, there is provided a traffic throttling method, the method including: intercepting a target service request aiming at a target service, which is sent to a server by a client; acquiring target state information and determining a matching state of the target state information and a target current limiting rule, wherein the target state information at least comprises: the method comprises the steps of accessing a flow state, a service priority of a target service, a resource use state of a server side and a service connection state with the server side at present; and under the condition that the target state information is matched with the target flow limiting rule, performing flow limiting processing on the target service request, wherein the flow limiting processing comprises one of the following steps: queuing and refusing; and under the condition that the target state information is not matched with the target current limiting rule, a token is issued to the client, wherein the token is the basis for processing the target service request by the server.
Optionally, the access traffic state includes one of: accessing a data flow value and a concurrent thread quantity value; the resource usage state of the server includes one of the following: the current processing service quantity, CPU utilization rate and IO utilization rate; the service connection state includes one of: the system comprises a fusing state, a semi-fusing state and a normal state, wherein in the fusing state, all access requests to the server are refused, in the semi-fusing state, part of access requests to the server are allowed, and in the normal state, all access requests to the server are allowed.
Optionally, the target current limit rule includes a first current limit rule and a second current limit rule, and determining a matching state of the target state information and the target current limit rule includes: under the condition that the access flow state is not smaller than a first preset threshold value, determining that the target state information is matched with a first current limiting rule; and under the condition that the access flow state is smaller than a first preset threshold value, determining that the target state information is not matched with the first current limiting rule, and determining the matching state of the target state information and the second current limiting rule according to the service priority, the resource using state and the service connection state.
Optionally, determining the matching state of the target state information and the second current limiting rule according to the service priority, the resource usage state and the service connection state includes: under the condition that the service connection state is a fusing state, determining that the target state information is matched with a second current limiting rule; determining a second preset threshold corresponding to the service priority of the target service under the condition that the service connection state is a semi-fusing state, wherein the second preset threshold corresponding to the high-priority service is larger than the second preset threshold corresponding to the low-priority service; under the condition that the resource use state is not smaller than a second preset threshold value, determining that the target state information is matched with a second current limiting rule; under the condition that the resource use state is smaller than a second preset threshold value, determining that the target state information is not matched with a second current limiting rule; and under the condition that the service connection state is a normal state, determining that the target state information is not matched with the second current limiting rule.
Optionally, in the case that the target state information matches the target current limiting rule, performing current limiting processing on the target service request includes: queuing the target service request under the condition that the access flow state is not smaller than a first preset threshold value and smaller than a third preset threshold value, wherein the service in the queue is processed according to the service priority from high to low; and under the condition that the access flow state is not smaller than a third preset threshold value, rejecting the target service request.
Optionally, in the case that the target state information matches the target current limiting rule, performing current limiting processing on the target service request includes: under the condition that the service connection state is a fusing state, rejecting the target service request; and queuing the target service request under the condition that the service connection state is a semi-fusing state and the resource use state is not less than a second preset threshold, wherein the service in the queue is processed according to the service priority from high to low.
Optionally, if the service connection state is the normal state, if the resource usage state is detected to be not less than the fourth preset threshold, switching the service connection state to the fusing state; under the condition that the service connection state is a fusing state, switching the service connection state into a semi-fusing state after a first preset time period; if the service connection state is the semi-fusing state, if the resource use state is detected to be not smaller than a fourth preset threshold value, switching the service connection state to the fusing state; and if the resource use state is continuously smaller than the fourth preset threshold value within the second preset time period, switching the service connection state into a normal state.
Optionally, before intercepting a target service request for a target service sent by a client to a server, determining a target current limiting rule from a preset current limiting rule template in response to a rule selection operation of a target object; or, configuring the target current limit rule in response to a rule configuration operation of the target object.
Optionally, issuing the token to the client comprises: determining a token corresponding to the target service from a preset token bucket; and issuing the token to the client, wherein the client is used for resending the target service request carrying the token to the server, and the server only processes the service request carrying the token.
Optionally, in response to a status query operation of the target object, status information corresponding to the status query operation is presented, wherein the status information includes at least one of: the method comprises the steps of accessing a flow state, a resource using state of a server side and a service connection state with the server side at present; responding to the log query operation of the target object, and displaying log information corresponding to the log query operation, wherein the log information comprises: processing log information of all the intercepted businesses in a preset time period.
According to another aspect of the present application, there is also provided a service flow limiting device, including: the interception module is used for intercepting a target service request aiming at a target service, which is sent to the server by the client; the matching module is used for acquiring the target state information and determining the matching state of the target state information and the target current limiting rule, wherein the target state information at least comprises: the method comprises the steps of accessing a flow state, a service priority of a target service, a resource use state of a server side and a service connection state with the server side at present; the flow limiting module is used for carrying out flow limiting processing on the target service request under the condition that the target state information is matched with the target flow limiting rule, wherein the flow limiting processing comprises one of the following steps: queuing and refusing; and the issuing module is used for issuing a token to the client under the condition that the target state information is not matched with the target current limiting rule, wherein the token is the basis for processing the target service request by the server.
According to another aspect of the present application, there is also provided a service processing system, including: the system comprises a client, a server and a stable access platform, wherein the stable access platform is used for executing the service flow limiting method.
According to another aspect of the present application, there is further provided a processor, where the processor is configured to execute a program, and when the program is executed, the service flow limiting method described above is executed.
According to another aspect of the present application, there is also provided an electronic device including one or more processors and a memory for storing one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the traffic throttling method described above.
In the application, a target service request aiming at a target service, which is sent to a server by a client, is intercepted first; then, target state information is acquired, wherein the target state information at least comprises: determining whether the target state information is matched with a target current limiting rule or not according to the current access flow state, the service priority of the target service, the resource use state of the server and the service connection state of the server; if the target state information is matched with the target flow limiting rule, performing flow limiting processing on the target service request, including queuing processing or refusing processing; if the target state information is not matched with the target flow limiting rule, a token is issued to the client, and the token is the basis for processing the target service request by the server. The method and the system for limiting the flow of the service can effectively solve the technical problems of single service flow limiting mode and poor effect in the related technology by comprehensively considering information such as access flow, service priority, server side state and the like and utilizing comprehensive and reliable flow limiting rules obtained by combining various flow limiting strategies to limit the flow of the service, thereby improving the stability of system service in a multi-service concurrency scene.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application, illustrate and explain the application and are not to be construed as limiting the application. In the drawings:
FIG. 1 is a schematic diagram of an architecture for providing an alternative business processing system according to an embodiment of the present application;
FIG. 2 is a schematic diagram of an architecture providing an alternative stable access platform according to an embodiment of the present application;
fig. 3 is a flow chart of an alternative service flow limiting method according to an embodiment of the present application;
FIG. 4 is a schematic diagram providing an alternative automatic switching of service connection states according to an embodiment of the present application;
FIG. 5 is a schematic diagram providing an alternative thresholding approach in accordance with an embodiment of the present application;
FIG. 6 is an interactive schematic diagram providing an alternative business processing system according to an embodiment of the present application;
fig. 7 is a schematic structural diagram of an alternative service current limiting device according to an embodiment of the present application;
fig. 8 is a schematic structural diagram of an alternative electronic device according to an embodiment of the present application.
Detailed Description
In order to make the present application solution better understood by those skilled in the art, the following description will be made in detail and with reference to the accompanying drawings in the embodiments of the present application, it is apparent that the described embodiments are only some embodiments of the present application, not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, shall fall within the scope of the present application.
It should be noted that the terms "first," "second," and the like in the description and claims of the present application and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate in order to describe the embodiments of the present application described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
It should be noted that, related information (including, but not limited to, user equipment information, user personal information, etc.) and data (including, but not limited to, data for presentation, analyzed data, etc.) related to the present application are information and data authorized by the user or sufficiently authorized by each party. For example, an interface is provided between the system and the relevant user or institution, before acquiring the relevant information, the system needs to send an acquisition request to the user or institution through the interface, and acquire the relevant information after receiving the consent information fed back by the user or institution.
Fig. 1 is a schematic structural diagram of an alternative service processing system according to an embodiment of the present application, as shown in fig. 1, where the system includes: the system comprises a client 11, a server 12 and a stable access platform 13, wherein the stable access platform 13 is used for intercepting a target service request aiming at a target service, which is sent by the client 11 to the server 12; acquiring target state information and determining a matching state of the target state information and a target current limiting rule, wherein the target state information at least comprises: the current access flow state, the service priority of the target service, the resource use state of the server 12 and the service connection state with the server 12; and in the case that the target state information is matched with the target flow limiting rule, performing flow limiting processing on the target service request, wherein the flow limiting processing comprises one of the following steps: queuing and refusing; and in the case that the target state information is not matched with the target throttling rule, a token is issued to the client 11, wherein the token is the basis for the server 12 to process the target service request.
The client 11 may be a single client or a client cluster formed by a plurality of clients; the server 12 may be a single server or a server cluster formed by a plurality of servers.
Compared with the application system in the related art, the service processing system in the embodiment of the application strips the current limiting function originally located at the server side, and the stable access platform is independently deployed in a cluster mode, and the platform performs current limiting processing on the accessed service request by combining multiple current limiting strategies so as to improve the stability of system service under a multi-service concurrency scene.
As an alternative implementation, the current limiting policy adopted in the embodiments of the present application includes at least the following:
delay processing policy based on thread pool: the strategy aims to delay or discard the service under the condition of flow surge so as to realize the flow stability of the server.
Service degradation policy with traffic level priority: the strategy sets a stepped rule threshold for each level of service according to the priority level of the service, when part of the low-priority service exceeds the threshold, the service degradation strategy is triggered, and queuing or rejecting operation is carried out on the low-priority service, so that the purpose of service hierarchical control is achieved, and the normal operation of the core service is guaranteed to the greatest extent.
A variety of fusing strategies: fusing the business category of the system resource breakthrough rule index threshold value, rejecting the flow access, and avoiding overload of the server; meanwhile, in order to avoid the conditions that the system index fluctuates greatly and the fusing/normal state is frequently switched, a semi-fusing state is set, and long-term stability of the resource index of the server under the high concurrency condition is ensured. In the semi-fusing state, the service request is delayed or refused according to the rule, and when the system index is kept below the threshold value for a certain period of time, the system index is switched to the normal state, and otherwise, the system index is switched to the fusing state.
Token bucket policy: the token mechanism is added, and the service end only processes the service with the token information, namely, the service can be processed if and only if the client end sends a service request carrying the token information to the service end. The token is used as a unique credential for judging whether the service request is legal or not, the client sends the request to the stable access platform to obtain the token, and a token bucket module in the platform performs real-time, time delay or refusal of issuing the token on the accessed service request according to a plurality of real-time system resources of the server so as to achieve the purpose of limiting the flow.
It should be noted that, the above current limiting policy is only to illustrate the principle, and in practical application, various current limiting policies are used in combination, and specific current limiting rules can be configured by a user according to scenes and requirements, so as to ensure applicability of various service scenes to the greatest extent; optionally, the platform may also provide a plurality of preset current limit rule templates for selection by the user.
Fig. 2 is a schematic architecture diagram of an alternative stable access platform according to an embodiment of the present application, and as shown in fig. 2, the platform mainly includes an application scenario layer 21, a service processing layer 22, and a data storage layer 23. Wherein, the application scene layer 21 includes: the rule configuration module 211 is responsible for providing the configuration of the current limiting rule to the outside, the request simulation module 212 is responsible for the client to request the simulation of the current limiting operation in batches, and the state query module 213 is provided for checking the running state of the platform; the service processing layer 22 includes: the configuration center 221 responds to the rule configuration operation to perform the flow limiting rule configuration, the flow limiting module 222 performs corresponding flow limiting operation on the requested service according to the rule defined by the configuration center 221, the token bucket module 223 issues tokens for the service which is not subjected to flow limiting, and the monitoring center 224 monitors the platform running state and the server side state; the data storage layer 23 stores data required for the operation of each module of the application scene layer 21 and the service processing layer 22, and includes: platform running state information, server state information, pre-configured current limiting rule templates and the like.
The flow performed by the stabilized access platform is described in detail below in connection with preferred implementation steps.
Fig. 3 is a flow chart of an alternative service flow limiting method according to an embodiment of the present application, as shown in fig. 3, the method includes the following steps:
step S301, intercepting a target service request aiming at a target service, which is sent to a server by a client;
step S302, obtaining target state information and determining a matching state of the target state information and a target current limiting rule, wherein the target state information at least comprises: the method comprises the steps of accessing a flow state, a service priority of a target service, a resource use state of a server side and a service connection state with the server side at present;
step S303, in the case that the target state information is matched with the target current limiting rule, performing current limiting processing on the target service request, wherein the current limiting processing comprises one of the following steps: queuing and refusing;
step S304, a token is issued to the client under the condition that the target state information is not matched with the target current limit rule, wherein the token is the basis for the server to process the target service request.
The method and the system for limiting the flow of the service can effectively solve the technical problems of single service flow limiting mode and poor effect in the related technology by comprehensively considering information such as access flow, service priority, server side state and the like and utilizing comprehensive and reliable flow limiting rules obtained by combining various flow limiting strategies to limit the flow of the service, thereby improving the stability of system service under the multi-service concurrency scene.
As an optional implementation manner, before intercepting a target service request for a target service sent by a client to a server, the stable access platform may determine a target current limit rule from a preset current limit rule template in response to a rule selection operation of a target object; or, configuring the target current limit rule in response to a rule configuration operation of the target object.
It can be appreciated that, to improve the applicability and flexibility of the target current limit rule, the user can configure the target current limit rule according to the application scenario and the requirement; in order to improve the convenience of use, the stable access platform also provides a plurality of preset current limiting rule templates, and a user can select the most suitable target current limiting rule according to the requirement.
As an alternative embodiment, the target current limit rule may be generally divided into the following two parts:
the first part is a first flow limiting rule configured by considering the current access flow state of the platform, and is responsible for carrying out primary screening on the accessed service. The access traffic state may select the following index as a reference basis: access data flow value, concurrent thread number value.
And the second part is a second flow limiting rule configured by comprehensively considering the service connection state with the server, the resource use state of the server and the service priority of the target service, and more carefully performing operations such as degradation on the accessed service. Wherein, the service connection state with the server side comprises one of the following: a fusing state, a semi-fusing state and a normal state, wherein in the fusing state, all access requests to the server are refused, in the semi-fusing state, part of access requests to the server are allowed, and in the normal state, all access requests to the server are allowed; the resource usage state of the server may select the following indexes as reference basis: the current processing service quantity, CPU utilization rate and IO utilization rate; the service priority of the target service is divided in advance according to the importance degree of the service, for example, different services can be divided into a core service or a common service according to the importance degree.
Optionally, in the embodiment of the present application, the service connection state between the stable access platform and the server may be set manually by a user, or may be switched automatically, and fig. 4 shows a schematic diagram of automatic switching of an optional service connection state, where a specific switching rule is as follows:
if the service connection state is detected to be not less than a fourth preset threshold value, the service connection state is switched to a fusing state, and in general, the fourth preset threshold value can be set to be the same as a second preset threshold value corresponding to the core service;
under the condition that the service connection state is a fusing state, switching the service connection state into a semi-fusing state after a first preset time period;
if the service connection state is the semi-fusing state, if the resource use state is detected to be not smaller than a fourth preset threshold value, switching the service connection state to the fusing state; and if the resource use state is continuously smaller than the fourth preset threshold value within the second preset time period, switching the service connection state into a normal state.
As an alternative embodiment, after the target state information is acquired, the matching state of the target state information and the target current limiting rule may be determined as follows:
Under the condition that the access flow state is not smaller than a first preset threshold value, determining that the target state information is matched with a first current limiting rule;
under the condition that the access flow state is smaller than a first preset threshold value, determining that the target state information is not matched with the first current limiting rule, and determining the matching state of the target state information and the second current limiting rule according to the service priority, the resource use state and the service connection state at the moment, specifically:
under the condition that the service connection state is a fusing state, determining that the target state information is matched with a second current limiting rule;
under the condition that the service connection state is a semi-fusing state, determining a second preset threshold corresponding to the service priority of the target service; under the condition that the resource use state is not smaller than a second preset threshold value, determining that the target state information is matched with a second current limiting rule; under the condition that the resource use state is smaller than a second preset threshold value, determining that the target state information is not matched with a second current limiting rule;
and under the condition that the service connection state is a normal state, determining that the target state information is not matched with the second current limiting rule.
As an alternative implementation manner, in the case that the target state information matches the first current limiting rule, the current limiting processing may be performed on the target service request in the following manner: queuing the target service request under the condition that the access flow state is not smaller than a first preset threshold value and smaller than a third preset threshold value, wherein the service in the queue is processed according to the service priority from high to low; and under the condition that the access flow state is not smaller than a third preset threshold value, rejecting the target service request.
Taking the concurrent thread number value selected by the access flow state as an example, assuming that the first preset threshold value is 5, and the third preset threshold value is 10, if the current concurrent thread number is 3, the current access flow is less, and no current limitation is needed; if the current concurrent thread number is 7, the current access flow is more, and the current access flow needs to be processed according to the service priority queuing; if the current concurrent thread number is 12, the current access flow is beyond the loadable range, and the processing is directly refused for the newly accessed service request.
As an alternative implementation manner, in the case that the target state information matches the second current limiting rule, the current limiting processing may be performed on the target service request in the following manner: under the condition that the service connection state is a fusing state, rejecting the target service request; and queuing the target service request under the condition that the service connection state is a semi-fusing state and the resource use state is not less than a second preset threshold, wherein the service in the queue is processed according to the service priority from high to low.
It will be appreciated that, in order to ensure that more important services are prioritized, the above second preset threshold is typically set stepwise, where the second preset threshold corresponding to a high priority service is greater than the second preset threshold corresponding to a low priority service. Taking the example that the CPU utilization rate and the service priority are selected as the core service and the common service in the resource utilization state, fig. 5 shows an alternative threshold dividing mode, wherein the second preset threshold corresponding to the core service is the same as the fourth preset threshold, and is 85%, the second preset threshold corresponding to the common service is 70%, and the current CPU utilization rate is assumed to be 90%, and the service connection state is the fusing state, so that the processing is refused no matter whether the target service is the core service or the common service; assuming that the current CPU utilization rate is 60%, the service connection state is a normal state, and the target service is a core service or a common service and is processed normally; assuming that the current CPU utilization rate is 80%, if the target service is a core service, normal processing is performed, and if the target service is a common service, current limiting processing is performed. By the method, the priority of processing the core service can be effectively ensured.
It should be noted that, the first preset threshold, the second preset threshold, the third preset threshold, the fourth preset threshold, the first preset duration and the second preset duration are all set by the user according to the requirement when configuring the target current limiting rule, and the values are only used as an illustration and do not constitute an actual limitation.
As an alternative implementation manner, when the target service does not meet the target current limiting rule, that is, does not need to perform the current limiting operation, the stable access platform may issue a token to the client in the following manner: determining a token corresponding to the target service from a preset token bucket; and issuing the token to the client, wherein the client is used for resending the target service request carrying the token to the server, and the server only processes the service request carrying the token.
Optionally, the stable access platform may further respond to a state query operation of the target object, and display state information corresponding to the state query operation, where the state information includes at least one of the following: the method comprises the steps of accessing a flow state, a resource using state of a server side and a service connection state with the server side at present; the log information corresponding to the log query operation can be displayed in response to the log query operation of the target object, wherein the log information comprises: processing log information of all the intercepted businesses in a preset time period.
FIG. 6 is a schematic diagram showing interaction of modules in an alternative service processing system, specifically including the following steps:
s1, a user configures a current limiting rule through a configuration center;
s2, the flow limiting module intercepts a service request sent by a client to a server;
s3, the current limiting module acquires relevant state information and determines whether the relevant state information is matched with a current limiting rule;
s4, if the service request is matched, carrying out delay or refusal operation on the service request;
s5, if the tokens are not matched, obtaining the tokens from a token bucket;
s6, the flow limiting module issues a token to the client;
s7, the client side sends the service request carrying the token to the server side again;
s8, the service end processes the service request carrying the token.
In the embodiment of the application, a target service request aiming at a target service, which is sent to a server by a client, is intercepted first; then, target state information is acquired, wherein the target state information at least comprises: determining whether the target state information is matched with a target current limiting rule or not according to the current access flow state, the service priority of the target service, the resource use state of the server and the service connection state of the server; if the target state information is matched with the target flow limiting rule, performing flow limiting processing on the target service request, including queuing processing or refusing processing; if the target state information is not matched with the target flow limiting rule, a token is issued to the client, and the token is the basis for processing the target service request by the server. The method and the system for limiting the flow of the service can effectively solve the technical problems of single service flow limiting mode and poor effect in the related technology by comprehensively considering information such as access flow, service priority, server side state and the like and utilizing comprehensive and reliable flow limiting rules obtained by combining various flow limiting strategies to limit the flow of the service, thereby improving the stability of system service in a multi-service concurrency scene.
It should be noted that the steps illustrated in the flowcharts of the figures may be performed in a computer system such as a set of computer executable instructions, and that although a logical order is illustrated in the flowcharts, in some cases the steps illustrated or described may be performed in an order other than that illustrated herein.
The embodiment of the application also provides a service current limiting device, and the service current limiting device of the embodiment of the application can be used for executing the service current limiting method provided by the embodiment of the application. The following describes a service current limiting device provided in an embodiment of the present application.
Fig. 7 is a schematic diagram of a traffic flow limiting device according to an embodiment of the present application. As shown in fig. 7, the apparatus includes: an interception module 71, a matching module 72, a restriction module 73 and a dispensing module 74.
An interception module 71, configured to intercept a target service request for a target service sent by a client to a server;
the matching module 72 is configured to obtain target state information, and determine a matching state of the target state information and the target current limit rule, where the target state information at least includes: the method comprises the steps of accessing a flow state, a service priority of a target service, a resource use state of a server side and a service connection state with the server side at present;
A current limiting module 73, configured to perform a current limiting process on the target service request if the target state information matches the target current limiting rule, where the current limiting process includes one of the following: queuing and refusing;
and the issuing module 74 is configured to issue a token to the client if the target state information does not match the target current limit rule, where the token is a basis for the server to process the target service request.
Optionally, in the service flow limiting device provided in the embodiment of the present application, the service flow limiting device further includes a rule configuration module, configured to determine, before intercepting a target service request for a target service sent by a client to a server, a target flow limiting rule from a preset flow limiting rule template in response to a rule selection operation of a target object; or, configuring the target current limit rule in response to a rule configuration operation of the target object.
It can be appreciated that, to improve the applicability and flexibility of the target current limit rule, the user can configure the target current limit rule according to the application scenario and the requirement; in order to improve the convenience of use, the service current limiting device also provides a plurality of preset current limiting rule templates, and a user can select the most suitable target current limiting rule according to the requirement.
As an alternative embodiment, the target current limit rule may be generally divided into the following two parts:
the first part is a first flow limiting rule configured in consideration of the current access flow state and is responsible for carrying out primary screening on the accessed service. The access traffic state may select the following index as a reference basis: access data flow value, concurrent thread number value.
And the second part is a second flow limiting rule configured by comprehensively considering the service connection state with the server, the resource use state of the server and the service priority of the target service, and more carefully performing operations such as degradation on the accessed service. Wherein, the service connection state with the server side comprises one of the following: a fusing state, a semi-fusing state and a normal state, wherein in the fusing state, all access requests to the server are refused, in the semi-fusing state, part of access requests to the server are allowed, and in the normal state, all access requests to the server are allowed; the resource usage state of the server may select the following indexes as reference basis: the current processing service quantity, CPU utilization rate and IO utilization rate; the service priority of the target service is divided in advance according to the importance degree of the service, for example, different services can be divided into a core service or a common service according to the importance degree.
Optionally, in the embodiment of the present application, the service connection state with the server may be set manually by the user, or may be switched automatically, where a specific switching rule is as follows:
if the service connection state is detected to be not less than a fourth preset threshold value, the service connection state is switched to a fusing state, and in general, the fourth preset threshold value can be set to be the same as a second preset threshold value corresponding to the core service;
under the condition that the service connection state is a fusing state, switching the service connection state into a semi-fusing state after a first preset time period;
if the service connection state is the semi-fusing state, if the resource use state is detected to be not smaller than a fourth preset threshold value, switching the service connection state to the fusing state; and if the resource use state is continuously smaller than the fourth preset threshold value within the second preset time period, switching the service connection state into a normal state.
As an optional implementation manner, after the matching module acquires the target state information, the matching module may determine the matching state of the target state information and the target current limiting rule in the following manner:
under the condition that the access flow state is not smaller than a first preset threshold value, determining that the target state information is matched with a first current limiting rule;
Under the condition that the access flow state is smaller than a first preset threshold value, determining that the target state information is not matched with the first current limiting rule, and determining the matching state of the target state information and the second current limiting rule according to the service priority, the resource use state and the service connection state at the moment, specifically:
under the condition that the service connection state is a fusing state, determining that the target state information is matched with a second current limiting rule;
under the condition that the service connection state is a semi-fusing state, determining a second preset threshold corresponding to the service priority of the target service; under the condition that the resource use state is not smaller than a second preset threshold value, determining that the target state information is matched with a second current limiting rule; under the condition that the resource use state is smaller than a second preset threshold value, determining that the target state information is not matched with a second current limiting rule;
and under the condition that the service connection state is a normal state, determining that the target state information is not matched with the second current limiting rule.
Optionally, in the case that the target state information matches the first current limiting rule, the current limiting module may perform current limiting processing on the target service request by: queuing the target service request under the condition that the access flow state is not smaller than a first preset threshold value and smaller than a third preset threshold value, wherein the service in the queue is processed according to the service priority from high to low; and under the condition that the access flow state is not smaller than a third preset threshold value, rejecting the target service request.
Optionally, in the case that the target state information matches the second current limiting rule, the current limiting module may perform current limiting processing on the target service request in the following manner: under the condition that the service connection state is a fusing state, rejecting the target service request; and queuing the target service request under the condition that the service connection state is a semi-fusing state and the resource use state is not less than a second preset threshold, wherein the service in the queue is processed according to the service priority from high to low.
It should be noted that, the first preset threshold, the second preset threshold, the third preset threshold, the fourth preset threshold, the first preset duration and the second preset duration are all set by the user according to the requirement when configuring the target current limiting rule, and the values are only used as an illustration and do not constitute an actual limitation.
As an alternative implementation manner, when the target service does not meet the target throttling rule, that is, does not need to perform the throttling operation, the issuing module may issue the token to the client in the following manner: determining a token corresponding to the target service from a preset token bucket; and issuing the token to the client, wherein the client is used for resending the target service request carrying the token to the server, and the server only processes the service request carrying the token.
Optionally, in the service current limiting device provided in the embodiment of the present application, the service current limiting device further includes a query module, configured to respond to a status query operation of a target object, and display status information corresponding to the status query operation, where the status information includes at least one of the following: the method comprises the steps of accessing a flow state, a resource using state of a server side and a service connection state with the server side at present; and the method is also used for responding to the log query operation of the target object and displaying log information corresponding to the log query operation, wherein the log information comprises the following steps: processing log information of all the intercepted businesses in a preset time period.
In the embodiment of the application, an interception module intercepts a target service request aiming at a target service, which is sent to a server by a client; the matching module obtains target state information, wherein the target state information at least comprises: determining whether the target state information is matched with a target current limiting rule or not according to the current access flow state, the service priority of the target service, the resource use state of the server and the service connection state of the server; if the target state information is matched with the target flow limiting rule, the flow limiting module performs flow limiting processing on the target service request, including queuing processing or refusing processing; if the target state information is not matched with the target current limit rule, the issuing module issues a token to the client, and the token is the basis for processing the target service request by the server. The method and the system for limiting the flow of the service can effectively solve the technical problems of single service flow limiting mode and poor effect in the related technology by comprehensively considering information such as access flow, service priority, server side state and the like and utilizing comprehensive and reliable flow limiting rules obtained by combining various flow limiting strategies to limit the flow of the service, thereby improving the stability of system service in a multi-service concurrency scene.
The traffic flow limiting device comprises a processor and a memory, the interception module 71, the matching module 72, the flow limiting module 73, the issuing module 74 and the like are all stored in the memory as program units, and the processor executes the program units stored in the memory to realize corresponding functions.
The processor includes a kernel, and the kernel fetches the corresponding program unit from the memory. The kernel can be provided with one or more than one, and the service flow limiting method is realized by adjusting kernel parameters.
The memory may include volatile memory, random Access Memory (RAM), and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM), among other forms in computer readable media, the memory including at least one memory chip.
The embodiment of the application provides a computer readable storage medium, on which a program is stored, which when executed by a processor, implements the service throttling method described above.
The embodiment of the application provides a processor, which is used for running a program, wherein the service flow limiting method is executed when the program runs.
As shown in fig. 8, an embodiment of the present application provides an electronic device, where the electronic device includes a processor, a memory, and a program stored on the memory and executable on the processor, and when the processor executes the program, the following steps are implemented: intercepting a target service request aiming at a target service, which is sent to a server by a client; acquiring target state information and determining a matching state of the target state information and a target current limiting rule, wherein the target state information at least comprises: the method comprises the steps of accessing a flow state, a service priority of a target service, a resource use state of a server side and a service connection state with the server side at present; and under the condition that the target state information is matched with the target flow limiting rule, performing flow limiting processing on the target service request, wherein the flow limiting processing comprises one of the following steps: queuing and refusing; and under the condition that the target state information is not matched with the target current limiting rule, a token is issued to the client, wherein the token is the basis for processing the target service request by the server.
The device herein may be a server, PC, PAD, cell phone, etc.
The present application also provides a computer program product adapted to perform, when executed on a data processing device, a program initialized with the method steps of: intercepting a target service request aiming at a target service, which is sent to a server by a client; acquiring target state information and determining a matching state of the target state information and a target current limiting rule, wherein the target state information at least comprises: the method comprises the steps of accessing a flow state, a service priority of a target service, a resource use state of a server side and a service connection state with the server side at present; and under the condition that the target state information is matched with the target flow limiting rule, performing flow limiting processing on the target service request, wherein the flow limiting processing comprises one of the following steps: queuing and refusing; and under the condition that the target state information is not matched with the target current limiting rule, a token is issued to the client, wherein the token is the basis for processing the target service request by the server.
It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In one typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, etc., such as Read Only Memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.
Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises an element.
The foregoing is merely exemplary of the present application and is not intended to limit the present application. Various modifications and changes may be made to the present application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc. which are within the spirit and principles of the present application are intended to be included within the scope of the claims of the present application.

Claims (14)

1. A traffic throttling method, comprising:
intercepting a target service request aiming at a target service, which is sent to a server by a client;
acquiring target state information and determining a matching state of the target state information and a target current limiting rule, wherein the target state information at least comprises: the current access flow state, the service priority of the target service, the resource use state of the server and the service connection state with the server;
And carrying out flow limiting processing on the target service request under the condition that the target state information is matched with the target flow limiting rule, wherein the flow limiting processing comprises one of the following steps: queuing and refusing;
and under the condition that the target state information is not matched with the target current limiting rule, issuing a token to the client, wherein the token is the basis for the server to process the target service request.
2. The method of claim 1, wherein the step of determining the position of the substrate comprises,
the access traffic state includes one of: accessing a data flow value and a concurrent thread quantity value;
the resource use state of the server side comprises one of the following: the current processing service quantity, the CPU utilization rate of the central processing unit and the IO utilization rate of input and output;
the service connection state includes one of: the system comprises a fusing state, a semi-fusing state and a normal state, wherein in the fusing state, all access requests to the server are refused, in the semi-fusing state, part of access requests to the server are allowed, and in the normal state, all access requests to the server are allowed.
3. The method of claim 2, wherein the target current limit rule comprises a first current limit rule and a second current limit rule, and determining a matching state of the target state information and the target current limit rule comprises:
Under the condition that the access flow state is not smaller than a first preset threshold value, determining that the target state information is matched with the first current limiting rule;
and under the condition that the access flow state is smaller than the first preset threshold value, determining that the target state information is not matched with the first current limiting rule, and determining the matching state of the target state information and the second current limiting rule according to the service priority, the resource using state and the service connection state.
4. The method of claim 3, wherein determining a matching state of the target state information and the second throttling rule based on the traffic priority, the resource usage state, and the service connection state comprises:
determining that the target state information is matched with the second current limiting rule under the condition that the service connection state is the fusing state;
determining a second preset threshold corresponding to the service priority of the target service under the condition that the service connection state is the semi-fusing state, wherein the second preset threshold corresponding to the high-priority service is larger than the second preset threshold corresponding to the low-priority service;
Determining that the target state information is matched with the second current limiting rule under the condition that the resource use state is not smaller than the second preset threshold value;
determining that the target state information is not matched with the second current limiting rule under the condition that the resource use state is smaller than the second preset threshold value;
and under the condition that the service connection state is the normal state, determining that the target state information is not matched with the second current limiting rule.
5. A method according to claim 3, wherein, in case the target state information matches the target current limit rule, performing current limit processing on the target service request comprises:
queuing the target service request under the condition that the access flow state is not smaller than the first preset threshold value and smaller than a third preset threshold value, wherein the service in the queue is processed according to the service priority from high to low;
and under the condition that the access flow state is not smaller than the third preset threshold value, rejecting the target service request.
6. The method of claim 4, wherein, in the case that the target state information matches the target current limit rule, performing current limit processing on the target service request comprises:
Under the condition that the service connection state is the fusing state, rejecting the target service request;
and queuing the target service request under the condition that the service connection state is the semi-fusing state and the resource use state is not smaller than the second preset threshold, wherein the service in the queue is processed according to the service priority from high to low.
7. The method according to claim 2, wherein the method further comprises:
if the service connection state is the normal state, if the resource use state is detected to be not smaller than a fourth preset threshold value, switching the service connection state to the fusing state;
under the condition that the service connection state is the fusing state, switching the service connection state into the semi-fusing state after a first preset time period;
if the service connection state is the semi-fusing state, if the resource use state is detected to be not smaller than the fourth preset threshold value, switching the service connection state to the fusing state; and if the resource use state is continuously smaller than the fourth preset threshold value within the second preset time period, switching the service connection state into the normal state.
8. The method of claim 1, wherein prior to intercepting a target service request for a target service sent by a client to a server, the method further comprises:
responding to rule selection operation of a target object, and determining the target current limiting rule from a preset current limiting rule template; or alternatively, the first and second heat exchangers may be,
and configuring the target current limiting rule in response to a rule configuration operation of the target object.
9. The method of claim 1, wherein issuing a token to the client comprises:
determining the tokens corresponding to the target service from a preset token bucket;
and issuing the token to the client, wherein the client is used for resending the target service request carrying the token to the server, and the server only processes the service request carrying the token.
10. The method according to claim 1, wherein the method further comprises:
responding to a state query operation of a target object, and displaying state information corresponding to the state query operation, wherein the state information at least comprises one of the following steps: the current access flow state, the resource using state of the server side and the service connection state of the server side;
Responding to a log query operation of a target object, and displaying log information corresponding to the log query operation, wherein the log information comprises: processing log information of all the intercepted businesses in a preset time period.
11. A traffic flow limiting device, comprising:
the interception module is used for intercepting a target service request aiming at a target service, which is sent to the server by the client;
the matching module is used for acquiring target state information and determining a matching state of the target state information and a target current limiting rule, wherein the target state information at least comprises: the current access flow state, the service priority of the target service, the resource use state of the server and the service connection state with the server;
the current limiting module is configured to perform current limiting processing on the target service request when the target state information matches the target current limiting rule, where the current limiting processing includes one of the following: queuing and refusing;
and the issuing module is used for issuing a token to the client under the condition that the target state information is not matched with the target current limiting rule, wherein the token is the basis for the server to process the target service request.
12. A business processing system, comprising:
the system comprises a client, a server and a stable access platform;
wherein the stable access platform is configured to perform the traffic throttling method of any of claims 1 to 10.
13. A processor, characterized in that the processor is configured to run a program, wherein the program when run performs the traffic throttling method according to any of claims 1 to 10.
14. An electronic device comprising one or more processors and a memory for storing one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the traffic throttling method of any of claims 1-10.
CN202310457952.5A 2023-04-25 2023-04-25 Service flow limiting method, device and service processing system Pending CN116489103A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310457952.5A CN116489103A (en) 2023-04-25 2023-04-25 Service flow limiting method, device and service processing system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310457952.5A CN116489103A (en) 2023-04-25 2023-04-25 Service flow limiting method, device and service processing system

Publications (1)

Publication Number Publication Date
CN116489103A true CN116489103A (en) 2023-07-25

Family

ID=87222805

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310457952.5A Pending CN116489103A (en) 2023-04-25 2023-04-25 Service flow limiting method, device and service processing system

Country Status (1)

Country Link
CN (1) CN116489103A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117556452A (en) * 2024-01-10 2024-02-13 支付宝(杭州)信息技术有限公司 Access control method for database and related equipment

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117556452A (en) * 2024-01-10 2024-02-13 支付宝(杭州)信息技术有限公司 Access control method for database and related equipment

Similar Documents

Publication Publication Date Title
US11601512B2 (en) System and method for throttling service requests having non-uniform workloads
US9729557B1 (en) Dynamic throttling systems and services
US9369389B1 (en) Dynamic isolation of shared resources
US10908950B1 (en) Robotic process automation system with queue orchestration and task prioritization
US11456965B2 (en) Network service request throttling system
US10700994B2 (en) Multi-tenant throttling approaches
US10013662B2 (en) Virtual resource cost tracking with dedicated implementation resources
US11106479B2 (en) Virtual provisioning with implementation resource boundary awareness
US10432551B1 (en) Network request throttling
US11762699B2 (en) Assignment of resources to database connection processes based on application information
US9197687B2 (en) Prioritized blocking of on-demand requests
US7694054B2 (en) Governing access to a computing resource
US20150199219A1 (en) Method and apparatus for server cluster management
CN110069911B (en) Access control method, device, system, electronic equipment and readable storage medium
US10305974B2 (en) Ranking system
CN110018781B (en) Disk flow control method and device and electronic equipment
CN106533961B (en) Flow control method and device
CN116489103A (en) Service flow limiting method, device and service processing system
CN115190078A (en) Access flow control method, device, equipment and storage medium
US20150341282A1 (en) Context-aware portal connection allocation
CN112866131B (en) Traffic load balancing method, device, equipment and medium
US9479579B2 (en) Grouping processing method and system
CN108153685A (en) It is a kind of to handle the method, apparatus of request and equipment, readable medium
CN108243225B (en) Distributed system, management method and access method
CN117354247A (en) Multi-dimensional current limiting method, system, storage medium and processor

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination