CN113238875A - Queue-based request frequency control system and control method - Google Patents
Queue-based request frequency control system and control method Download PDFInfo
- Publication number
- CN113238875A CN113238875A CN202110456042.6A CN202110456042A CN113238875A CN 113238875 A CN113238875 A CN 113238875A CN 202110456042 A CN202110456042 A CN 202110456042A CN 113238875 A CN113238875 A CN 113238875A
- Authority
- CN
- China
- Prior art keywords
- module
- queue
- request
- service
- task
- 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
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/546—Message passing systems or structures, e.g. queues
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
- G06F9/4881—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/48—Indexing scheme relating to G06F9/48
- G06F2209/484—Precedence
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/54—Indexing scheme relating to G06F9/54
- G06F2209/548—Queue
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer And Data Communications (AREA)
Abstract
A request frequency control system and a control method based on a queue are provided, the request frequency control system comprises a client and a system server, and the client is connected with the system server to realize request sending and task result receiving; the system server comprises a Broker module, a Worker module, a Limiter module, a Backend module, a Controller module and a Monitor module; the Broker module receives a request sent by a service through a client without limit, the received request is completely stored in an ordered queue, the priority of the request is used as an ordering factor, and the Worker module is waited to execute in order; the method for requesting frequency control can realize complete encapsulation of frequency control, the distributed design naturally supports transverse expansion, huge throughput is met, the method is simple and easy to use, the service can realize butt joint only by introducing a specified code base and setting a small amount of configuration, and custom expansion can be realized.
Description
Technical Field
The invention belongs to the field of network information processing, and particularly relates to a request frequency control system and a request frequency control method based on a queue.
Background
In the current information age, various industries are in informationized development, and the participants of the industries form a huge and complicated information ecology. To enter the ecology, the individual has essential information and more importantly needs to be connected with other target objects. This involves programmatic interface API (application Programming interface) interfacing. Specifically, an interface is exposed by the service provider, and the user of the service can obtain the desired result by calling the interface to enter the appropriate parameters. For example, the weather station is used as a service provider to expose a weather forecast interface, and the user can obtain the weather condition of the target area at the specified time only by providing the geographic coordinates and the time range. In this way, the service usage unit establishes an active connection with the weather station. However, as more and more users establish connections with weather stations, in order to obtain more timely weather changes, some users initiate more frequent queries, or hackers initiate network attacks and continuously initiate weather queries, which finally results in too much service pressure of the service provider and makes the service unavailable. The service provider will take some measures to avoid this foreseeable situation, and the basic measures are: 1. and (4) authenticating the authority. Each service user is given a unique identity and a corresponding authentication signature. All service users are ensured to have a record on the provider, and requests with unknown sources do not provide services, and only corresponding error codes are returned. 2. And (5) controlling the frequency. The existing service user can not initiate requests without limit, and must satisfy how many qps (queries Per second) cannot be exceeded, and more complicated, the requests can be graded according to the service types. For the service provider, when receiving the request of exceeding quota from the registered service user, the service provider does not execute the service logic, and the range directly corresponds to the error code. If the number of errors is too large, degradation or a shutdown operation is performed on the user side. Thus, the purposes of controlling frequency and reducing service pressure can be achieved. It is obviously not correct for the service user that a normal service request has an error code, and it is acceptable if the service can be retried only by a polling operation, but not acceptable if it is a non-idempotent operation.
Disclosure of Invention
The invention aims to provide a queue-based request frequency control system and a queue-based request frequency control method for solving the problem that the request frequency of a service user is over-limited under the condition that the complexity is continuously increased in the prior art, so that the service user can be ensured to work stably.
In order to achieve the purpose, the invention has the following technical scheme:
a request frequency control system based on a queue comprises a client and a system server, and the client is connected with the system server to realize request sending and task result receiving; the system server comprises a Broker module, a Worker module, a Limiter module, a Backend module, a Controller module and a Monitor module;
the Broker module is used for receiving a request Task sent by a service through a client without limit, all received requests are grouped and stored in an ordered queue by using a Topic, and the priority of the request is used as an ordering factor to wait for the execution of the Broker module in sequence;
the Worker module takes the request object from the ordered queue according to the priority and executes the request object, the execution result is transmitted to the backup module and then called back to the service, and the execution frequency is controlled by the Limiter module;
the Limiter module is used for setting the highest outflow rate limit and realizing various frequency control strategies;
the backskend module is used for storing and calling back an execution result of the Worker module to the client side to touch the service system;
the Controller module is used for receiving a control instruction to maintain a system and adjust a queue;
the Monitor module is used for monitoring various state indexes required by the system, including a service state and a self running state.
As a preferred scheme of the request frequency control system of the present invention, the Worker module controls the consumption rate according to the frequency controller specified by the target platform in combination with the corresponding configuration parameters.
As a preferred solution of the request frequency control system of the present invention, the frequency control strategy implemented by the Limiter module includes the following categories:
a. a constant speed control strategy, wherein the set times are not exceeded in a certain period of time;
b. controlling the frequency according to the return value, and controlling the frequency according to the quota used condition in the request return result;
c. and (4) hierarchical control, which is to set quotas respectively according to the hierarchical structure of the service, wherein the quotas of a plurality of levels are consumed by a request sent by the client, and any overrun is regarded as overrun and a corresponding error code is returned.
As an optimal scheme of the request frequency control system, the backup module calls back an Http URL, and calls back a service through the address after a task is completed; or MQ or Kafka is used to enable the task results to be backlogged to a certain extent, and the pressure of the Worker module consumption speed is reduced.
As a preferred embodiment of the request frequency control system of the present invention, the queue adjustment that can be performed by the Controller module includes emptying, suspending, and resuming the designated queue.
As a preferred solution of the request frequency control system of the present invention, the service state includes: a service access service list and the health state thereof, a butted platform list and the health state thereof, a Topic list, the backlog condition of each queue, the task consumption duration and the error rate;
the self-running state comprises the following steps: memory, CPU use case, operation and maintenance operation record and pressure curve.
As an optimal scheme of the request frequency control system, a Manager module of a management end calls a Controller module and a Monitor module to realize daily operation and maintenance operation and visual monitoring, viewing and analysis.
The invention also provides a queue-based request frequency control method, which comprises the following steps:
the Server Broker receives the sent service Task without limit;
the Task is put in a warehouse and queued according to the priority order;
starting a Worker daemon thread to try to consume the Task in the queue, before the Task is consumed, acquiring a corresponding request token, if the request token can be taken, normally executing the Task, otherwise, judging that the Task is out of limit and cannot be executed;
if the task is normally executed, taking out the task with the highest current priority from the ordered queue; executing the current task and sending a request to a service provider platform; and receiving and storing a result returned by the service provider platform, and calling back the result to the service system.
As a preferred scheme of the request frequency control method, all steps in the operation process are recorded into an analysis library through corresponding logs for query and statistical analysis.
As a preferred scheme of the request frequency control method, the task processing speed, the response time, the error rate, the task backlog condition and the CPU and Memory use condition are monitored in the operation process, and the system pressure is analyzed.
Compared with the prior art, the invention has the following beneficial effects:
the invention can completely shield the frequency control problem to the service, the service can realize the unlimited request initiation, and the invention can execute the service request as soon as possible and call back the result to the service. The invention has stable and reliable frequency control capability, ensures the long-term stable work of the service of a service user, supports the transverse expansion and bears high throughput. The invention supports multi-point access, the front end can be connected with a plurality of services, the back end can simultaneously support a plurality of service providing platforms, and the frequency control strategy customized by various platforms is satisfied. The invention has flexible and convenient operation, only needs a small amount of configuration for the new access service, configures the frequency control strategy for explaining the target service providing platform and the corresponding frequency control strategy, and configures the parameters corresponding to the strategy. In addition, the invention can also support some high-level functions, such as supporting task priority, and the task is executed according to the priority; the task expiration time is supported, and the task with higher timeliness is not executed after expiration; and the system can be used as a task distribution system, and effectively solves the problem that a service user requests frequency control.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required to be used in the embodiments are briefly described below, it should be understood that the following drawings only show some embodiments of the present invention, and it is obvious for those skilled in the art that other related drawings can be obtained according to these drawings without creative efforts.
FIG. 1 is a schematic diagram of a conventional public storage queuing request frequency control system;
fig. 2 is a schematic structural diagram of a queue-based request frequency control system according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. Based on the embodiments of the present invention, those skilled in the art can also obtain other embodiments without creative efforts.
The existing solutions for solving the problem that the service user requests frequent control are as follows from simple to complex:
1. no control, even if the usage scenario is much less frequent than the provider requires, is not considered.
2. And (4) pausing the thread, and pausing for a period of time after the request is sent out so as to ensure that the quota is not exceeded in the whole.
3. And local queuing is suitable for a single-instance system and does not support cluster deployment of a distributed system. But at present, a somewhat larger system requires distribution.
4. The public storage queue meets the frequency control of a distributed system, multiple accesses need multiple coding, multiple configurations, too high coupling degree of frequency control logic and business logic, and the compiling and reading are all disordered. Maintenance costs will also be higher and higher as shown in fig. 1.
The above schemes can achieve the purpose of controlling frequency, and each scheme has the service complexity and the service scale which can be supported by the scheme.
Compared with the existing scheme, the queue-based request frequency control system and the queue-based request frequency control method are a scheme based on independent middleware, namely the mode adopted by the queue-based request frequency control system and the queue-based request frequency control method are completely encapsulated, so that the problem of completely shielding frequency control of services can be realized.
Referring to fig. 2, an embodiment of a queue-based request frequency control system according to the present invention includes:
the service system uses the Client (Queue-Client) to connect with a system Server (Queue-Server) to realize the work of request (task) sending and task result receiving. And setting a callback mode and corresponding parameters, and calling back the service system according to the callback mode after the system is executed, so that the service system can continue the subsequent flow.
The system Server (Queue-Server) comprises the following modules:
-a Broker module;
and the Broker module receives the tasks sent by the Client without limit, all the received services are stored in the ordered queue, the priority of the request is used as an ordering factor, and the Worker is waited to execute in sequence. The current ordered queue uses the ZSet of Redis, and in principle all containers with high concurrency capability that support ordering can be used as storage for the Broker module.
-a Worker module;
the Worker module takes the request object from the ordered queue according to the priority and executes the request object, and the execution result is transmitted to the Backend module and then called back to the service. The execution frequency is controlled by the Limiter module.
-a Limiter module;
the Limiter module is a core module of a frequency control system, and various frequency control strategies are realized. When the Worker module consumes, a proper frequency controller is selected according to the target platform to control the consumption rate by combining with the corresponding configuration parameters.
The Limiter module implements a funnel model that has no restriction on the inflow of flow, but sets the highest outflow rate limit. Namely, when the engine is operated at a small flow rate, the inflow amount is equal to the outflow amount; when the engine runs at full load, a large amount of water flows in and flows out at a constant speed, and the difference is accumulated in the storage. The frequency control strategy which can be realized by the Limiter module comprises the following steps:
1. and (5) controlling the strategy at a constant speed, wherein m seconds are not more than n times.
2. And controlling the frequency according to the return value, wherein some platforms can display the current quota utilization rate in the request result, and the frequency control strategy is realized by using the group of values.
3. And (4) hierarchical control, for example, a hierarchical structure of business APP > User > Account, one Account sends a request to simultaneously consume quotas of three levels of APP, User and Account, wherein any overrun is regarded as overrun, and a corresponding error code is returned.
The three types basically meet most frequency control scenes, and only one strategy needs to be selected and strategy parameters need to be set when one service providing platform is accessed.
-a Backend module;
the backup module is responsible for calling back to the Client so as to reach the service system. The simplest Backend module can call back the Http URL, and call back the service by changing the address after the task is completed, so that the service task result processing capability has higher throughput, Load Balancing (LBS) service is usually increased, and a plurality of service instances are proxied. The advanced can use MQ or Kafka as Backend, and the service is connected with MQ or Kafka. Task results can be backlogged to some extent in such middleware and consumed slowly by the business system. The specific suitable scheme is determined according to the service situation.
-a Controller module;
the Controller module is used for receiving control instructions for system maintenance and adapting to some special service cases, such as emptying, suspending and resuming a designated queue.
-a Monitor module;
the Monitor module is used for providing various state indexes required by the monitoring system, including the state of the service and the running state of the Monitor module.
The service states are as follows: a service access service list and the health state thereof, a butted platform list and the health state thereof, a Topic list and queue backlog condition, task consumption duration and an error rate;
the self running state comprises the following steps: memory, CPU service conditions, operation and maintenance operation records and pressure curves.
The request frequency control system based on the Queue further comprises a Manager module, wherein the Manager module provides a visual page, and the daily operation and maintenance operation, monitoring, viewing and analysis are realized by calling a Controller module and a Monitor module of a system Server (Queue-Server). Promiscuose and Grafana are accessed to realize visual analysis.
The request frequency control system provided by the invention can realize complete encapsulation of frequency control, the server is independently deployed, the distributed design naturally supports transverse expansion, huge throughput is met, the system is simple and easy to use, and the service can realize butt joint by only introducing a specified code library and setting a small amount of configuration; the service end can realize the butt joint of the service providing platform by a small amount of configuration. The user-defined expansion can be realized, and high-level functions can be realized through a small amount of codes, for example, a user-defined execution mode of tasks can be realized by realizing a Worker execution interface; the user-defined frequency control strategy can be realized by realizing the Limiter interface. Flexible and flexible. The service system itself can also be used as a service provider, and the system can also be used as a task distribution system after the corresponding configuration is changed, and the system naturally has the frequency control characteristic.
As shown in fig. 2, the third party platforms involved, including the uppermost business system and the lowermost target service provider platform, are partially dashed. The arrows with numbers indicate the service execution process and also illustrate the interrelationship between the various constituent modules of the system.
As shown, the system is divided into three parts: queue Client, Queue Server and Queue Manager. The Queue Server is a system core, and the service system interacts with the Queue Server through a Queue Client and is mainly responsible for sending tasks and receiving results. The Queue Server realizes core logic, executes the task on the basis of meeting the frequency control condition, and returns the task result to the Queue Client. The Queue Manager is responsible for daily operation and monitoring work of the Queue Server.
A request frequency control method based on a queue comprises the following detailed steps:
the Broker of the Queue Server receives the service Task transmitted by the Client without limit.
And (2) the tasks are put in a warehouse for queuing according to the priority order, wherein an ordered queue of Redis is adopted. Other storage supporting ordering may be substituted.
3. Each frequency control strategy of each accessed service provider platform starts a Worker daemon thread, and the Worker continuously tries to consume tasks in the queue.
4. Before consuming the Task, the Limiter module is firstly used for acquiring a corresponding request token. If the description is provided with a quota, the task can be executed normally, otherwise, the description is over-limit, and the task cannot be executed (if the task is executed forcibly, the task is greatly likely to receive a corresponding error code returned by the provider).
5. Assume that step 4 determines that the task can be performed. The task with the highest current priority is taken out of the overall ordered queue.
6. And executing the current task and sending a request to the service provider platform.
7. And receiving a result returned by the service provider platform.
8. And sending the received result to a backup, wherein the backup is responsible for calling back to the Queue Client so as to touch the service system.
And 9, returning the task result to the service system by the Backend module.
At this point, the tasks of a business system are completed. This is the core logic. Of course, at each step, the corresponding log records are entered into an Analysis library (Analysis) for query Analysis by the Queue Manager.
The detailed steps carried out by the Queue Manager end are as follows:
1. and (5) daily operation and maintenance. And the control interface provided by the Controller is called through the page, so that the method and the system realize the functions of pause and recovery of Topic, queue emptying, checking of specified tasks, changing of worker configuration and changing of Limiter configuration. And (5) suspending the service system connection and suspending the service provider connection.
2. And (5) monitoring and analyzing. And analyzing the system traffic and analyzing the system pressure. Such as the processing speed, response time, task backlog condition of various types of Topic tasks, and the application condition of CPU and Memory of the device. Promiscuuose and Grafana were accessed for visual analysis.
The invention can completely shield the frequency control problem for the service and can initiate the request without limit. Therefore, the invention can be pertinently applied to the background that the business scale is continuously large and the complexity is continuously increased, and ensures the long-term stable work of a service user.
The above-mentioned embodiments are only preferred embodiments of the present invention, and are not intended to limit the technical solution of the present invention, and it should be understood by those skilled in the art that the technical solution can be modified and replaced by a plurality of simple modifications and replacements without departing from the spirit and principle of the present invention, and the modifications and replacements also fall into the protection scope covered by the claims.
Claims (10)
1. A request frequency control system based on a queue is characterized by comprising a client and a system server, wherein the client is connected with the system server to realize request sending and task result receiving; the system server comprises a Broker module, a Worker module, a Limiter module, a Backend module, a Controller module and a Monitor module;
the Broker module is used for receiving a request Task sent by a service through a client without limit, all received requests are grouped and stored in an ordered queue by using a Topic, and the priority of the request is used as an ordering factor to wait for the execution of the Broker module in sequence;
the Worker module takes the request object from the ordered queue according to the priority and executes the request object, the execution result is transmitted to the backup module and then called back to the service, and the execution frequency is controlled by the Limiter module;
the Limiter module is used for setting the highest outflow rate limit and realizing various frequency control strategies;
the backskend module is used for storing and calling back an execution result of the Worker module to the client side to touch the service system;
the Controller module is used for receiving a control instruction to maintain a system and adjust a queue;
the Monitor module is used for monitoring various state indexes required by the system, including a service state and a self running state.
2. The queue-based request frequency control system of claim 1, wherein: and the Worker module controls the consumption rate according to the frequency controller appointed by the target platform and the corresponding configuration parameters.
3. The queue-based request frequency control system of claim 1, wherein the frequency control strategy implemented by the Limiter module comprises the following categories:
a. a constant speed control strategy, wherein the set times are not exceeded in a certain period of time;
b. controlling the frequency according to the return value, and controlling the frequency according to the quota used condition in the request return result;
c. and (4) hierarchical control, which is to set quotas respectively according to the hierarchical structure of the service, wherein the quotas of a plurality of levels are consumed by a request sent by the client, and any overrun is regarded as overrun and a corresponding error code is returned.
4. The queue-based request frequency control system of claim 1, wherein the callback module calls back Http URL, and calls back service through the address after the task is completed; or MQ or Kafka is used to enable the task results to be backlogged to a certain extent, and the pressure of the Worker module consumption speed is reduced.
5. The queue-based request frequency control system of claim 1, wherein the queue adjustments that the Controller module can make include emptying, suspending, and resuming a specified queue.
6. The queue-based request frequency control system of claim 1, wherein the traffic state comprises: a service access service list and the health state thereof, a butted platform list and the health state thereof, a Topic list, the backlog condition of each queue, the task consumption duration and the error rate;
the self-running state comprises the following steps: memory, CPU use case, operation and maintenance operation record and pressure curve.
7. The queue-based request frequency control system of claim 1, wherein a Manager module calls a Controller and a Monitor module to implement daily operation and maintenance operations and visual monitoring, viewing and analysis.
8. A queue-based request frequency control method, wherein the queue-based control request frequency control system according to any one of claims 1 to 7 operates, and comprises the following steps:
the Server Broker receives the sent service Task without limit;
the Task is put in a warehouse and queued according to the priority order;
starting a Worker daemon thread to try to consume the Task in the queue, before the Task is consumed, acquiring a corresponding request token, if the request token can be taken, normally executing the Task, otherwise, judging that the Task is out of limit and cannot be executed;
if the task is normally executed, taking out the task with the highest current priority from the ordered queue; executing the current task and sending a request to a service provider platform; and receiving and storing a result returned by the service provider platform, and calling back the result to the service system.
9. The queue-based request frequency control method according to claim 8, wherein: and recording each step in the operation process into an analysis library through a corresponding log so as to be used for inquiry and statistical analysis.
10. The queue-based request frequency control method according to claim 8, wherein: and in the operation process, the task processing speed, the response time, the error rate, the task backlog condition and the CPU and Memory use condition are monitored, and the system pressure is analyzed.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110456042.6A CN113238875A (en) | 2021-04-26 | 2021-04-26 | Queue-based request frequency control system and control method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110456042.6A CN113238875A (en) | 2021-04-26 | 2021-04-26 | Queue-based request frequency control system and control method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113238875A true CN113238875A (en) | 2021-08-10 |
Family
ID=77129367
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110456042.6A Pending CN113238875A (en) | 2021-04-26 | 2021-04-26 | Queue-based request frequency control system and control method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113238875A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113626247A (en) * | 2021-08-26 | 2021-11-09 | 宁波菊风系统软件有限公司 | Error code transmission method in distributed system |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8423662B1 (en) * | 2003-04-28 | 2013-04-16 | Akamai Technologies, Inc. | Forward request queuing in a distributed edge processing environment |
| CN108848037A (en) * | 2018-05-31 | 2018-11-20 | 平安医疗科技有限公司 | Service request processing method, device, computer equipment and storage medium |
| CN111782692A (en) * | 2020-06-01 | 2020-10-16 | 京东数字科技控股有限公司 | Frequency control method and device |
| CN111901249A (en) * | 2020-07-31 | 2020-11-06 | 深圳前海微众银行股份有限公司 | Service current limiting method, device, equipment and storage medium |
-
2021
- 2021-04-26 CN CN202110456042.6A patent/CN113238875A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8423662B1 (en) * | 2003-04-28 | 2013-04-16 | Akamai Technologies, Inc. | Forward request queuing in a distributed edge processing environment |
| CN108848037A (en) * | 2018-05-31 | 2018-11-20 | 平安医疗科技有限公司 | Service request processing method, device, computer equipment and storage medium |
| CN111782692A (en) * | 2020-06-01 | 2020-10-16 | 京东数字科技控股有限公司 | Frequency control method and device |
| CN111901249A (en) * | 2020-07-31 | 2020-11-06 | 深圳前海微众银行股份有限公司 | Service current limiting method, device, equipment and storage medium |
Non-Patent Citations (3)
| Title |
|---|
| JOSEPH DOYLE: "An experimental evaluation of Distributed Rate Limiting for cloud computing applications", 《2010 ACM/IEEE SYMPOSIUM ON ARCHITECTURES FOR NETWORKING AND COMMUNICATIONS SYSTEMS (ANCS)》 * |
| 张立敏等: "基于QoS的自适应控制中间件研究与应用", 《电脑知识与技术》 * |
| 朱育发: "《jQuery与jQuery Mobile开发完全技术宝典》", 31 October 2014 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113626247A (en) * | 2021-08-26 | 2021-11-09 | 宁波菊风系统软件有限公司 | Error code transmission method in distributed system |
| CN113626247B (en) * | 2021-08-26 | 2024-03-22 | 宁波菊风系统软件有限公司 | Error code transmission method in distributed system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2018130163A1 (en) | Scheduling method and device for mobile cloud computing platform | |
| CN109684358B (en) | Data query method and device | |
| CN101981531B (en) | Aggregating recurrent schedules to optimize resource consumption | |
| US8700931B2 (en) | Method and system for managing power of a mobile device | |
| CN102255935B (en) | Cloud service consuming method, cloud service intermediary and cloud system | |
| Yang et al. | An algorithm in SwinDeW-C for scheduling transaction-intensive cost-constrained cloud workflows | |
| WO2021258753A1 (en) | Service processing method and apparatus, and electronic device and storage medium | |
| CN102567106B (en) | Task scheduling method, system and device | |
| CN102075554B (en) | Service processing method and system based on SOA (Service Oriented Architecture) | |
| CN103902646A (en) | Distributed task managing system and method | |
| CN110336859B (en) | Task scheduling system under multi-tenant environment | |
| CN111338791A (en) | Method, device and equipment for scheduling cluster queue resources and storage medium | |
| CN111010426A (en) | Message pushing method and device | |
| CN113422842B (en) | Distributed power utilization information data acquisition system considering network load | |
| CN101795443A (en) | Service reminder method, service reminder system and communication system | |
| US20140092737A1 (en) | Traffic control method and traffic control apparatus | |
| CN111614550A (en) | Optimized integrated gateway of electric power marketing service system | |
| CN102780933A (en) | Method and television for acquiring user information | |
| CN111240864A (en) | Asynchronous task processing method, device, equipment and computer readable storage medium | |
| CN113238875A (en) | Queue-based request frequency control system and control method | |
| US8458716B2 (en) | Enterprise resource planning with asynchronous notifications of background processing events | |
| WO2019029721A1 (en) | Task scheduling method, apparatus and device, and storage medium | |
| CN104735134B (en) | A kind of method and apparatus serviced for providing calculating | |
| CN111427674A (en) | Micro-service management method, device and system | |
| US10635997B1 (en) | Finite life instances |
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 |