CN104572974A - Service request processing method and device - Google Patents

Abstract

The present invention provides a service request processing method and device, wherein the method includes: intercepting the service request sent by the application to the database; judging whether there is an idle connection with the database in the connection pool; if not, saving the The service request, and continue to judge whether there is an idle connection with the database in the connection pool according to the set rules until the idle connection appears in the connection pool; select the idle connection that occurs, and use The selected idle connection sends the service request to the database. Through the present invention, the application only needs to send a service request once to ensure that the service request is processed by the database, which can not only prevent the user from receiving a message that the service request fails, resulting in a decrease in user experience, but also prevent the application from repeatedly sending the service request. Therefore, both Reducing the operating burden of the terminal where the application is located and the network can improve the user experience.

Description

Service request processing method and device

technical field

The present invention relates to the technical field of data processing, in particular to a service request processing method and device.

Background technique

At present, in the relational database system and the non-distributed database system, the architecture of direct connection between the application and the database is mainly adopted. When a database system with this architecture processes a business request, the application directly sends the business request to the database, and the database returns the corresponding response result to the application.

With this existing business request processing scheme, when the number of business requests currently processed by the database reaches the upper limit that the database can support (the number of connections to the database reaches the upper limit), and when a new application sends a business request to the database, the database receives the business request After the request, since there is no idle connection available to the application, a message of service request failure will be returned to the application. After the application receives the request failure message, it will send the service request to the database again, and if the database still has no idle connection, it will return the service request failure message to the application again. The application and the database will repeat the above operations until an idle connection in the database is provided for the application to process the service request.

It can be seen that in the existing business request processing scheme, when the number of business requests currently processed by the database reaches the upper limit that the database can support, when a new application sends a business request to the database, on the one hand, since the database directly returns business requests to the application Request failure messages, therefore, affect the user experience. At the same time, using the application requires repeated service requests until the request succeeds, which will not only affect the user experience, but also increase the operational burden of the terminal where the application is located and the network. On the other hand, since the database has to repeatedly determine whether there is an idle connection and return a message of service request failure to the application, the operational burden of the database will also be increased.

Contents of the invention

In view of the above existing problems, the present invention is proposed to provide a service request processing method and device for overcoming the above problems or at least partially solving the above problems.

According to one aspect of the present invention, a service request processing method is provided, including: intercepting the service request sent by the application to the database; judging whether there is an idle connection with the database in the connection pool; if not, saving the service request Request, and continue to judge whether there is an idle connection with the database in the connection pool according to the set rules until the idle connection appears in the connection pool; select the idle connection that occurs, and use the selected The idle connection sends the service request to the database.

According to another aspect of the present invention, a service request processing device is provided, the service request processing device includes: a first interception module, used to intercept the service request sent by the application device to the database device; a judging module, used to judge the connection Whether there is an idle connection with the database device in the pool; the first execution module is used to save the service request if the judging result of the judgment module is that there is no idle connection, and continue to judge the service request according to the set rules Whether there is an idle connection with the database device in the connection pool, until the idle connection appears in the connection pool; the sending module is used to select the idle connection that appears, and use the selected An idle connection sends the service request to the database device.

Through the present invention, in a database system, especially a non-distributed database system such as a relational database system, the service request sent by the application to the database is intercepted, and an idle connection with the database is selected from the connection pool to send to the service request. When the connection pool When there is an idle connection in the pool, the business request can be directly sent to the database through the idle connection. When there is no idle connection in the connection pool, the business request of the application is still accepted normally. When an idle connection appears, the business request will be sent to the database for processing. Process without returning an error or failure message to the application. It can be seen that the application only needs to send a business request once to ensure that the business request is processed by the database, which can not only prevent the user from receiving the message that the business request fails, resulting in a decrease in user experience, but also prevent the application from repeatedly sending business requests. The operating burden of the terminal and the network can improve the user experience. In addition, in the business information processing solution disclosed in the present invention, the business request is only sent to the database for processing when there is an idle connection in the database, and the database does not need to repeatedly judge whether there is an idle connection and does not need to return a message of business request failure to the application. Therefore, the operational burden on the database can be effectively reduced.

The above description is only an overview of the technical solution of the present invention. In order to better understand the technical means of the present invention, it can be implemented according to the contents of the description, and in order to make the above and other purposes, features and advantages of the present invention more obvious and understandable , the specific embodiments of the present invention are enumerated below.

Description of drawings

Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiment. The drawings are only for the purpose of illustrating a preferred embodiment and are not to be considered as limiting the invention. Also throughout the drawings, the same reference numerals are used to designate the same parts. In the attached picture:

FIG. 1 is a schematic flow chart of steps of a service request processing method according to Embodiment 1 of the present invention;

FIG. 2 is a schematic flowchart of steps of a service request processing method according to Embodiment 2 of the present invention;

FIG. 3 is a schematic flowchart of steps of a service request processing method according to Embodiment 3 of the present invention;

FIG. 4 is a schematic structural diagram of a service request processing device according to Embodiment 4 of the present invention;

Fig. 5 is a schematic structural diagram of a service request processing device according to Embodiment 5 of the present invention.

Detailed ways

Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited by the embodiments set forth herein. Rather, these embodiments are provided for more thorough understanding of the present disclosure and to fully convey the scope of the present disclosure to those skilled in the art.

Embodiment one

Referring to FIG. 1 , it shows a schematic flowchart of steps of a service request processing method according to Embodiment 1 of the present invention.

The service request processing method in this embodiment includes the following steps:

Step S102: Intercept the service request sent by the application to the database.

Among them, the service request is any service request that the application can send to the database, for example: a request to obtain a user number, a request to obtain the remaining traffic value of a package, etc.

It should be noted that in this embodiment, the service request sent by the application to the database may be intercepted by the middleware set between the application and the database, or may be intercepted by any other appropriate device.

Step S104: Determine whether there is an idle connection to the database in the connection pool.

In the connection pool, according to the supportable connection information of the database, a corresponding connection is established for the database. When the connection to the database in the connection pool is occupied by a business request, the current state of the connection is busy; when the connection to the database in the connection pool is not occupied by a business request, the current state of the connection is idle. After intercepting the service request, select an idle connection with the database from the connection pool to send the service request to the database.

Step S106: If there is no idle connection to the database in the connection pool, save the service request, and continue to judge whether there is an idle connection to the database in the connection pool according to the set rules until an idle connection appears in the connection pool.

It should be noted that the service request may be stored in a processing queue, or in a preset cache, or in any other appropriate storage form.

In the actual implementation process, those skilled in the art can set specific rules for continuously judging whether there is an idle connection with the database in the connection pool according to actual needs. For example: poll the status of each connection between the connection pool and the database every set time interval to determine whether there is an idle connection.

Step S108: Select an idle connection that appears, and use the selected idle connection to send the service request to the database.

Select an idle connection to send the service request to the database, and the service request can be guaranteed to be processed due to the existence of an idle connection in the database.

Through the service request processing method provided in this embodiment, in a database system, especially a non-distributed database system such as a relational database system, the service request sent by the application to the database is intercepted, and an idle connection with the database is selected from the connection pool to send For business requests, when there is an idle connection in the connection pool, the business request can be directly sent to the database through the idle connection. When there is no idle connection, the business request of the application is still accepted normally, and the business request will be processed when an idle connection appears. Sent to the database for processing without returning an error or failure message to the application. It can be seen that the application only needs to send a business request once to ensure that the business request is processed by the database, which can not only prevent the user from receiving the message that the business request fails, resulting in a decrease in user experience, but also prevent the application from repeatedly sending business requests. The operating burden of the terminal and the network can improve the user experience. In addition, only when the database has an idle connection, the business request is sent to the database for processing, and the database does not need to repeatedly judge whether there is an idle connection or not to return a message of failure of the business request to the application. Therefore, the operational burden of the database can be effectively reduced.

Embodiment two

Referring to FIG. 2 , it shows a schematic flowchart of steps of a service request processing method according to Embodiment 2 of the present invention.

The service request processing method in this embodiment includes the following steps:

Step S202: the middleware intercepts the service request sent by the application to the database.

Wherein, in this embodiment, the middleware is used to intercept the service request sent by the application to the database, and the middleware is set between the application and the database. The so-called gap is not a gap in the physical sense, but because the middleware intercepts the data sent between the application and the database, so it is called the middleware set between the application and the database.

It should be noted that the application, middleware, and database can be set on the same device, or each can be set on one device, or a combination of two can be set on different devices. One middleware can be set between multiple applications and one database, that is, one middleware is set for each database, and one middleware can be set between multiple applications and multiple databases, that is, one middleware is set for multiple databases.

Among them, the service request is any service request that the application can send to the database, for example: a request to obtain a user number, a request to obtain the remaining traffic value of a package, etc.

Step S204: the middleware judges whether there is an idle connection between the middleware and the database in its own connection pool, if yes, execute step S206, if not, execute step S208.

Wherein, the connection pool between the middleware and the database is set in the connection pool of the middleware itself, the number of which is the same as the number of connections supported by the database. In addition, when there are a plurality of databases, the data stored in each database is also the same.

Step S206: If the middleware determines that there is an idle connection between the middleware and the database in its own connection pool, select an idle connection, and then execute step S210.

This embodiment does not make specific restrictions on the specific selection method for selecting an idle connection. When there are multiple idle connections, the middleware can randomly select an idle connection, or select a connection with the longest idle time according to the idle time of the connection. , of course, can also be selected according to other selection methods.

Step S208: If the middleware judges that there is no idle connection between the middleware and the database in its own connection pool, save the business request, and continue to judge whether there is an idle connection between the middleware and the database in the connection pool according to the set rules Connect until an idle connection appears in the connection pool, select the idle connection that appears, and then execute step S210.

It should be noted that the service request may be stored in a processing queue, or in a preset cache, or in any other appropriate storage form.

In the actual implementation process, those skilled in the art can set specific rules for continuously judging whether there is an idle connection between the middleware and the database in the connection pool according to actual needs. For example: poll the status of each connection between the connection pool and the database every set time interval to determine whether there is an idle connection.

Step S210: the middleware uses the selected idle connection to send the service request to the database.

The middleware selects an idle connection to send the service request to the database, and since there is an idle connection in the database, the service request can be guaranteed to be processed.

Step S212: The middleware intercepts the response result to the service request returned by the database to the application through the selected idle connection, and sends the intercepted response result to the application sending the service request.

After the database finishes processing the service request, it returns the response result to the application through the connection sending the service request. At this time, the middleware intercepts the response result to the service request returned by the database.

How the middleware determines the application corresponding to the response result can be set by those skilled in the art according to the actual situation, for example: the business request sent by the middleware to the database can carry the identification information of the application that sent the business request, and the database returns the response In the result, the response result also carries application identification information, and when the middleware intercepts the response result, the corresponding application can be determined according to the application identification information in the response result.

In related technologies, a non-distributed database system such as a relational database system mainly adopts an architecture of direct connection between an application and a database, which causes the database to be unable to respond to service requests exceeding the upper limit of its number of connections. And through the service request processing method provided in this embodiment, in the database system, especially in the non-distributed database system such as the relational database system, the middleware between the application and the database is set, and the middleware intercepts the service request sent by the application to the database. Select an idle connection between the middleware and the database from the middleware's own connection pool to send to the business request. When there is an idle connection in the middleware, the business request can be directly sent to the database through the idle connection. When the middleware When there is no idle connection, the business request of the application is still accepted normally, and when an idle connection occurs, the business request will be sent to the database for processing without returning an error or failure message to the application. It can be seen that the application only needs to send a business request once to ensure that the business request is processed by the database, which can not only prevent the user from receiving the message that the business request fails, resulting in a decrease in user experience, but also prevent the application from repeatedly sending business requests. The operating burden of the terminal and the network can improve the user experience. In addition, the middleware only sends business requests to the database for processing when there is an idle connection in the database. The database does not need to repeatedly judge whether there is an idle connection and does not need to return a message of business request failure to the application. Therefore, the operational burden of the database can be effectively reduced .

Embodiment three

Referring to FIG. 3 , it shows a schematic flowchart of steps of a service processing method according to Embodiment 3 of the present invention.

The business processing method of this embodiment specifically includes the following steps:

Step S302: The middleware generates a connection pool according to the connection information supported by the database.

Wherein, the middleware is arranged between the application and the database. A connection pool is used to manage the connections that a database can support.

An optional generation method for the middleware to generate a connection pool based on the connection information that the database can support is as follows: the middleware determines the upper limit of the connection that the database can support according to the connection information that the database can support; set the same number in the connection pool Connection. For example: the upper limit of connections supported by the database is 50 connections, then the middleware establishes 50 connections in the connection pool.

The service processing method in this embodiment can be applied to various database systems. Preferably, the service request processing method in this embodiment is applied to a non-distributed database system, more preferably, to a relational database system. Since the current non-distributed database systems such as relational database systems process business requests, the application directly sends business requests to the database, and the database directly responds or rejects the business requests sent by the application. When the number of business requests reaches the upper limit that the database can support, the database will directly return a message of business request failure to the application, affecting the user experience. Therefore, apply the business request processing method in this embodiment to a relational database, set middleware between the application and the database, and use the middleware to cache business requests that the database cannot process immediately, and wait for the database to have an idle connection to process the business When the request is made, the business request is sent to the database without returning an error or failure message to the application, which can effectively solve the problems affecting the user experience.

Step S304: the middleware intercepts the service request sent by the application to the database, and returns a message that the service request is accepted to the application.

It should be noted that it is optional for the middleware to return the message that the business request is accepted to the application. Accepted message. By returning the message that the business request is accepted to the application, the application can confirm that the business request has been successfully accepted, avoiding the application to continuously send inquiry messages to the database or middleware, and reducing the operation burden of the application and the information interaction burden of the network.

Step S306: the middleware judges whether there is an idle connection between the middleware and the database in its own connection pool, if yes, execute step S308, if not, execute step S310.

A preferred way for the middleware to determine whether there is an idle connection with the database in the connection pool is as follows:

The middleware judges whether there is an idle connection with the database in the connection pool according to the connection status of each connection in the connection pool; when there is a connection whose connection status is idle, it is determined that there is an idle connection with the database in the connection pool; When the status of all connections is busy, it is determined that there is no idle connection with the database in the connection pool.

Another way for the middleware to judge whether there is an idle connection with the database in the connection pool is as follows: the middleware can determine that there is an idle connection with the database in the connection pool when it judges that the response result returned by the database is intercepted.

Step S308: If the middleware determines that there is an idle connection in the connection pool, select an idle connection, and then execute step S312.

Step S310: If the middleware determines that there is no idle connection in its own connection pool, the middleware saves the service request, and returns to step S306.

For example, the middleware stores the service request in a pending queue, or stores the service request in a preset cache.

That is, if the middleware judges that there is no idle connection in the connection pool, it will return to step S306 and continue to judge whether there is an idle connection with the database in the connection pool according to the set rules until there is an idle connection in the connection pool, and select the one that appears. idle connection.

Preferably, the setting rules can be set to include but not limited to the following rules:

In the first rule, the middleware judges whether there is an idle connection with the database in the connection pool according to the set time interval. Wherein, the setting of the time interval can be set by those skilled in the art according to actual needs, for example: set to poll the connection in the connection pool again every 1 second after polling all the connections between the connection pool and the database .

In the second rule, the middleware judges in real time whether there is an idle connection to the database in the connection pool.

It should be noted that, in this step, it is judged whether there is an idle connection with the database in the connection pool, until an idle connection appears in the connection pool, any preferred method described in step S306 can be selected.

Step S312: the middleware changes the connection state of the selected idle connection from idle to busy, and uses the selected idle connection to send a service request to the database.

The middleware can efficiently and quickly determine the current state of each connection in the connection pool by changing the connection state of the selected idle connection to busy, so that the idle connection can be selected for the service request more effectively.

When the middleware uses the selected idle connection to send a business request to the database, it will send the business request according to the position of the business request in the queue or the priority of the business request, specifically:

When the business request is stored in the queue to be processed, the business request is sequentially taken out from the queue to be processed, and an idle connection is allocated for the taken out business request, and the business request is sent to the database using the allocated idle connection.

When the service request is stored in the preset cache, the service request is taken out in sequence according to the priority of the service request, and an idle connection is allocated for the taken out service request, and the service request is sent to the database using the allocated idle connection.

That is to say, if the service request saved in step S310 is located at the first place in the queue to be processed or has the highest priority in the preset cache, then when an idle connection is selected, the service request can be directly sent to database. And if the service request is not at the top of the queue to be processed or is not the service request with the highest priority, you need to wait until the service request before the service request in the queue to be processed, or with a priority higher than the service request Only after the priority business request is sent to the database can an idle connection be selected to send the service request to the database.

Step S314: The middleware intercepts the response result to the service request returned by the database to the application through the selected idle connection.

The database receives the business request, and after processing the business request, it returns the response to the business request to the application through the idle connection selected by the previous middleware. At this time, the middleware intercepts the response result.

Step S316: According to the intercepted response result, the middleware changes the connection state of the connection returning the response result from busy to idle, and at the same time, the middleware sends the intercepted response result to the application sending the service request.

In this step, when the middleware intercepts the response result returned by a certain connection, it changes the connection status of the connection from busy to idle, so that the middleware can allocate connections for unprocessed service requests and improve connection utilization.

At the same time, the middleware will send the intercepted response result to the application that sends the business request.

It should be noted that the modification of the connection state and the sending of the response result to the application can be executed in parallel or in any order.

Through the service request processing method provided in this embodiment, in a database system, especially a non-distributed database system such as a relational database system, middleware between the application and the database is set, and the middleware intercepts the service request sent by the application to the database, from Select an idle connection with the database in the connection pool to send the business request. When there is an idle connection in the connection pool, the business request can be directly sent to the database through the idle connection. When there is no idle connection in the connection pool, it will still Accept the business request of the application normally, and send the business request to the database for processing when an idle connection occurs, without returning an error or failure message to the application. It can be seen that the application only needs to send a business request once to ensure that the business request is processed by the database, which can not only prevent the user from receiving the message that the business request fails, resulting in a decrease in user experience, but also prevent the application from repeatedly sending business requests. The operating burden of the terminal and the network can improve the user experience. In addition, the middleware only sends business requests to the database for processing when there are idle connections in the database. The database does not need to repeatedly judge whether there are idle connections in the connection pool, nor does it need to return a message of business request failure to the application. Therefore, it can effectively reduce the workload of the database. Workload.

Embodiment four

Referring to FIG. 4 , it shows a schematic structural diagram of a service request processing apparatus according to Embodiment 4 of the present invention.

The service request processing device in this embodiment can be set between the application device and the database device. The service request processing device includes: a first interception module 402, which is used to intercept the service request sent by the application device to the database device; a judging module 404, which is used to judge Whether there is an idle connection with the database device in the connection pool; the first execution module 406 is used to save the service request if the judging result of the judging module is that there is no idle connection, and continue to judge the connection pool according to the set rules. Whether there is an idle connection with the database device, until an idle connection appears in the connection pool; the sending module 408 is used to select the idle connection that appears, and use the selected idle connection to send the service request to the database device. It should be noted that the service request processing device, the application device and the database device may be set in the same device, or may be respectively set in different devices. This is not specifically limited in this embodiment.

Through the service request processing device provided in this embodiment, in a database system, especially a non-distributed database system such as a relational database system, it is possible to intercept the service request sent by the application device to the database device, and select a connection with the database device from the connection pool. When there is an idle connection, the service request can be directly sent to the database device through the idle connection. When there is no idle connection, the service request of the application is still accepted normally. When an idle connection occurs, the service request will be sent Business requests are sent to the database for processing without returning an error or failure message to the application. It can be seen that the application device only needs to send a service request once to ensure that the service request is processed by the database, which can not only prevent the user from receiving a message that the service request fails, resulting in a decrease in user experience, but also prevent the application from repeatedly sending service requests. The operating burden of the terminal where the application is located and the network can also improve the user experience. In addition, the service request processing device of this embodiment only sends the service request to the database device for processing when there is an idle connection in the database device, and the database device does not need to repeatedly judge whether it has an idle connection, nor does it need to return a message of service request failure to the application. Therefore, the operational burden on the database device can be effectively reduced.

Embodiment five

Referring to FIG. 5 , it shows a schematic structural diagram of a service request processing apparatus according to Embodiment 5 of the present invention.

This embodiment further optimizes the service request processing device in the fourth embodiment. The optimized service request processing device includes: a first interception module 502, which is used to intercept the service request sent by the application device to the database device; a judgment module 504, It is used to judge whether there is an idle connection with the database device in the connection pool; the first execution module 506 is used to save the business request if the judgment result of the judgment module is that there is no idle connection, and continue to judge according to the set rules Whether there is an idle connection with the database device in the connection pool, until an idle connection appears in the connection pool, select the idle connection that occurs; the sending module 508 is used to select the idle connection that occurs, and use the selected idle connection to send the service request to the database device.

Preferably, the service request processing device in this embodiment further includes: a second execution module 510, configured to select an idle connection if the judging result of the judging module 504 is that there is an idle connection with the database in the connection pool, and use the selected The idle connection sends the service request to the database.

Preferably, the service request processing device in this embodiment further includes: a second interception module 512, configured to intercept the response result to the service request returned by the database device to the application device through the selected idle connection, and convert the intercepted response result Sent to the application sending the service request.

Preferably, the service request processing device in this embodiment further includes: a connection pool generation module 514, configured to, according to the connection information supported by the database device, before the first interception module 502 intercepts the service request sent by the application device to the database device, A connection pool is generated, wherein the connection pool is used to manage connections that the database device can support.

Preferably, the first interception module 502 is configured to intercept the service request sent by the application device to the database device, and return a message that the service request is accepted to the application device.

Preferably, the judging module 504 includes: a state judging module 5042, which is used to judge whether there is a connection between the middleware device and the database device in the connection pool of the middleware device itself according to the connection status of each connection in the connection pool of the middleware device itself. Idle connection; Determining module 5044 is used to determine that there is an idle connection between the database device in the connection pool when the judgment result of the state judgment module 5042 is that there is a connection whose connection state is idle; when the judgment result of the state judgment module 5042 is When the states of all connections are busy, it is determined that there is no idle connection with the database device in the connection pool.

Preferably, the sending module 508 is configured to change the connection status of the selected idle connection from idle to busy, and use the selected idle connection to send a service request to the database device; the service request information processing device of this embodiment also includes: connection status The modification module 516 is configured to, after the second interception module 512 intercepts the response result to the service request returned by the database device to the application device through the selected idle connection, according to the intercepted response result, the connection status of the connection that will return the response result Change from busy to free.

Preferably, when the first execution module 506 continues to judge whether there is an idle connection with the database device in the connection pool according to the set rules: when it is judged that the response result returned by the database device is intercepted, then it is determined that there is between idle connections.

Preferably, when the first execution module 506 continues to judge whether there is an idle connection with the database device in the connection pool according to the set rules: judge whether there is an idle connection with the database device in the connection pool at a set time interval; or , judging in real time whether there is an idle connection with the database device in the connection pool.

Preferably, when storing the service request, the first execution module 506 stores the service request in a queue to be processed; or stores the service request in a preset cache.

Preferably, when the sending module 508 uses the selected idle connection to send the service request to the database device: when the service request is stored in the queue to be processed, the service request is sequentially taken out from the queue to be processed, and an idle connection is allocated for the taken out service request, Use the allocated idle connection to send the service request to the database device; when the service request is stored in the preset cache, take out the service request in sequence according to the priority of the service request, and allocate an idle connection for the taken out service request, and use the allocated idle connection Send the service request to the database device.

Preferably, the service request processing apparatus of this embodiment is applied to a non-distributed database system.

Preferably, the service request processing apparatus of this embodiment is applied to a relational database system.

Preferably, the service request processing device of this embodiment is a middleware device, which is arranged between the application device and the database, and the middleware device is provided with its own connection pool, and the middleware intercepts the application device to the database device When sending a service request, judge whether there is an idle connection between the middleware and the database device in the connection pool of the middleware device itself; when judging that there is an idle connection between the middleware and the database device, select an idle connection, and A service request is sent to the database using the selected idle connection. When it is judged that there is no idle connection between the middleware and the database device, then save the intercepted service request, and continue to judge whether there is an idle connection between the middleware and the database device in its own connection pool according to the set rules, Until an idle connection appears in the connection pool, select the idle connection that appears, and use the selected idle connection to send the service request to the database device.

The service request processing apparatus in this embodiment is used to implement the corresponding service request processing methods in the first embodiment, the second embodiment and the third embodiment, and has the beneficial effects of the corresponding method embodiments, which will not be repeated here.

The service request processing solution provided here is not inherently related to any specific computer, virtual system or other equipment. Various generic systems can also be used with the teachings based on this. The structure required to construct a system having the solution of the present invention is apparent from the above description. Furthermore, the present invention is not specific to any particular programming language. It should be understood that various programming languages can be used to implement the content of the present invention described herein, and the above description of specific languages is for disclosing the best mode of the present invention.

In the description provided herein, numerous specific details are set forth. However, it is understood that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure the understanding of this description.

Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the invention, in order to streamline this disclosure and to facilitate an understanding of one or more of the various inventive aspects, various features of the invention are sometimes grouped together in a single embodiment, figure, or its description. This method of disclosure, however, is not to be interpreted as reflecting an intention that the claimed invention requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the Detailed Description are hereby expressly incorporated into this Detailed Description, with each claim standing on its own as a separate embodiment of this invention.

Those skilled in the art can understand that the modules in the device in the embodiment can be adaptively changed and arranged in one or more devices different from the embodiment. Modules or units or components in the embodiments may be combined into one module or unit or component, and furthermore may be divided into a plurality of sub-modules or sub-units or sub-assemblies. All features disclosed in this specification (including accompanying claims, abstract and drawings) and any method or method so disclosed may be used in any combination, except that at least some of such features and/or processes or units are mutually exclusive. All processes or units of equipment are combined. Each feature disclosed in this specification (including accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.

Furthermore, those skilled in the art will understand that although some embodiments described herein include some features included in other embodiments but not others, combinations of features from different embodiments are meant to be within the scope of the invention. and form different embodiments. For example, in the claims, any one of the claimed embodiments can be used in any combination.

The various component embodiments of the present invention may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. Those skilled in the art should understand that a microprocessor or a digital signal processor (DSP) may be used in practice to implement some or all functions of some or all components in the service request processing solution according to the embodiment of the present invention. The present invention can also be implemented as an apparatus or an apparatus program (for example, a computer program and a computer program product) for performing a part or all of the methods described herein. Such a program for realizing the present invention may be stored on a computer-readable medium, or may be in the form of one or more signals. Such a signal may be downloaded from an Internet site, or provided on a carrier signal, or provided in any other form.

It should be noted that the above-mentioned embodiments illustrate rather than limit the invention, and that those skilled in the art will be able to design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" or "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention can be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In a unit claim enumerating several means, several of these means can be embodied by one and the same item of hardware. The use of the words first, second, and third, etc. does not indicate any order. These words can be interpreted as names.

The embodiment of the present invention discloses A1, a service request processing method, including:

Intercept the business request sent by the application to the database;

Judging whether there is an idle connection with the database in the connection pool;

If it does not exist, then save the service request, and continue to judge whether there is the idle connection with the database in the connection pool according to the set rules until the idle connection appears in the connection pool;

Select the idle connection that appears, and use the selected idle connection to send the service request to the database.

A2. The method according to A1, wherein the method also includes:

If there is an idle connection to the database in the connection pool, select an idle connection, and use the selected idle connection to send the service request to the database.

A3. The method according to A1, wherein the method also includes:

Intercepting the response result to the service request returned by the database to the application through the selected idle connection, and sending the intercepted response result to the application sending the service request.

A4. The method according to A1, wherein, before the step of intercepting the service request sent by the application to the database, the method further includes:

The connection pool is generated according to the information of the connections supported by the database, wherein the connection pool is used to manage the connections supported by the database.

A5. The method according to A1, wherein the interception of the service request sent by the application to the database includes:

Intercepting the service request sent by the application to the database, and returning a message that the service request is accepted to the application.

A6. The method according to A1, wherein the step of judging whether there is an idle connection with the database in the connection pool includes:

According to the connection state of each connection in the connection pool, it is judged whether there is an idle connection with the database in the connection pool;

When there is a connection whose connection state is idle, it is determined that there is an idle connection with the database in the connection pool; when all the connections are busy, it is determined that there is no idle connection with the database in the connection pool .

A7. The method according to A6, wherein the step of sending the service request to the database using the selected idle connection includes:

changing the connection state of the selected idle connection from idle to busy, and using the selected idle connection to send the service request to the database.

A8. The method according to A3, wherein, after the step of intercepting the response result of the service request returned by the database to the application through the selected idle connection, the method further includes:

According to the intercepted response result, change the connection state of the connection returning the response result from busy to idle.

A9. The method according to A8, wherein the step of continuously judging whether there is an idle connection with the database in the connection pool according to the set rules includes:

When it is judged that the response result returned by the database is intercepted, it is determined that there is an idle connection with the database in the connection pool.

A10. The method according to A8, wherein the step of continuously judging whether there is an idle connection with the database in the connection pool according to the set rules includes:

judging whether there is an idle connection with the database in the connection pool according to a set time interval;

or,

It is judged in real time whether there is an idle connection with the database in the connection pool.

A11. The method according to A2, wherein the step of saving the service request includes:

storing the service request in a waiting queue; or storing the service request in a preset cache.

A12. The method according to A11, wherein the step of using the selected idle connection to send the service request to the database includes:

When the business request is stored in the queue to be processed, the business request is sequentially taken out from the queue to be processed, and an idle connection is allocated for the taken out business request, and the service request is sent to said database;

When the service requests are stored in the preset cache, the service requests are sequentially taken out according to the priority of the service requests, and idle connections are allocated for the taken out service requests, and the allocated idle connections are used to connect the Service requests are sent to the database.

A13. The method according to A1, wherein the service request processing method is applied to a non-distributed database system.

A14. The method according to A1 or A13, wherein the service request processing method is applied to a relational database system.

The embodiment of the present invention also discloses B15, a service request processing device, the service request processing device includes:

The first interception module is used to intercept the service request sent by the application device to the database device;

A judging module, configured to judge whether there is an idle connection with the database device in the connection pool;

The first execution module is configured to save the service request if the judging result of the judging module is that there is no idle connection, and continue judging whether the connection pool with the database device exists in the connection pool according to the set rules between idle connections until the idle connection appears in the connection pool;

A sending module, configured to select the idle connection that appears, and use the selected idle connection to send the service request to the database device.

B16. The service request processing device according to B15, wherein the device also includes:

The second execution module is configured to select an idle connection if the judging result of the judging module is that there is an idle connection with the database in the connection pool, and send the service request to the database.

B17. The service request processing device according to B15, wherein the device also includes:

The second interception module is configured to intercept the response result to the service request returned by the database device to the application device through the selected idle connection, and send the intercepted response result to the sending The application device of the service request.

B18. The service request processing device according to B15, wherein the device also includes:

A connection pool generation module, configured to generate the connection pool according to the information of the connections supported by the database device before the first interception module intercepts the service request sent by the application device to the database device, wherein the connection pool Used to manage the connections supported by the database appliance.

B19. The service request information processing device according to B15, wherein the first interception module is configured to intercept the service request sent by the application device to the database device, and return the service request to the application device accepted message.

B20. The service request processing device according to B15, wherein the judging module includes:

A status judging module, configured to judge whether there is an idle connection with the database device in the connection pool according to the connection status of each connection in the connection pool;

A determination module, configured to determine that there is an idle connection with the database device in the connection pool when the judgment result of the state judgment module is that there is a connection whose connection state is idle; when the judgment of the state judgment module As a result, when the status of all connections is busy, it is determined that there is no idle connection with the database device in the connection pool.

B21. The service request processing device according to B20, wherein the sending module is configured to change the connection status of the selected idle connection from idle to busy, and send the selected idle connection to the database device Send the service request;

B22. According to the service request processing device described in B18, the service information processing device also includes:

The connection state changing module is configured to, after the second intercepting module intercepts the response result to the service request returned by the database device to the application device through the selected idle connection, according to the intercepted A response result that changes the connection status of the connection that returned the response result from busy to idle.

B23. The service request processing device according to B22, wherein, when the execution module continues to judge whether there is an idle connection with the database device in the connection pool according to the set rules:

When it is judged that the response result returned by the database device is intercepted, it is determined that there is an idle connection with the database device in the connection pool.

B24. The service request processing device according to B22, wherein, when the execution module continues to judge whether there is an idle connection with the database device in the connection pool according to the set rules:

judging whether there is an idle connection with the database device in the connection pool according to a set time interval;

or,

It is judged in real time whether there is an idle connection with the database device in the connection pool.

B25. The service request processing device according to B16, wherein, when the first execution module saves the service request, it stores the service request in a queue to be processed; or, stores the service request in a preset cache.

B26. The service request processing device according to B25, wherein when the sending module uses the selected idle connection to send the service request to the database device:

When the business request is stored in the queue to be processed, the business request is sequentially taken out from the queue to be processed, and an idle connection is allocated for the taken out business request, and the service request is sent to said database means;

When the service requests are stored in the preset cache, the service requests are sequentially taken out according to the priority of the service requests, and idle connections are allocated for the taken out service requests, and the allocated idle connections are used to connect the A service request is sent to the database device.

B27. The service request processing device according to B15, wherein the service information processing device is applied to a non-distributed database system.

B28. The service request processing device according to B15 or B27, wherein the service information processing device is applied to a relational database system.

Claims (10)

1. A service request processing method, comprising: Intercept the business request sent by the application to the database; Judging whether there is an idle connection with the database in the connection pool; If not, save the service request, and continue to judge whether there is an idle connection with the database in the connection pool according to the set rules until the idle connection appears in the connection pool; and Select the idle connection that appears, and use the selected idle connection to send the service request to the database. 2. The method of claim 1, wherein the method further comprises: If there is an idle connection to the database in the connection pool, select an idle connection, and use the selected idle connection to send the service request to the database. 3. The method of claim 1, wherein the method further comprises: Intercepting the response result to the service request returned by the database to the application through the selected idle connection, and sending the intercepted response result to the application sending the service request. 4. The method according to claim 1, wherein, before the step of intercepting the service request sent by the application to the database, the method further comprises: The connection pool is generated according to the information of the connections supported by the database, wherein the connection pool is used to manage the connections supported by the database. 5. The method according to claim 1, wherein the service request sent by the intercepting application to the database comprises: Intercepting the service request sent by the application to the database, and returning a message that the service request is accepted to the application. 6. The method according to claim 1, wherein the step of judging whether there is an idle connection with the database in the connection pool comprises: According to the connection state of each connection in the connection pool, it is judged whether there is an idle connection with the database in the connection pool; When there is a connection whose connection state is idle, it is determined that there is an idle connection with the database in the connection pool; when all the connections are busy, it is determined that there is no idle connection with the database in the connection pool . 7. The method according to claim 6, wherein the step of sending the service request to the database using the selected idle connection comprises: changing the connection state of the selected idle connection from idle to busy, and using the selected idle connection to send the service request to the database. 8. The method according to claim 3, wherein, after the step of intercepting the response result of the service request returned by the database to the application through the selected idle connection, the method further comprises : According to the intercepted response result, change the connection state of the connection returning the response result from busy to idle. 9. The method according to claim 8, wherein the step of continuously judging whether there is an idle connection with the database in the connection pool according to the set rules comprises: When it is judged that the response result returned by the database is intercepted, it is determined that there is an idle connection with the database in the connection pool. 10. A service request processing device, the service request processing device comprising: The first interception module is used to intercept the service request sent by the application device to the database device; A judging module, configured to judge whether there is an idle connection with the database device in the connection pool; The first execution module is configured to save the service request if the judging result of the judging module is that there is no idle connection, and continue judging whether the connection pool with the database device exists in the connection pool according to the set rules between idle connections until the idle connection appears in the connection pool; and A sending module, configured to select the idle connection that appears, and use the selected idle connection to send the service request to the database device.