Access request processing method, device, storage medium and server

Abstract

The present invention relates to the field of data processing, and specifically to an access request processing method, device, storage medium and server, the method comprising: receiving access requests sent by a client through a traffic cache server, counting whether the access requests reach an estimated value; if the access requests do not reach the estimated value, transferring the access requests to a business server according to a preset frequency, and responding to the access requests through the business server; if the access requests reach the estimated value, obtaining access requests with an importance level higher than a preset level in the access requests, transferring the access requests with an importance level higher than the preset level to an emergency server, and responding to the access requests through the emergency server. The present invention can dynamically configure the processing logic of access requests, improve the system's processing capability for access requests at high concurrency, and prevent system paralysis.

Description

Technical Field

[0001] The present invention relates to the field of data processing, and in particular to an access request processing method, device, storage medium and server. Background Art

[0002] With the development of Internet technology, the number of clients is increasing. During the operation of the client, it is necessary to hold activities or promotions from time to time to increase the activity of the client. At these times, the number of client visits will increase dramatically. At the same time, the number of access requests sent by the client to the server will also increase dramatically. When the access requests exceed the threshold that the server system can withstand for a long time, the server system may be overwhelmed, eventually causing the entire service to be unavailable and the client to be unable to respond normally. Therefore, how to deal with high-concurrency access requests is a problem that needs to be considered when designing the server system. Summary of the invention

[0003] In order to overcome the above technical problems, especially the problem that the existing technology cannot efficiently process access requests with high concurrency, the following technical solutions are proposed:

[0004] In a first aspect, the present invention provides an access request processing method, comprising:

[0005] Receive access requests sent by the client through the traffic cache server, and count whether the access requests reach the estimated value;

[0006] If the access request does not reach the estimated value, forwarding the access request to the service server according to a preset frequency, and responding to the access request through the service server;

[0007] If the access requests reach the estimated value, obtain the access requests whose importance level is higher than the preset level, transfer the access requests whose importance level is higher than the preset level to the emergency server, and respond to the access requests through the emergency server.

[0008] Further, obtaining the access requests whose importance level is higher than the preset level among the access requests, and transferring the access requests whose importance level is higher than the preset level to the emergency server, includes:

[0009] Obtain access requests with an importance level higher than a preset level, store the access requests in a quantitative cache server, obtain the access requests from the quantitative server at a preset frequency, and forward the access requests to an emergency server.

[0010] Furthermore, after receiving the access request sent by the client through the traffic cache server, the method further includes:

[0011] Count the access requests of clients with the same IP address to a service. Within a preset time, a preset proportion of the access requests are considered valid requests, and the rest are considered invalid requests.

[0012] Furthermore, after treating a preset proportion of access requests as valid requests and treating the remaining access requests as invalid requests, the method further includes:

[0013] Obtaining identity information or registration information of the client user corresponding to the invalid request;

[0014] Matching corresponding configuration parameters according to the identity information or registration information;

[0015] Returning preset configuration parameters to the client corresponding to the invalid request.

[0016] Furthermore, if the access request reaches the estimated value, before obtaining the access request with an importance level higher than a preset level among the access requests, the method further includes:

[0017] The number of the access requests is obtained, and the level of the preset level is adjusted according to the number of the access requests.

[0018] Furthermore, after receiving the access request sent by the client through the traffic cache server and counting whether the access request reaches the estimated value, the method further includes:

[0019] The access request processing efficiency of the traffic cache server is counted, and the capacity strategy of the traffic cache server is matched according to the access request processing efficiency.

[0020] In a second aspect, the present invention provides an access request processing device, comprising:

[0021] Request receiving module: used to receive access requests sent by the client and count whether the access requests reach the estimated value;

[0022] A first processing module: configured to forward the access request to a service server according to a preset frequency if the access request does not reach the estimated value, and respond to the access request through the service server;

[0023] The second processing module is used for obtaining access requests whose importance level is higher than the preset level in the access requests if the access requests reach the estimated value, transferring the access requests whose importance level is higher than the preset level to the emergency server, and responding to the access requests through the emergency server.

[0024] Furthermore, the second processing module executes obtaining access requests with an importance level higher than a preset level among the access requests, and transferring the access requests with an importance level higher than the preset level to the emergency server, including:

[0025] Obtain access requests with an importance level higher than a preset level, store the access requests in a quantitative cache server, obtain the access requests from the quantitative server at a preset frequency, and forward the access requests to an emergency server.

[0026] In a third aspect, the present invention further provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the access request processing method described above is implemented.

[0027] In a fourth aspect, the present invention also provides a server, comprising one or more processors, a memory, and one or more computer programs, wherein the one or more computer programs are stored in the memory and configured to be executed by the one or more processors, and the one or more programs are configured to execute the above-mentioned access request processing method.

[0028] Compared with the prior art, the present invention has the following beneficial effects:

[0029] The present invention provides a method for dynamically processing access requests for situations with different numbers of access requests. The method receives access requests sent by a client through a unified traffic cache server, counts whether the access requests reach an estimated value, and conveniently manages the received access requests in a unified manner. If the access requests do not reach the estimated value, the traffic cache server is controlled to transfer the access requests to a business server at a preset frequency, and the business server responds to the access requests, and then feeds back the response results to the business requester. If the access requests reach the estimated value, the traffic cache server is controlled to obtain access requests with an importance level higher than a preset level, and then the access requests with an importance level higher than the preset level are transferred to an emergency server, and the emergency server responds to the access requests, thereby achieving the purpose of giving priority to important access requests, and effectively restricting ordinary access requests to prevent excessive access requests from causing system paralysis, thereby achieving the purpose of protecting the database and the system.

[0030] Additional aspects and advantages of the present invention will be given in part in the following description, which will become obvious from the following description, or may be learned through practice of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] The above and / or additional aspects and advantages of the present invention will become apparent and easily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

[0032] Figure 1 A schematic diagram of a flow chart of an embodiment of a method for processing an access request according to the present invention;

[0033] Figure 2 A schematic flow chart of another embodiment of the access request processing method of the present invention;

[0034] Figure 3 A schematic diagram of an embodiment of an access request processing device of the present invention;

[0035] Figure 4 The figure is a schematic diagram of the structure of a server according to an embodiment of the present invention. DETAILED DESCRIPTION

[0036] Embodiments of the present invention are described in detail below, examples of which are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present invention, and cannot be interpreted as limiting the present invention.

[0037] Those skilled in the art will appreciate that, unless otherwise stated, the singular forms "a", "an", "said" and "the" used herein may also include plural forms. It should be further understood that the term "comprising" used in the specification of the present invention refers to the presence of the features, integers, steps, operations, but does not exclude the presence or addition of one or more other features, integers, steps, operations.

[0038] Those skilled in the art will understand that, unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as those generally understood by those skilled in the art in the field to which the present invention belongs. It should also be understood that terms such as those defined in common dictionaries should be understood to have meanings consistent with the meanings in the context of the prior art, and will not be interpreted with idealized or overly formal meanings unless specifically defined as here.

[0039] Those skilled in the art should understand that the concepts of "application", "application program", "computer program" and similar expressions referred to in the present invention are the same concepts known to those skilled in the art, and refer to computer software suitable for electronic operation that is organically constructed by a series of computer instructions and related data resources. Unless otherwise specified, such naming itself is not limited by the type and level of programming language, nor by the operating system or platform on which it runs. Of course, such concepts are not limited by any form of terminal.

[0040] The embodiment of the present invention provides a method for processing an access request. Figure 1 As shown, the method comprises the following steps:

[0041] S10: receiving access requests sent by the client through the traffic cache server, and counting whether the access requests reach the estimated value.

[0042] This technical solution is applied to large-scale high-concurrency systems. Large-scale high-concurrency systems can effectively deal with a large number of access requests in a specific time period. In this embodiment, the large-scale high-concurrency system includes a traffic cache server, a quantitative cache server, a business server, and an emergency server. The access request sent by the client is received by the traffic cache server, that is, the access request of this embodiment is uniformly received by the traffic cache server in the large-scale high-concurrency system, and the received access request is stored in the traffic cache server. The traffic cache server manages the access request in an overall manner. Specifically, the access request is counted to see whether it reaches the estimated value, and then the received access request is processed differently according to whether the access request reaches the estimated value. Optionally, the access request statistics can be the total number of all access requests within a preset period, or the file size of all access requests within a preset period.

[0043] S20: If the access request does not reach the estimated value, forward the access request to the service server according to a preset frequency, and respond to the access request through the service server.

[0044] In the normal stage of business, the access requests of the client will not be too concentrated in a certain time period. When the received access requests are counted, if the access requests do not reach the estimated value, that is, the access requests received by the large-scale high-concurrency system in a certain time period are less than the estimated value, then the traffic cache server of the large-scale high-concurrency system is controlled to transfer the access requests to the business server at a preset frequency. In this embodiment, the traffic cache server is designed based on the principle of water bucket flow, and the water in the bucket flows out according to a predetermined flow rate, which is equivalent to transferring the access requests to the business server at a preset frequency in this step, and the business server responds to the access request and then feeds back the response result to the business requester.

[0045] S30: If the access requests reach the estimated value, obtain the access requests whose importance level is higher than the preset level, transfer the access requests whose importance level is higher than the preset level to the emergency server, and respond to the access requests through the emergency server.

[0046] In special phases of the business, such as reporting related business promotion activities, lucky draw activities and other special phases, the access requests of the client will be too concentrated in a certain time period. In this embodiment, if the access request reaches the estimated value, for example, the traffic cache server has received 100,000 client access requests during the period of 10:00-10:04, and the estimated value is that only 100,000 client access requests can be processed during 10:00-10:10, and the actual number of access requests exceeds the estimated value, if the traffic cache server receives the access request of the client again, some access requests cannot be responded to normally, that is, the access request overflows, which is similar to the overflow of water in a bucket, and all access requests cannot be received and processed normally. At this time, among the access requests of the continuously received clients, the access requests with an importance level higher than the preset level are obtained, and then the access requests with an importance level higher than the preset level are transferred to the emergency server, and the access requests are responded to by the emergency server, so as to achieve the purpose of giving priority to important access requests, and effectively restrict ordinary access requests, so as to prevent excessive access requests from causing system paralysis, access speed reduction, and concurrent access volume reduction, so as to achieve the purpose of protecting the database and the system.

[0047] The present embodiment provides a method for dynamically processing access requests for different numbers of access requests, wherein access requests sent by clients are received through a unified traffic cache server, and statistics are counted whether the access requests reach an estimated value, so as to facilitate unified management of the received access requests. If the access requests do not reach the estimated value, the traffic cache server is controlled to transfer the access requests to the business server at a preset frequency, and the business server responds to the access requests, and then feeds back the response results to the business requester. If the access requests reach the estimated value, the traffic cache server is controlled to obtain access requests with an importance level higher than a preset level, and then the access requests with an importance level higher than the preset level are transferred to an emergency server, and the emergency server responds to the access requests, thereby achieving the purpose of giving priority to important access requests, and effectively restricting ordinary access requests to prevent excessive access requests from causing system paralysis, thereby achieving the purpose of protecting the database and the system.

[0048] An embodiment of the present invention, as Figure 2 As shown, if the access request reaches the estimated value, obtaining the access request whose importance level is higher than the preset level among the access requests, and transferring the access request whose importance level is higher than the preset level to the emergency server includes:

[0049] S22: If the access request reaches the estimated value, obtain access requests with an importance level higher than a preset level, store the access requests in a quantitative cache server, obtain the access requests from the quantitative server at a preset frequency, forward the access requests to the emergency server, and respond to the access requests through the emergency server.

[0050] In order to ensure that important access requests are responded to, and because the number of such important access requests is relatively small, in this embodiment, the large concurrent system is designed to further include a quantitative cache server, which is used to store specific access requests. In one embodiment, the quantitative cache server is derived from the flow cache server and is a part of the flow cache server. The quantitative cache server cannot occupy too many resources. Therefore, when the access request reaches the estimated value, the flow cache server first obtains access requests with an importance level higher than the preset level, and then stores these access requests in the quantitative cache server, and then obtains the access requests from the quantitative server at a preset frequency. The quantitative cache server is equivalent to a bucket for storing fixed-capacity tokens, and tokens are added to the bucket at a fixed rate. Only when there are tokens in the bucket, the request is processed, otherwise, the request is not processed, that is, the access request forwarded to the quantitative cache server. The quantitative cache server forwards the access request to the business server, thereby ensuring that the quantitative cache server does not occupy too many resources and can process important access requests in a timely manner, while the flow cache server receives the access request of the client as usual without affecting the operation of the flow cache server.

[0051] In one embodiment of the present invention, after the traffic cache server receives the access request sent by the client, the method further includes:

[0052] Count the access requests of clients with the same IP address to a service. Within a preset time, a preset proportion of the access requests are considered valid requests, and the rest are considered invalid requests.

[0053] In actual applications, when a user does not get a response after operating a client, he will operate the client multiple times in a short period of time, resulting in sending access requests to the system for the same service in a short period of time, or connecting multiple devices in the same local area network, opening multiple clients to initiate access requests to the same service, at this time, the external access IPs of these devices are the same. In this embodiment, after receiving the access request sent by the client, the traffic cache server counts multiple access requests for the same service by the same IP within a preset time, and then regards several access requests in the multiple access requests as valid requests, and the remaining access requests as invalid requests. For example, the traffic cache server regards the access request received from the client for the same service as a valid request every 5S, and the remaining access requests as invalid requests. Invalid requests are no longer added to the traffic cache server, nor are they transferred to the quantitative cache server, but the invalid requests are directly discarded or directly fed back. Further, in one implementation of this embodiment, the preset ratio is adjusted according to the number of access requests. For example, when the number of access requests is 500 times / second, the preset ratio is one-fifth; when the number of access requests is 800 times / second, the preset ratio is one-eighth.

[0054] In an embodiment of the present invention, after treating a preset proportion of access requests as valid requests and treating the remaining access requests as invalid requests, the method further includes:

[0055] Obtaining identity information or registration information of the client user corresponding to the invalid request;

[0056] Matching corresponding configuration parameters according to the identity information or registration information;

[0057] Returning preset configuration parameters to the client corresponding to the invalid request.

[0058] In the above embodiment, after determining that some access requests are valid requests and some access requests are invalid requests, preset configuration parameters are returned to the client corresponding to the invalid request for the invalid request. Furthermore, different configuration parameters can be returned to the client according to different identity information or registration information of the client user. The client outputs corresponding prompt information on the user interface according to the received configuration parameters. For example, according to the identity information of client user A, configuration parameter C1 is returned, and the style of prompt information output by the client on the user interface is S1. According to the identity information of client user B, configuration parameter C2 is returned, and the style of prompt information output by the client on the user interface is S2. Different configuration parameters are returned to different clients, so that different clients output different prompt information. Different reminder information is set for client users with different identities, thereby improving the differences between clients. At the same time, returning different configuration parameters can enable different clients to output different prompt information without defining different prompt information for each client, thereby improving the processing efficiency of invalid requests.

[0059] In an embodiment of the present invention, after receiving the access request sent by the client through the traffic cache server and counting whether the access request reaches the estimated value, the method further includes:

[0060] The access request processing efficiency of the traffic cache server is counted, and the capacity strategy of the traffic cache server is matched according to the access request processing efficiency.

[0061] In actual applications, as the business develops, the traffic cache server needs to process more and more access requests. The efficiency of the traffic cache server needs to be strictly controlled to ensure the normal operation of the business from the source of the business. In this embodiment, the access request processing efficiency of the traffic cache server is counted, and then the capacity strategy of the traffic cache server is matched according to the processing efficiency of the access request. When the processing efficiency decreases, the standby traffic cache server can be temporarily configured as a traffic cache server for current use, so as to increase the capacity of the traffic cache server, ensure that the traffic cache server can receive more and more comprehensive access requests, and ensure that the access requests can be forwarded to the business server for effective processing. According to the "adjusted level of the preset level" and the access request processing efficiency matching traffic cache server capacity strategy, the capacity strategy is used to determine the preset ratio.

[0062] In another embodiment, when the access requests with an importance level higher than a preset level increase to a preset value, part of the capacity of the traffic cache server is configured as the capacity of the quantitative cache server, thereby improving the efficiency of the quantitative cache server in receiving and forwarding access requests with an importance level higher than the preset level.

[0063] In an embodiment of the present invention, if the access request reaches the estimated value, before obtaining the access request whose importance level is higher than the preset level among the access requests, the method further includes:

[0064] The number of the access requests is obtained, and the level of the preset level is adjusted according to the number of the access requests.

[0065] Since the number of visits may continue to increase, the emergency server cannot handle too many important access requests. In this embodiment, when the access requests reach the estimated value, the number of access requests is obtained, and then the preset level of the access requests sent to the emergency server is adjusted according to the number of access requests. For example, if the number of access requests is 500 times / second, the preset level of the access requests sent to the emergency server is level 8 and above; and when the number of access requests is 800 times / second, the preset level of the access requests sent to the emergency server is adjusted to level 9 and above. Otherwise, if the number of important access requests is too large, the emergency server cannot handle too many important access requests, thereby ensuring that the more important access requests can be responded to and processed in a timely manner.

[0066] like Figure 3 As shown, in another embodiment, the present invention provides an access request processing device, comprising:

[0067] Request receiving module 10: used to receive access requests sent by the client, and count whether the access requests reach the estimated value;

[0068] The first processing module 20 is used for forwarding the access request to the service server according to a preset frequency if the access request does not reach the estimated value, and responding to the access request through the service server;

[0069] The second processing module 21 is used for obtaining access requests whose importance level is higher than the preset level in the access requests if the access requests reach the estimated value, transferring the access requests whose importance level is higher than the preset level to the emergency server, and responding to the access requests through the emergency server.

[0070] In an embodiment of the present invention, the second processing module 21 executes obtaining access requests with an importance level higher than a preset level in the access requests, and transferring the access requests with an importance level higher than the preset level to the emergency server, including:

[0071] Obtain access requests with an importance level higher than a preset level, store the access requests in a quantitative cache server, obtain the access requests from the quantitative server at a preset frequency, and forward the access requests to an emergency server.

[0072] In one embodiment of the present invention, after the request receiving module 10 receives the access request sent by the client, it also includes executing:

[0073] Count the access requests of clients with the same IP address to a service. Within a preset time, a preset proportion of the access requests are considered valid requests, and the rest are considered invalid requests.

[0074] In one embodiment of the present invention, after the request receiving module 10 executes the process of treating a preset proportion of access requests as valid requests and treating the remaining access requests as invalid requests, it further includes executing:

[0075] Obtaining identity information or registration information of the client user corresponding to the invalid request;

[0076] Matching corresponding configuration parameters according to the identity information or registration information;

[0077] Returning preset configuration parameters to the client corresponding to the invalid request.

[0078] In one embodiment of the present invention, the request receiving module 10 further comprises executing:

[0079] The number of the access requests is obtained, and the level of the preset level is adjusted according to the number of the access requests.

[0080] In one embodiment of the present invention, the request receiving module 10 further comprises executing:

[0081] The access request processing efficiency of the traffic cache server is counted, and the capacity strategy of the traffic cache server is matched according to the access request processing efficiency.

[0082] In another embodiment, the present invention provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the access request processing method described in the above embodiment is implemented. The computer-readable storage medium includes, but is not limited to, any type of disk (including floppy disk, hard disk, optical disk, CD-ROM, and magneto-optical disk), ROM (Read-Only Memory), RAM (Random Access Memory), EPROM (EraSable Programmable Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), flash memory, magnetic card or optical card. That is, the storage device includes any medium that stores or transmits information in a readable form by a device (for example, a computer, a mobile phone), which can be a read-only memory, a disk or an optical disk, etc.

[0083] A computer-readable storage medium provided by an embodiment of the present invention can be used to receive access requests sent by clients through a traffic cache server, and count whether the access requests reach an estimated value; if the access requests do not reach the estimated value, transfer the access requests to a business server according to a preset frequency, and respond to the access requests through the business server; if the access requests reach the estimated value, obtain access requests with an importance level higher than a preset level in the access requests, transfer the access requests with an importance level higher than the preset level to an emergency server, and respond to the access requests through the emergency server. The invention provides a method for dynamically processing access requests according to different numbers of access requests. The access requests sent by the client are received through a unified traffic cache server, and statistics are counted whether the access requests reach the estimated value, so as to facilitate unified management of the received access requests. If the access requests do not reach the estimated value, the traffic cache server is controlled to transfer the access requests to the business server at a preset frequency, and the business server responds to the access requests, and then the response results are fed back to the business requester. If the access requests reach the estimated value, the traffic cache server is controlled to obtain access requests with an importance level higher than the preset level, and then the access requests with an importance level higher than the preset level are transferred to the emergency server, and the access requests are responded to by the emergency server, so as to achieve the purpose of giving priority to important access requests, and effectively limit ordinary access requests to prevent excessive access requests from causing system paralysis, so as to achieve the purpose of protecting the database and the system.

[0084] The computer-readable storage medium provided in the embodiment of the present invention can implement the embodiment of the access request processing method described above. For specific functional implementation, please refer to the description in the method embodiment, which will not be repeated here.

[0085] In addition, in another embodiment, the present invention further provides a server, which includes a flow cache server, a quantitative cache server and an emergency server. Figure 4 As shown, the server includes a processor 403, a memory 405, an input unit 407, a display unit 409 and other devices. Those skilled in the art can understand that Figure 4 The structural devices shown do not constitute a limitation on all servers, and may include more or fewer components than shown, or combine certain components. The memory 405 can be used to store the computer program 401 and various functional modules, and the processor 403 runs the computer program 401 stored in the memory 405, thereby executing various functional applications and data processing of the device. The memory 405 can be an internal memory or an external memory, or include both internal and external memories. The internal memory may include a read-only memory (ROM), a programmable ROM (PROM), an electrically programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a flash memory, or a random access memory. The external memory may include a hard disk, a floppy disk, a ZIP disk, a U disk, a magnetic tape, etc. The memory disclosed in the present invention includes but is not limited to these types of memories. The memory 405 disclosed in the present invention is only used as an example and not as a limitation.

[0086] The input unit 407 is used to receive input signals and user input. The input unit 407 may include a touch panel and other input devices. The touch panel can collect user touch operations on or near it (such as operations performed by the user using any suitable object or accessory such as a finger, stylus, etc. on or near the touch panel), and drive the corresponding connection device according to a pre-set program; other input devices may include but are not limited to one or more of a physical keyboard, function keys (such as playback control keys, switch keys, etc.), a trackball, a mouse, a joystick, etc. The display unit 409 can be used to display information input by the user or information provided to the user and various menus of the computer device. The display unit 409 can be in the form of a liquid crystal display, an organic light emitting diode, etc. The processor 403 is the control center of the computer device. It uses various interfaces and lines to connect various parts of the entire computer, and executes various functions and processes data by running or executing software programs and / or modules stored in the memory 405, and calling data stored in the memory.

[0087] In one embodiment, the server includes one or more processors 403, one or more memories 405, and one or more computer programs 401, wherein the one or more computer programs 401 are stored in the memory 405 and are configured to be executed by the one or more processors 403, and the one or more computer programs 401 are configured to execute the message push processing method described in the above embodiment. Figure 4 The one or more processors 403 shown in FIG. 4 are capable of executing, implementing Figure 3 The functions of the request receiving module 10, the first processing module 20 and the second processing module 21 are shown in FIG.

[0088] A server provided by an embodiment of the present invention can receive access requests sent by clients through a traffic cache server, and count whether the access requests reach an estimated value; if the access requests do not reach the estimated value, transfer the access requests to a business server according to a preset frequency, and respond to the access requests through the business server; if the access requests reach the estimated value, obtain access requests with an importance level higher than a preset level in the access requests, transfer the access requests with an importance level higher than the preset level to an emergency server, and respond to the access requests through the emergency server. The invention provides a method for dynamically processing access requests according to different numbers of access requests. The access requests sent by the client are received through a unified traffic cache server, and statistics are counted whether the access requests reach the estimated value, so as to facilitate unified management of the received access requests. If the access requests do not reach the estimated value, the traffic cache server is controlled to transfer the access requests to the business server at a preset frequency, and the business server responds to the access requests, and then the response results are fed back to the business requester. If the access requests reach the estimated value, the traffic cache server is controlled to obtain access requests with an importance level higher than the preset level, and then the access requests with an importance level higher than the preset level are transferred to the emergency server, and the access requests are responded to by the emergency server, so as to achieve the purpose of giving priority to important access requests, and effectively limit ordinary access requests to prevent excessive access requests from causing system paralysis, so as to achieve the purpose of protecting the database and the system.

[0089] The server provided in the embodiment of the present invention can implement the embodiment of the access request processing method provided above. For specific function implementation, please refer to the description in the method embodiment, which will not be repeated here.

[0090] The above descriptions are only some embodiments of the present invention. It should be pointed out that, for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. A method for processing an access request, characterized in that: include: Receive access requests sent by the client through the traffic cache server, and count whether the access requests reach the estimated value; If the access request does not reach the estimated value, forwarding the access request to the service server according to a preset frequency, and responding to the access request through the service server; If the access requests reach the estimated value, obtaining the number of the access requests, and determining a preset level of the access requests according to the number of the access requests; Obtaining access requests with an importance level higher than the preset level from the access requests, storing the access requests with an importance level higher than the preset level in a quantitative cache server, obtaining the access requests from the quantitative cache server at a preset frequency, transferring the access requests to an emergency server, and responding to the access requests through the emergency server; wherein the quantitative cache server is a part of the traffic cache server; After the traffic cache server receives the access request sent by the client, the method further includes: Counting access requests of clients with the same IP address to a service, and within a preset time, treating a preset proportion of the access requests as valid requests, and treating the remaining access requests as invalid requests; wherein, counting whether the access requests reach the estimated value includes counting whether the valid requests of each client reach the estimated value; Obtaining identity information or registration information of the client user corresponding to the invalid request; Matching corresponding configuration parameters according to the identity information or registration information; The configuration parameters are returned to the client corresponding to the invalid request, so that the client outputs corresponding prompt information on the user interface according to the received configuration parameters.

2. The method according to claim 1, characterized in that After receiving the access request sent by the client through the traffic cache server and counting whether the access request reaches the estimated value, the method further includes: The access request processing efficiency of the traffic cache server is counted, and the capacity strategy of the traffic cache server is matched according to the access request processing efficiency.

3. An access request processing device, characterized in that: include: Request receiving module: used to receive access requests sent by the client through the traffic cache server, and count whether the access requests reach the estimated value; A first processing module: configured to forward the access request to a service server according to a preset frequency if the access request does not reach the estimated value, and respond to the access request through the service server; A second processing module: configured to obtain the number of the access requests if the access requests reach the estimated value, and determine a preset level of the access requests according to the number of the access requests; Obtaining access requests with an importance level higher than the preset level from the access requests, storing the access requests with an importance level higher than the preset level in a quantitative cache server, obtaining the access requests from the quantitative cache server at a preset frequency, transferring the access requests to an emergency server, and responding to the access requests through the emergency server; wherein the quantitative cache server is a part of the traffic cache server; Wherein, the request receiving module is also used for: Counting access requests of clients with the same IP address to a service, and within a preset time, treating a preset proportion of the access requests as valid requests, and treating the remaining access requests as invalid requests; wherein, counting whether the access requests reach the estimated value includes counting whether the valid requests of each client reach the estimated value; Obtaining identity information or registration information of the client user corresponding to the invalid request; Matching corresponding configuration parameters according to the identity information or registration information; The configuration parameters are returned to the client corresponding to the invalid request, so that the client outputs corresponding prompt information on the user interface according to the received configuration parameters.

4. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, which, when executed by a processor, implements the access request processing method according to any one of claims 1 to 2.

5. A server, characterized in that: include: one or more processors; Memory; One or more computer programs, wherein the one or more computer programs are stored in the memory and configured to be executed by the one or more processors, and the one or more computer programs are configured to execute the access request processing method according to any one of claims 1 to 2.

Images