CN113986391B - Request processing method, device, medium and computing equipment - Google Patents
Request processing method, device, medium and computing equipment Download PDFInfo
- Publication number
- CN113986391B CN113986391B CN202111272611.8A CN202111272611A CN113986391B CN 113986391 B CN113986391 B CN 113986391B CN 202111272611 A CN202111272611 A CN 202111272611A CN 113986391 B CN113986391 B CN 113986391B
- Authority
- CN
- China
- Prior art keywords
- current limiting
- call request
- limiting configuration
- call
- logic
- 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.)
- Active
Links
- 238000003672 processing method Methods 0.000 title abstract description 12
- 230000000670 limiting effect Effects 0.000 claims abstract description 311
- 238000012545 processing Methods 0.000 claims abstract description 90
- 238000000034 method Methods 0.000 claims abstract description 48
- 230000015556 catabolic process Effects 0.000 claims abstract description 39
- 238000006731 degradation reaction Methods 0.000 claims abstract description 39
- 230000003068 static effect Effects 0.000 claims description 29
- 238000012544 monitoring process Methods 0.000 claims description 22
- 238000004590 computer program Methods 0.000 claims description 3
- 238000010586 diagram Methods 0.000 description 8
- 230000000694 effects Effects 0.000 description 5
- 230000002452 interceptive effect Effects 0.000 description 5
- 238000002955 isolation Methods 0.000 description 4
- 241000700189 Hystrix <Rodentia> Species 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000008901 benefit Effects 0.000 description 2
- 238000004364 calculation method Methods 0.000 description 2
- 239000013307 optical fiber Substances 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 238000009933 burial Methods 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000004883 computer application Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 210000001503 joint Anatomy 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000004366 reverse phase liquid chromatography Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
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/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
-
- 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/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Telephonic Communication Services (AREA)
Abstract
The embodiment of the disclosure provides a request processing method, a request processing device, a request processing medium and a request processing computing device. The method comprises the following steps: receiving a call request sent by a client; determining corresponding current limiting configuration according to the call request; determining whether the call request triggers a current limiting operation based on the current limiting configuration; and executing multi-stage degradation logic processing under the condition that the call request is determined to trigger a current limiting operation. The method and the device can realize differentiated current limiting on the call request, and simultaneously can relieve the operation pressure of the server and improve the stability of the server.
Description
Technical Field
Embodiments of the present disclosure relate to the field of computer application technology, and more particularly, to a request processing method, apparatus, medium, and computing device.
Background
This section is intended to provide a background or context to the embodiments of the disclosure recited in the claims. The description herein is not admitted to be prior art by inclusion in this section.
Nowadays, application (APP) is becoming more and more rich in kinds and functions, for example: a user may listen to a song or watch video related to a song, etc. through a music application. Currently, the main-stream music application programs can provide massive songs or videos for users, so that the users generally need to initiate a query request to a server corresponding to the music application program through a client corresponding to the music application program, so as to query a music library provided by the server for songs or videos which the users want to listen to.
However, if the number of users querying music in the music library is large in a period of time, the flow of the query request received by the server is large, which is very likely to cause the operation pressure of the server to be too high. In such cases, it is often difficult for the server to provide query results to the user, thereby affecting the user experience.
Disclosure of Invention
In this context, embodiments of the present disclosure desire to provide a request processing method, apparatus, medium, and computing device.
In a first aspect of embodiments of the present disclosure, there is provided a request processing method, the method including:
Receiving a call request sent by a client;
determining corresponding current limiting configuration according to the call request;
Determining whether the call request triggers a current limiting operation based on the current limiting configuration;
And executing multi-stage degradation logic processing under the condition that the call request is determined to trigger a current limiting operation.
Optionally, the call request includes a service identifier corresponding to the service logic to be called;
the determining the corresponding current limiting configuration according to the call request comprises the following steps:
And acquiring the flow limiting configuration corresponding to the service logic from a database for storing the preset flow limiting configuration based on the service identifier in the call request.
Optionally, based on the service identifier in the call request, the obtaining the corresponding current limiting configuration from the database for storing the preset current limiting configuration includes:
constructing a current limiting keyword based on the service identifier in the call request, and searching a current limiting configuration corresponding to the current limiting keyword in a database for storing preset current limiting configuration;
and determining the found current limiting configuration as the current limiting configuration corresponding to the service logic.
Optionally, the determining the found current limit configuration as the current limit configuration corresponding to the service logic includes:
If the current limiting configuration corresponding to the current limiting keyword is found in the database, determining the found current limiting configuration as the current limiting configuration corresponding to the business logic;
If the current limiting configuration corresponding to the current limiting keyword is not found in the database, a default current limiting configuration is created for the current limiting keyword in the database based on preset current limiting configuration parameters, and the default current limiting configuration is determined to be the current limiting configuration corresponding to the business logic.
Optionally, the current limiting configuration includes one or more of the following: query rate QPS per second current limiting configuration; thread number current limiting configuration;
the QPS current limiting configuration includes: the number of call requests acquired in each second reaches a preset first threshold;
the thread count current limiting configuration comprises: the number of threads for responding to the call request reaches a preset second threshold.
Optionally, the performing multi-stage degradation logic processing in the case that the call request is determined to trigger the current limiting operation includes:
determining whether preset call request degradation logic is configured;
If the call request demotion logic is configured, executing the call request demotion logic, demoting the call request, and determining whether the demoted call request triggers a current limiting operation or not based on the current limiting configuration;
if the demoted call request does not trigger the current limiting operation, calling service logic corresponding to the demoted call request, and determining a call result as a processing result of multistage demotion logic processing;
If the call request demotion logic is not configured, or the demoted call request triggers a current limiting operation, determining whether a preset static call result is configured;
And if the static call result is configured, determining the static call result as a processing result of multistage degradation logic processing.
Optionally, the method further comprises:
and if the static call result is not configured, determining a null value as a processing result of the multistage degradation logic processing.
Optionally, the downgrade processing of the call request includes:
And simplifying the call parameters in the call request.
Optionally, the method further comprises:
monitoring the current limiting probability of the received call request, and generating a corresponding monitoring log;
And adjusting the current limiting configuration parameters in the current limiting configuration based on the current limiting probability recorded in the monitoring log.
Optionally, the method further comprises:
and returning the processing result of the multistage degradation logic processing to the client.
In a second aspect of the embodiments of the present disclosure, there is provided a request processing apparatus, the apparatus comprising:
The receiving module is used for receiving a call request sent by the client;
the first determining module is used for determining the corresponding current limiting configuration according to the calling request;
The second determining module is used for determining whether the call request triggers a current limiting operation or not based on the current limiting configuration;
and the execution module is used for executing multistage degradation logic processing under the condition that the calling request is determined to trigger the current limiting operation.
Optionally, the call request includes a service identifier corresponding to the service logic to be called;
The first determining module is specifically configured to:
And acquiring the flow limiting configuration corresponding to the service logic from a database for storing the preset flow limiting configuration based on the service identifier in the call request.
Optionally, the first determining module is specifically configured to:
constructing a current limiting keyword based on the service identifier in the call request, and searching a current limiting configuration corresponding to the current limiting keyword in a database for storing preset current limiting configuration;
and determining the found current limiting configuration as the current limiting configuration corresponding to the service logic.
Optionally, the first determining module is specifically configured to:
If the current limiting configuration corresponding to the current limiting keyword is found in the database, determining the found current limiting configuration as the current limiting configuration corresponding to the business logic;
If the current limiting configuration corresponding to the current limiting keyword is not found in the database, a default current limiting configuration is created for the current limiting keyword in the database based on preset current limiting configuration parameters, and the default current limiting configuration is determined to be the current limiting configuration corresponding to the business logic.
Optionally, the current limiting configuration includes one or more of the following: query rate QPS per second current limiting configuration; thread number current limiting configuration;
the QPS current limiting configuration includes: the number of call requests acquired in each second reaches a preset first threshold;
the thread count current limiting configuration comprises: the number of threads for responding to the call request reaches a preset second threshold.
Optionally, the execution module is specifically configured to:
determining whether preset call request degradation logic is configured;
If the call request demotion logic is configured, executing the call request demotion logic, demoting the call request, and determining whether the demoted call request triggers a current limiting operation or not based on the current limiting configuration;
if the demoted call request does not trigger the current limiting operation, calling service logic corresponding to the demoted call request, and determining a call result as a processing result of multistage demotion logic processing;
If the call request demotion logic is not configured, or the demoted call request triggers a current limiting operation, determining whether a preset static call result is configured;
And if the static call result is configured, determining the static call result as a processing result of multistage degradation logic processing.
Optionally, the execution module is further configured to:
and if the static call result is not configured, determining a null value as a processing result of the multistage degradation logic processing.
Optionally, the execution module is specifically configured to:
And simplifying the call parameters in the call request.
Optionally, the apparatus further comprises:
The monitoring module is used for monitoring the current limiting probability of the received call request and generating a corresponding monitoring log;
And the adjusting module is used for adjusting the current limiting configuration parameters in the current limiting configuration based on the current limiting probability recorded in the monitoring log.
Optionally, the apparatus further comprises:
and the return module is used for returning the processing result of the multistage degradation logic processing to the client.
In a third aspect of the disclosed embodiments, a medium is provided on which a computer program is stored, which when executed by a processor implements any of the above-described request processing methods.
In a fourth aspect of embodiments of the present disclosure, there is provided a computing device comprising:
A processor;
a memory for storing a processor executable program;
Wherein the processor implements any of the request processing methods described above by running the executable program.
According to the embodiment of the disclosure, a corresponding current limiting configuration can be determined according to a received call request, and when the call request is determined to trigger a current limiting operation based on the current limiting configuration, multistage degradation logic processing is performed. By adopting the mode, the differentiated current limiting of the scheduling request can be realized, meanwhile, the operation pressure of the server can be relieved, and the stability of the server is improved.
Drawings
The above, as well as additional purposes, features, and advantages of exemplary embodiments of the present disclosure will become readily apparent from the following detailed description when read in conjunction with the accompanying drawings. Several embodiments of the present disclosure are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings, in which:
FIG. 1 schematically illustrates a schematic diagram of an application scenario of request processing according to an embodiment of the present disclosure;
FIG. 2A schematically illustrates a schematic diagram of a user interface according to an embodiment of the present disclosure;
FIG. 2B schematically illustrates a schematic diagram of another user interface according to an embodiment of the present disclosure;
FIG. 3 schematically illustrates a flow chart of a request processing method according to an embodiment of the disclosure;
FIG. 4 schematically illustrates a flow chart of a method of determining a current limit configuration, according to an embodiment of the disclosure;
FIG. 5 schematically illustrates a flow diagram of a method of performing a multi-level downgrade logic process in accordance with an embodiment of the present disclosure;
FIG. 6 schematically illustrates a schematic diagram of a medium according to an embodiment of the present disclosure;
FIG. 7 schematically illustrates a block diagram of a request processing apparatus according to an embodiment of the disclosure;
fig. 8 schematically illustrates a schematic diagram of a computing device according to an embodiment of the disclosure.
In the drawings, the same or corresponding reference numerals indicate the same or corresponding parts.
Detailed Description
The principles and spirit of the present disclosure will be described below with reference to several exemplary embodiments. It should be understood that these embodiments are presented merely to enable one skilled in the art to better understand and practice the present disclosure and are not intended to limit the scope of the present disclosure in any way. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
Those skilled in the art will appreciate that embodiments of the present disclosure may be implemented as a system, apparatus, device, method, or computer program product. Accordingly, the present disclosure may be embodied in the following forms, namely: complete hardware, complete software (including firmware, resident software, micro-code, etc.), or a combination of hardware and software.
According to an embodiment of the disclosure, a method, a device, a medium and a computing device for processing a request are provided.
In this document, it should be understood that any number of elements in the drawings is for illustration and not limitation, and that any naming is used only for distinction and not for any limitation.
The principles and spirit of the present disclosure are explained in detail below with reference to several representative embodiments thereof.
Summary of The Invention
In practical applications, when a user queries music in a music library provided by a server corresponding to a music application, a query request is generally initiated by a client corresponding to the music application, and the client sends the query request to the server. The query request may be an RPC (Remote Procedure Call ) request, for calling an RPC interface related to a music query service in the server; the RPC interface includes service logic associated with a music query service.
Correspondingly, when the server receives the RPC request, the server may call an RPC interface corresponding to the RPC request, calculate, by the RPC interface, based on the call parameter in the RPC request and the service logic in the RPC interface, and return, as a call result, a result obtained by calculating by the RPC interface to the client.
Therefore, if the number of users querying music in the music library is large in a period of time, the flow of the query request received by the server is large, and the server needs to call the interface related to the music query service multiple times, which is very likely to cause the operation pressure of the server to be too high.
In order to relieve the operation pressure of the server when the flow is large, in the related art, the query request received by the server can be limited based on Hystrix; hystrix is an open source library, and by adding delay tolerant and fault tolerant logic, the avalanche effect of the system is avoided, and a support is provided for the stability of the system. Hystrix can be divided into two types, namely thread isolation and semaphore isolation; in the thread isolation manner, more threads are usually created, and the frequency of executing the context switch by the CPU (Central Processing Unit ) is increased, so that the system performance is poor; while the manner of semaphore isolation is only applicable to current limiting in the case of no external access, and not in the case of frequent I/O (Input/Output) calls and RPCs.
Or the current limit for a certain RPC interface in the server side can be realized more simply, that is, the current limit is performed on the query request received by the server side and used for calling the RPC interface. In this case, differentiated throttling of query requests for invoking the same RPC interface cannot be achieved.
In order to solve the above-mentioned problems, the present disclosure provides a technical solution for request processing, where a corresponding current limiting configuration may be determined according to a received call request, and when it is determined that the call request triggers a current limiting operation based on the current limiting configuration, a multi-stage degradation logic process is performed. By adopting the mode, the differentiated current limiting of the scheduling request can be realized, meanwhile, the operation pressure of the server can be relieved, and the stability of the server is improved.
It should be noted that the technical solution for request processing of the present disclosure is not only applicable to the music query service described above, but also applicable to any other service involving interface call.
Having described the basic principles of the present disclosure, various non-limiting embodiments of the present disclosure are specifically described below.
Application scene overview
Typically, a user may install a client corresponding to a certain business activity in the device in which the user is using. The device can be a terminal device such as a smart phone, a tablet personal computer, a palm computer, a notebook computer, a PC (Personal Computer ), an intelligent wearable device, an intelligent vehicle-mounted device or a game machine.
The client can output a user interface related to the business activity to a user, so that the user can execute interactive operation in the user interface; the client can construct a call request corresponding to the interactive operation of the user in the user interface and send the call request to the service end corresponding to the business activity. When the service end receives the call request, the interface corresponding to the call request can be called, namely, the service logic related to the service activity in the interface is called, and the call result is returned to the client end. The server side can be specifically deployed on a single server or a server cluster and other devices.
Referring first to fig. 1, fig. 1 schematically illustrates a schematic diagram of an application scenario of request processing according to an embodiment of the present disclosure.
As shown in fig. 1, in an application scenario of request processing, a server may be included, and at least one client (e.g., clients 1-N) accessing the server. The client may be a client corresponding to a certain application program, and the server may be a server corresponding to the application program.
In practical application, the server may interface with a database for storing preset current limiting configuration, so that the received call request sent by the client may be limited based on the current limiting configuration stored in the database. The current limiting configuration may be preset by a technician according to actual requirements, or may be a default value, which is not limited in this disclosure.
Taking a music application as an example, a user may perform interactive operations related to a music query service in a user interface output from the client. The client can construct a query request corresponding to the interactive operation based on the interactive operation of the user in the user interface, and send the query request to the server; the query request is one of the above-mentioned call requests. When the service end receives the query request, the service end can call an interface corresponding to the query request, namely, call service logic related to the music query service in the interface, and return a call result to the client end.
Specifically, in one aspect, the client may output a user interface as shown in fig. 2A to a user. The user may enter relevant information (e.g., artist name, song name, music type, etc.) for the music desired to be queried in a search field 201 in the user interface. The client can construct a query request and send the query request to the server; wherein the query parameters in the query request may include information entered by the user in the search bar 201. When the service end receives the query request, the interface corresponding to the query request can be called, the interface calculates based on the calling parameters in the query request and the service logic related to the music query service in the interface, and the calling result calculated by the interface is returned to the client end.
On the other hand, the client may output a user interface as shown in fig. 2B to the user. In the user interface, results corresponding to the user-initiated query request may be presented, for example: the user can check the single-song query result corresponding to the single-song query request by clicking the single-song region 202; or the video query result corresponding to the video query request can be checked by clicking the "video" area 203; and so on.
Exemplary method
A method for request processing according to an exemplary embodiment of the present disclosure is described below with reference to fig. 3-5 in conjunction with the application scenario of fig. 1. It should be noted that the above application scenario is only shown for the convenience of understanding the spirit and principles of the present disclosure, and the embodiments of the present disclosure are not limited in any way in this respect. Rather, embodiments of the present disclosure may be applied to any scenario where applicable.
Referring to fig. 3, fig. 3 schematically illustrates a flow chart of a request processing method according to an embodiment of the present disclosure.
The above request processing method can be applied to the server shown in fig. 1; the request processing method specifically comprises the following steps:
step 301, receiving a call request sent by a client;
step 302, determining a corresponding current limiting configuration according to the call request;
Step 303, determining whether the call request triggers a current limiting operation based on the current limiting configuration;
Step 304, in the case that the call request is determined to trigger the current limiting operation, performing multistage degradation logic processing.
In this embodiment, the call request may be classified. In this case, the same flow restricting operation may be performed for the same type of call request; and different flow restricting operations may be performed for different types of call requests.
For example, the call request may be classified according to the type of business logic that the call request needs to call, or the call request may be classified according to the number of call parameters in the call request, etc.; the present disclosure is not limited in this regard.
In practical applications, the above-mentioned call request may be an RPC request for calling an RPC interface, or may be an HTTP (Hyper Text Transfer Protocol ) call request for calling an API (Application Programming Interface, application program interface), or the like; the present disclosure is not limited in this regard.
The user can initiate a call request through the client, and the client sends the call request to the server.
When the server receives the call request, the server may determine the current limiting configuration corresponding to the call request according to the call request.
In one embodiment shown, the above-described flow restricting configuration may include one or more of the following: QPS (Query Per Second) current limiting configuration; thread count current limiting configuration.
When the current limiting operation is executed, the current limiting operation corresponding to the current limiting configuration can be executed based on the Sentinel; wherein Sentinel is an open source flow control assembly.
In practical application, for a certain interface, the QPS current limiting operation may be to limit the number of call requests acquired in each second when the number of call requests exceeds a preset threshold (hereinafter referred to as a first threshold); the thread count throttling operation may be to throttle the call request when the number of threads for responding to the call request exceeds a preset threshold (hereinafter referred to as a second threshold). The first threshold value and the second threshold value may be preset by a technician according to actual requirements, or may be default values, which is not limited in the disclosure.
For example, assuming that the first threshold set for the type a of the call request is 60, it may be determined whether the number of call requests of the type a acquired in the previous second obtained by statistics exceeds 60 when the call request is acquired; if yes, the call request can be considered to trigger the QPS current limiting operation; otherwise, the invoke request may be considered to not trigger a QPS current limit operation. Assuming that the above second threshold set for type a is 20, it is possible to detect, when the call request is acquired, whether the number of threads currently used to respond to the call request of type a exceeds 20; if yes, the call request can be considered to trigger thread number current limiting operation; otherwise, the call request may be considered to not trigger a thread count throttling operation.
In the case where the current limit configuration corresponding to the above-described call request is determined, it may be determined whether the call request triggers a current limit operation based on the current limit configuration.
In practical application, when QPS current limiting is carried out on the call requests, only the number of the call requests acquired in each second is counted; while the number of threads for a call request is limited, the number of threads currently used to respond to the call request needs to be detected.
Therefore, for the above-mentioned call request, the QPS current limiting operation may be executed first, and when the call request does not trigger the QPS current limiting operation, the thread count current limiting operation is executed again; when the call request triggers the QPS current limiting operation, the thread number current limiting operation is not needed to be executed. If the call request does not trigger the thread count current limiting operation, the call request can be considered to not trigger the current limiting operation; otherwise, the invoke request may be considered to trigger a current limit operation.
Or for the call request, the thread number current limiting operation can be executed first, and when the call request does not trigger the thread number current limiting operation, the QPS current limiting operation is executed again; when the call requests to trigger the thread number limiting operation, the QPS limiting operation is not required to be executed. If the invoke request does not trigger the QPS current limit operation yet, the invoke request can be considered to not trigger the current limit operation; otherwise, the invoke request may be considered to trigger a current limit operation.
Furthermore, the QPS throttling operation and the thread count throttling operation may be performed simultaneously with respect to the call request. In this case, if the invoke request does not trigger either the QPS throttling operation or the thread count throttling operation, then the invoke request may be considered to not trigger the throttling operation; otherwise, the invoke request may be considered to trigger a current limit operation.
On the one hand, if the call request does not trigger the flow limiting operation, the service logic corresponding to the call request can be called, and the call result is returned to the client. Specifically, an interface corresponding to the call request may be called, the interface calculates based on the call parameter in the call request and the service logic corresponding to the call request in the interface, and the result obtained by calculating the interface is returned to the client as a call result.
On the other hand, if the above-mentioned call request triggers a current limiting operation, the call request may be current-limited. Specifically, a multi-level demotion logic process may be performed based on the call request.
In one embodiment, when the execution of the multi-level degradation logic process is completed, the processing result of the multi-level degradation logic process may be returned to the client, so that the client may display the processing result to the user for viewing by the user.
The determination of the current limit configuration corresponding to the call request in step 302 is described in detail below.
Referring to fig. 4, fig. 4 schematically illustrates a flow chart of a current limit configuration determination method according to an embodiment of the present disclosure.
The current limiting configuration method specifically comprises the following steps:
Step 3021, constructing a current limiting keyword based on the service identifier in the call request, and searching a current limiting configuration corresponding to the current limiting keyword in a database for storing preset current limiting configurations;
Step 3022, if the current limiting configuration corresponding to the current limiting keyword is found in the database, determining the found current limiting configuration as the current limiting configuration corresponding to the service logic;
Step 3023, if the current limiting configuration corresponding to the current limiting keyword is not found in the database, creating a default current limiting configuration for the current limiting keyword in the database based on a preset current limiting configuration parameter, and determining the default current limiting configuration as the current limiting configuration corresponding to the service logic.
In one embodiment shown, the call requests may be categorized by the type of business logic invoked.
For example, with continued reference to the user interface shown in fig. 2B, service logic associated with a music query service may be specifically classified into integrated query logic, single-song query logic, video query logic, and the like. In this case, the call request may be classified into various types of call requests such as a call request corresponding to the integrated query logic, a call request corresponding to the single-song query logic, a call request corresponding to the song query logic, and a call request corresponding to the video query logic.
Correspondingly, the call request can carry a service identifier corresponding to the service logic to be called; the service logic is the service logic corresponding to the call request. When determining the current limiting configuration corresponding to the call request, the current limiting configuration corresponding to the service logic can be obtained from a database for storing the preset current limiting configuration based on the service identifier in the call request.
In practical applications, the database may be a Key-Value type database. In the Key-Value type database, key may be a current limit Key constructed based on a service identifier corresponding to service logic, and Value may be a current limit configuration.
Or may take the form of a current limiting configuration as shown below:
Wherein the grade field may indicate the type of throttling operation, for example: "0" may represent a QPS current limit operation and "1" may represent a thread count current limit operation. The count field may represent a threshold corresponding to a current limit operation, such as: when the grade field indicates a QPS current limit operation, the count field may be the first threshold described above; when the grade field indicates a thread count throttling operation, the count field may be the second threshold described above. The resource field may represent a current limit key.
Further, in one embodiment shown, a current limit key may be constructed based on the service identifier in the call request, and a current limit configuration corresponding to the current limit key may be searched for in the database. Subsequently, the found current limit configuration may be determined as the current limit configuration corresponding to the service logic.
For example, with continued reference to the user interface shown in FIG. 2B, the user may initiate a single-shot query request by clicking on the "single-shot" area 202. At this time, the single-song query request is a call request corresponding to the single-song query logic. The service identifier corresponding to the single-shot query logic may be "song_search", and the service identifier in the call request may be "song_search".
Or the user may initiate a video query request by clicking on the "video" area 203. At this time, the video query request is a call request corresponding to the video query logic. The service identifier corresponding to the video query logic may be "video_search", and at this time, the service identifier in the call request may be "video_search".
Taking single-song query logic as an example, qps _ can be added as a prefix before the service identification of the song_search to obtain the current limiting key word of the qps song_search. The current limiting configuration corresponding to the current limiting key word is the QPS current limiting configuration corresponding to the single-song service logic, and whether the call request corresponding to the single-song service logic triggers the current limiting operation can be determined according to the QPS current limiting configuration.
Or "thread_" may be added as a prefix before the service identifier of "song_search" to obtain the current limiting key of "thread_song_search". The current limiting configuration corresponding to the current limiting key word is the thread number current limiting configuration corresponding to the single-song service logic, and whether the call request corresponding to the single-song service logic triggers the current limiting operation can be determined according to the thread number current limiting configuration.
Specifically, in one embodiment shown, on the one hand, if the current limiting configuration corresponding to the current limiting keyword is found in the database, the found current limiting configuration may be directly determined as the current limiting configuration corresponding to the service logic.
On the other hand, if the current limiting configuration corresponding to the current limiting keyword is not found in the database, a default current limiting configuration may be created for the current limiting keyword in the database based on a preset current limiting configuration parameter, and the default current limiting configuration may be determined as the current limiting configuration corresponding to the service logic.
In practical applications, the current limiting configuration parameters in the QPS current limiting configuration may include the first threshold, a type identifier corresponding to the QPS current limiting operation, a current limiting keyword corresponding to the QPS current limiting operation and service logic, and the like; the current limiting configuration parameters in the thread number current limiting configuration may include the second threshold, a type identifier corresponding to the thread number current limiting operation, a current limiting keyword corresponding to the thread number current limiting operation and business logic, and the like.
It should be noted that, the current limiting configuration parameters used to create the default current limiting configuration may be general current limiting configuration parameters, and no service is targeted. The specific values of the general current limiting configuration parameters can be preset by a technician.
The multi-stage degradation logic processing performed in step 304 is described in detail below.
Referring to fig. 5, fig. 5 schematically illustrates a flowchart of a multi-stage degradation logic process execution method according to an embodiment of the present disclosure.
The method for executing the multistage degradation logic processing specifically comprises the following steps:
Step 3041, determining whether preset call request degradation logic is configured; if the call request demotion logic is configured, executing step 3042; if the call request demotion logic is not configured, executing step 3045;
step 3042, executing the call request demotion logic, and demoting the call request;
Step 3043, determining whether the demoted call request triggers a current limiting operation based on the current limiting configuration; if the demoted call request does not trigger the current limiting operation, executing step 3044; if the demoted call request triggers a current limiting operation, executing step 3045;
step 3044, calling the service logic corresponding to the demoted call request, and determining the call result as the processing result of the multistage demotion logic processing;
step 3045, determining whether a preset static call result is configured; if the static call result is configured, executing step 3046; if the static call result is not configured, executing step 3047;
Step 3046, determining the static call result as a processing result of multistage degradation logic processing;
in step 3047, the null value is determined as the processing result of the multi-stage degradation logic processing.
In one embodiment shown, it may be determined first whether preset call request demotion logic is configured. Wherein the call request downgrade logic may be preconfigured by a technician; the call request demotion logic can be stored locally at the server side or in a database which is in butt joint with the server side and used for storing the call request demotion logic; the present disclosure is not limited in this regard.
If the call request demotion logic is configured, the call request demotion logic can be executed to demote the call request.
Specifically, in one embodiment shown, when performing the demotion processing on the above-mentioned call request, the call parameter in the call request may be subjected to the simplified processing.
For example, assume that the above-described call request is a call request corresponding to single-shot query logic; the call parameters in the call request include "audible korean songs", and the call parameters may be simplified to "korean songs" to reduce the calculation amount of single-song queries.
It should be noted that, for the demoted call request, when responding to the demoted call request, an interface corresponding to the call request still needs to be called, and the interface calculates based on the call parameters in the demoted call request and the service logic in the interface.
Therefore, after performing the demotion processing on the call request, it may be determined whether the demoted call request triggers a current limiting operation based on the current limiting configuration again.
If the demoted call request does not trigger the current limiting operation, service logic corresponding to the demoted call request can be called, and the call result is determined to be the processing result of the multistage demotion logic processing.
However, if the call request demotion logic is not configured, or the demoted call request triggers a current limit operation, it may be further determined whether a preset static call result is configured.
On the one hand, if the static call result is configured, the static call result can be directly determined as the processing result of the multistage degradation logic processing, that is, the interface corresponding to the call request is not used for calculation, so that the operation pressure of the server side is relieved.
It should be noted that the static call result may be a general call result.
For example, for a call request corresponding to single-shot query logic, the static call result may be one or more songs preset by a technician. In this case, regardless of the specific call parameters in the call request (e.g., "Zhou Jielun songs" or "audible Korean songs"), the song or songs may be directly determined as the processing result of the above-mentioned multi-level degradation logic processing, without performing the corresponding query operation.
On the other hand, if the above call request demotion logic is not configured, a null value (null) may be determined as a processing result of the multistage demotion logic processing.
In practical application, when the client receives the processing result of the null value, a text prompt of "query failure" can be output to the user so as to prompt the user to re-perform the music query.
In order to achieve a better current limiting effect, in the illustrated embodiment, the current limiting probability of the call request may also be monitored, and a corresponding monitoring log may be generated.
Specifically, call requests can be monitored through a data burial point, the number of call requests (marked as N) acquired within a period of time (for example, 1 second) is counted, the number of call requests triggering the QPS current limiting operation (marked as M 1), the number of call requests triggering the thread number current limiting operation (marked as M 2), and the QPS current limiting probability (namely, M 1/N) and the thread number current limiting probability (namely, M 2/N) are calculated.
In generating the monitoring log, the monitoring log format may be employed as follows:
[{"code":"search_total_block_tab","count":4,"threadBlockCount":0,"qpsBlockCount":1,"threadBlockRate":0.00,"qpsBlockRate":0.25}]
wherein the count field may represent the number of call requests acquired, the threadBlockCount field may represent the number of call requests triggering the thread count throttling operation, threadBlockRate may represent the thread count throttling probability, qpsBlockCount may represent the number of call requests triggering the QPS throttling operation, and qpsBlockRate may represent the QPS throttling probability.
Further, a chart for displaying the data such as the QPS current limiting probability and the thread number current limiting probability can be generated based on the monitoring log, so that the technician can conveniently check the chart.
Subsequently, based on the current limiting probability recorded in the monitoring log, the current limiting configuration parameters in the current limiting configuration can be adjusted according to actual requirements.
Specifically, if the QPS current limit probability is considered to be large, the first threshold may be appropriately increased, so that a call request for triggering the QPS current limit operation may be reduced; if the thread number limiting probability is considered to be larger, the second threshold value can be properly increased, so that the calling request for triggering the thread number limiting operation can be reduced; and so on.
According to the embodiment of the disclosure, a corresponding current limiting configuration can be determined according to a received call request, and when the call request is determined to trigger a current limiting operation based on the current limiting configuration, multistage degradation logic processing is performed. By adopting the mode, the differentiated current limiting of the scheduling request can be realized, meanwhile, the operation pressure of the server can be relieved, and the stability of the server is improved.
Exemplary Medium
Having described the method of an exemplary embodiment of the present disclosure, next, a medium of an exemplary embodiment of the present disclosure will be described with reference to fig. 6.
In the present exemplary embodiment, the above-described method may be implemented by a program product, such as a portable compact disc read only memory (CD-ROM) and including program code, and may be run on a device, such as a personal computer. However, the program product of the present disclosure is not limited thereto, and in this document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium can be, for example, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium would include the following: an electrical connection having one or more wires, a portable disk, a hard disk, random Access Memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
The computer readable signal medium may include a data signal propagated in baseband or as part of a carrier wave with readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RE, etc., or any suitable combination of the foregoing.
Program code for carrying out operations of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C++ or the like and conventional procedural programming languages, such as the C programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of remote computing devices, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., connected via the Internet using an Internet service provider).
Exemplary apparatus
Having described the media of the exemplary embodiments of the present disclosure, next, an apparatus of the exemplary embodiments of the present disclosure will be described with reference to fig. 7.
The implementation process of the functions and roles of each module in the following device is specifically shown in the implementation process of the corresponding steps in the above method, and will not be described herein. For the device embodiments, reference is made to the description of the method embodiments for the relevant points, since they essentially correspond to the method embodiments.
Fig. 7 schematically illustrates a request processing apparatus according to an embodiment of the present disclosure, the apparatus comprising:
a receiving module 701, configured to receive a call request sent by a client;
a first determining module 702, configured to determine a corresponding current limiting configuration according to the call request;
A second determining module 703, configured to determine, based on the current limiting configuration, whether the call request triggers a current limiting operation;
and an execution module 704, configured to execute a multi-level degradation logic process in a case that it is determined that the call request triggers a current limiting operation.
Optionally, the call request includes a service identifier corresponding to the service logic to be called;
The first determining module 702 is specifically configured to:
And acquiring the flow limiting configuration corresponding to the service logic from a database for storing the preset flow limiting configuration based on the service identifier in the call request.
Optionally, the first determining module 702 is specifically configured to:
constructing a current limiting keyword based on the service identifier in the call request, and searching a current limiting configuration corresponding to the current limiting keyword in a database for storing preset current limiting configuration;
and determining the found current limiting configuration as the current limiting configuration corresponding to the service logic.
Optionally, the first determining module 702 is specifically configured to:
If the current limiting configuration corresponding to the current limiting keyword is found in the database, determining the found current limiting configuration as the current limiting configuration corresponding to the business logic;
If the current limiting configuration corresponding to the current limiting keyword is not found in the database, a default current limiting configuration is created for the current limiting keyword in the database based on preset current limiting configuration parameters, and the default current limiting configuration is determined to be the current limiting configuration corresponding to the business logic.
Optionally, the current limiting configuration includes one or more of the following: query rate QPS per second current limiting configuration; thread number current limiting configuration;
the QPS current limiting configuration includes: the number of call requests acquired in each second reaches a preset first threshold;
the thread count current limiting configuration comprises: the number of threads for responding to the call request reaches a preset second threshold.
Optionally, the execution module 704 is specifically configured to:
determining whether preset call request degradation logic is configured;
If the call request demotion logic is configured, executing the call request demotion logic, demoting the call request, and determining whether the demoted call request triggers a current limiting operation or not based on the current limiting configuration;
if the demoted call request does not trigger the current limiting operation, calling service logic corresponding to the demoted call request, and determining a call result as a processing result of multistage demotion logic processing;
If the call request demotion logic is not configured, or the demoted call request triggers a current limiting operation, determining whether a preset static call result is configured;
And if the static call result is configured, determining the static call result as a processing result of multistage degradation logic processing.
Optionally, the execution module 704 is further configured to:
and if the static call result is not configured, determining a null value as a processing result of the multistage degradation logic processing.
Optionally, the execution module 704 is specifically configured to:
And simplifying the call parameters in the call request.
Optionally, the apparatus further comprises:
The monitoring module 705 is configured to monitor the current limiting probability of the received call request, and generate a corresponding monitoring log;
And the adjusting module 706 is configured to adjust a current limiting configuration parameter in the current limiting configuration based on the current limiting probability recorded in the monitoring log.
Optionally, the apparatus further comprises:
and the return module 707 is configured to return a processing result of the multi-stage degradation logic processing to the client.
Exemplary computing device
Having described the methods, media, and apparatus of exemplary embodiments of the present disclosure, a computing device of exemplary embodiments of the present disclosure is next described with reference to fig. 8.
The computing device 800 shown in fig. 8 is merely an example and should not be taken as limiting the functionality and scope of use of embodiments of the present disclosure.
As shown in fig. 8, computing device 800 is in the form of a general purpose computing device. Components of computing device 800 may include, but are not limited to: the at least one processing unit 801, the at least one memory unit 802, and a bus 803 connecting different system components (including the processing unit 801 and the memory unit 802).
Bus 803 includes a data bus, a control bus, and an address bus.
The storage unit 802 may include readable media in the form of volatile memory, such as Random Access Memory (RAM) 8021 and/or cache memory 8022, and may further include readable media in the form of nonvolatile memory, such as Read Only Memory (ROM) 8023.
The storage unit 802 may also include a program/utility 8025 having a set (at least one) of program modules 8024, such program modules 8024 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment.
Computing device 800 may also communicate with one or more external devices 804 (e.g., keyboard, pointing device, etc.).
Such communication may occur through an input/output (I/O) interface 805. Moreover, computing device 800 may also communicate with one or more networks such as a Local Area Network (LAN), a Wide Area Network (WAN) and/or a public network, such as the Internet, through network adapter 806. As shown in fig. 8, network adapter 806 communicates with other modules of computing device 800 over bus 803. It should be appreciated that although not shown, other hardware and/or software modules may be used in connection with computing device 800, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.
It should be noted that although several units/modules or sub-units/modules of the request processing apparatus are mentioned in the above detailed description, such a division is merely exemplary and not mandatory. Indeed, the features and functionality of two or more units/modules described above may be embodied in one unit/module in accordance with embodiments of the present disclosure. Conversely, the features and functions of one unit/module described above may be further divided into ones that are embodied by a plurality of units/modules.
Furthermore, although the operations of the methods of the present disclosure are depicted in the drawings in a particular order, this is not required or suggested that these operations must be performed in this particular order or that all of the illustrated operations must be performed in order to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step to perform, and/or one step decomposed into multiple steps to perform.
While the spirit and principles of the present disclosure have been described with reference to several particular embodiments, it is to be understood that this disclosure is not limited to the particular embodiments disclosed nor does it imply that features in these aspects are not to be combined to benefit from this division, which is done for convenience of description only. The disclosure is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.
Claims (20)
1. A method of request processing, the method comprising:
Receiving a call request sent by a client;
determining corresponding current limiting configuration according to the call request;
Determining whether the call request triggers a current limiting operation based on the current limiting configuration;
determining whether preset call request degradation logic is configured;
If the call request demotion logic is configured, executing the call request demotion logic, demoting the call request, and determining whether the demoted call request triggers a current limiting operation or not based on the current limiting configuration;
if the demoted call request does not trigger the current limiting operation, calling service logic corresponding to the demoted call request, and determining a call result as a processing result of multistage demotion logic processing;
If the call request demotion logic is not configured, or the demoted call request triggers a current limiting operation, determining whether a preset static call result is configured;
And if the static call result is configured, determining the static call result as a processing result of multistage degradation logic processing.
2. The method of claim 1, the call request comprising a service identification corresponding to service logic to be invoked;
the determining the corresponding current limiting configuration according to the call request comprises the following steps:
And acquiring the flow limiting configuration corresponding to the service logic from a database for storing the preset flow limiting configuration based on the service identifier in the call request.
3. The method according to claim 2, wherein the obtaining, based on the service identifier in the call request, the corresponding current limit configuration from the database for storing the preset current limit configuration includes:
constructing a current limiting keyword based on the service identifier in the call request, and searching a current limiting configuration corresponding to the current limiting keyword in a database for storing preset current limiting configuration;
and determining the found current limiting configuration as the current limiting configuration corresponding to the service logic.
4. A method according to claim 3, said determining the found current limit configuration as the current limit configuration corresponding to the service logic, comprising:
If the current limiting configuration corresponding to the current limiting keyword is found in the database, determining the found current limiting configuration as the current limiting configuration corresponding to the business logic;
If the current limiting configuration corresponding to the current limiting keyword is not found in the database, a default current limiting configuration is created for the current limiting keyword in the database based on preset current limiting configuration parameters, and the default current limiting configuration is determined to be the current limiting configuration corresponding to the business logic.
5. The method of claim 1, the current limiting configuration comprising one or more of the following: query rate QPS per second current limiting configuration; thread number current limiting configuration;
the QPS current limiting configuration includes: the number of call requests acquired in each second reaches a preset first threshold;
the thread count current limiting configuration comprises: the number of threads for responding to the call request reaches a preset second threshold.
6. The method of claim 1, the method further comprising:
and if the static call result is not configured, determining a null value as a processing result of the multistage degradation logic processing.
7. The method of claim 1, the downgrading the call request comprising:
And simplifying the call parameters in the call request.
8. The method of claim 1, the method further comprising:
monitoring the current limiting probability of the received call request, and generating a corresponding monitoring log;
And adjusting the current limiting configuration parameters in the current limiting configuration based on the current limiting probability recorded in the monitoring log.
9. The method of claim 1, the method further comprising:
and returning the processing result of the multistage degradation logic processing to the client.
10. A request processing apparatus, the apparatus comprising:
The receiving module is used for receiving a call request sent by the client;
the first determining module is used for determining the corresponding current limiting configuration according to the calling request;
The second determining module is used for determining whether the call request triggers a current limiting operation or not based on the current limiting configuration;
The execution module is used for determining whether preset call request degradation logic is configured; if the call request demotion logic is configured, executing the call request demotion logic, demoting the call request, and determining whether the demoted call request triggers a current limiting operation or not based on the current limiting configuration; if the demoted call request does not trigger the current limiting operation, calling service logic corresponding to the demoted call request, and determining a call result as a processing result of multistage demotion logic processing; if the call request demotion logic is not configured, or the demoted call request triggers a current limiting operation, determining whether a preset static call result is configured; and if the static call result is configured, determining the static call result as a processing result of multistage degradation logic processing.
11. The apparatus of claim 10, the invocation request comprising a service identification corresponding to service logic to be invoked;
The first determining module is specifically configured to:
And acquiring the flow limiting configuration corresponding to the service logic from a database for storing the preset flow limiting configuration based on the service identifier in the call request.
12. The apparatus of claim 11, the first determining module is specifically configured to:
constructing a current limiting keyword based on the service identifier in the call request, and searching a current limiting configuration corresponding to the current limiting keyword in a database for storing preset current limiting configuration;
and determining the found current limiting configuration as the current limiting configuration corresponding to the service logic.
13. The apparatus of claim 12, the first determining module is specifically configured to:
If the current limiting configuration corresponding to the current limiting keyword is found in the database, determining the found current limiting configuration as the current limiting configuration corresponding to the business logic;
If the current limiting configuration corresponding to the current limiting keyword is not found in the database, a default current limiting configuration is created for the current limiting keyword in the database based on preset current limiting configuration parameters, and the default current limiting configuration is determined to be the current limiting configuration corresponding to the business logic.
14. The apparatus of claim 10, the current limiting configuration comprising one or more of the following: query rate QPS per second current limiting configuration; thread number current limiting configuration;
the QPS current limiting configuration includes: the number of call requests acquired in each second reaches a preset first threshold;
the thread count current limiting configuration comprises: the number of threads for responding to the call request reaches a preset second threshold.
15. The apparatus of claim 10, the execution module further to:
and if the static call result is not configured, determining a null value as a processing result of the multistage degradation logic processing.
16. The apparatus of claim 10, the execution module being specifically configured to:
And simplifying the call parameters in the call request.
17. The apparatus of claim 10, the apparatus further comprising:
The monitoring module is used for monitoring the current limiting probability of the received call request and generating a corresponding monitoring log;
And the adjusting module is used for adjusting the current limiting configuration parameters in the current limiting configuration based on the current limiting probability recorded in the monitoring log.
18. The apparatus of claim 10, the apparatus further comprising:
and the return module is used for returning the processing result of the multistage degradation logic processing to the client.
19. A medium having stored thereon a computer program which, when executed by a processor, implements the method of any of claims 1-9.
20. A computing device, comprising:
A processor;
a memory for storing a processor executable program;
Wherein the processor is configured to implement the method of any of claims 1-9 by running the executable program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111272611.8A CN113986391B (en) | 2021-10-29 | 2021-10-29 | Request processing method, device, medium and computing equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111272611.8A CN113986391B (en) | 2021-10-29 | 2021-10-29 | Request processing method, device, medium and computing equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113986391A CN113986391A (en) | 2022-01-28 |
| CN113986391B true CN113986391B (en) | 2024-06-25 |
Family
ID=79744442
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111272611.8A Active CN113986391B (en) | 2021-10-29 | 2021-10-29 | Request processing method, device, medium and computing equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113986391B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115396379A (en) * | 2022-08-24 | 2022-11-25 | 北京沃东天骏信息技术有限公司 | Flow control method, device, equipment and medium for service server |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106375472A (en) * | 2016-09-29 | 2017-02-01 | 北京三快在线科技有限公司 | Access request processing method and apparatus, and server |
| CN110505155A (en) * | 2019-08-13 | 2019-11-26 | 北京达佳互联信息技术有限公司 | Request degradation processing method, device, electronic equipment and storage medium |
| CN113284586A (en) * | 2021-05-24 | 2021-08-20 | 康键信息技术（深圳）有限公司 | Medical service processing method, device, equipment and storage medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107222426B (en) * | 2016-03-21 | 2021-07-20 | 阿里巴巴集团控股有限公司 | Flow control method, device and system |
-
2021
- 2021-10-29 CN CN202111272611.8A patent/CN113986391B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106375472A (en) * | 2016-09-29 | 2017-02-01 | 北京三快在线科技有限公司 | Access request processing method and apparatus, and server |
| CN110505155A (en) * | 2019-08-13 | 2019-11-26 | 北京达佳互联信息技术有限公司 | Request degradation processing method, device, electronic equipment and storage medium |
| CN113284586A (en) * | 2021-05-24 | 2021-08-20 | 康键信息技术（深圳）有限公司 | Medical service processing method, device, equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113986391A (en) | 2022-01-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11822640B1 (en) | User credentials verification for search | |
| US20140047070A1 (en) | Cloud comuting device and method for storing data files in cloud servers | |
| US11310066B2 (en) | Method and apparatus for pushing information | |
| JP2017538200A (en) | Service addressing in a distributed environment | |
| JP2020042784A (en) | Method and apparatus for operating intelligent terminal | |
| CN112612988A (en) | Page processing method and device, computer equipment and storage medium | |
| JP7439186B2 (en) | Coordinating overlapping audio queries | |
| CN112732663A (en) | Log information processing method and device | |
| CN113238815B (en) | Interface access control method, device, equipment and storage medium | |
| US10855750B2 (en) | Centralized management of webservice resources in an enterprise | |
| CN113986391B (en) | Request processing method, device, medium and computing equipment | |
| CN111221869A (en) | Method and device for tracking database transaction time and analyzing database lock | |
| CN112130944A (en) | Page abnormity detection method, device, equipment and storage medium | |
| CN110781159A (en) | Ceph directory file information reading method and device, server and storage medium | |
| US20160127497A1 (en) | Smart site preloading | |
| US8280950B2 (en) | Automatic client-server code generator | |
| US12001458B2 (en) | Multi-cloud object store access | |
| JP6772389B2 (en) | Reducing redirects | |
| CN110647331A (en) | Development tool acquisition method and device, storage medium and electronic equipment | |
| US11301538B1 (en) | Data management in multi-application web pages | |
| US20060161551A1 (en) | Generation and retrieval of incident reports | |
| US9177255B1 (en) | Cloud systems and methods for determining the probability that a second application is installed based on installation characteristics | |
| CN114218013A (en) | Searching method, searching device and electronic equipment storage medium | |
| CN108509223B (en) | Data processing method, device and system and storage medium | |
| CN113111138A (en) | Data processing method, device, computing equipment and medium |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |