Method of optimizing the interaction between a software application and a database server or other kind of remote data source

• US 9,396,228 B2
• Filed: 02/22/2011
• Issued: 07/19/2016
• Est. Priority Date: 02/22/2010
• Status: Active Grant

• Current Assignee: Data Accelerator Ltd.
• Original Assignee: Data Accelerator Ltd.
• Inventors: Corbett, Sean P., Elliott, Edward Philip Edwin, Clothier, Matthew P.
• Primary Examiner(s): Alam, Uzma
• Application Number:
  US13/880,707
• Publication Number:
  US 20130325927A1
• Time in Patent Office: 1,974 Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity
• CPC Class Codes: G06F 16/2453 Query optimisation
• CPC Class Codes: G06F 16/24539 using cached or materialised query results
• CPC Class Codes: H04L 67/01 Protocols

Abstract

The invention is a method of optimizing the interaction between (i) a client, being an application such as database software, implemented on a computing device, and (ii) database server software implemented on a computing device. Query data is routed from the client to the database server software through an optimization system implemented on a computing device and then response data provided by the database server software is routed to the optimization system. The optimization system analyzes that (or later) query data and, based on that analysis, applies rules to response data provided by the database server software, in order to generate optimized response data to thereby speed up the interaction between the client and the database server software.

Claims

1. A method comprising:

routing query data from a client to a database server through an optimisation system implemented on a computing device;

routing response data corresponding to the query data provided by the database server from the database server to the optimisation system;

decoding, by the optimisation system, the query data and/or the response data to generate content and/or context data of the query data and/or the response data, the content and/or the context data specifying how the client and/or the server understands the query data and/or the response data;

analysing, by the optimisation system, the query data;

applying rules, by the optimisation system, to the response data that is routed to the optimisation system from the database server based on analysis of the query data, in order to generate optimised response data at the optimisation system and speed up interaction between the client and the database server, wherein the rules are applied to the response data and the optimised response data is generated after the response data has been generated by the database server and after the response data has been provided to the optimisation system from the database server.

2. The method of claim 1, wherein the query data includes an actual query that the client has asked to be run or a request for data that the client has asked for.

3. The method of claim 1, wherein context of the query data includes whether a query, included as part of the query data, is a part of a series of requests generated by the client and relationships between the requests.

4. The method of claim 1, wherein context of the query data includes environmental details including which server a request included as part of the query data is going to, which user and workstation sent the request, and network link speeds.

5. The method of claim 1, further comprising determining, by the optimisation system based on context of the response data, effectiveness of specific rules applied to specific requests, in order to either change parameters of the rules or enable or disable one or more of the rules.

6. The method of claim 1, further comprising optimising the interaction between the client and the database server to enable a practical connection to be made over a slow link or a high latency link.

7. The method of claim 6, wherein optimising the interaction between the client and the database server further includes speeding up flow of data, causing cessation of the flow of data, obviating a need for data to flow, or managing the flow of data.

8. The method of claim 6, wherein the slow link or the high latency link is over a wide area network or the Internet.

9. The method of claim 1, wherein the query data and the response data include database management server requests and responses.

10. The method of claim 1, wherein the rules are applied based on factors including initiator and server addresses or locations, time of day, configuration, server load, and a combination of these.

11. The method of claim 1, wherein the rules are applied at different points in a request/response stream.

12. The method of claim 1, further comprising:

generating the optimised response data by compressing the response data at the optimisation system after the response data has been generated by the database server and after the response data has been provided to the optimisation system.

13. The method of claim 1, further comprising:

generating the optimised response data by encrypting the response data at the optimisation system after the response data has been generated by the database server and after the response data has been provided to the optimisation system.

14. The method of claim 1, wherein the optimisation system is implemented on the same computing device as the client, wherein a second optimisation system is implemented on a computing device of the database server and wherein the optimisation system and the second optimisation system are separated by a wide area network (WAN) link.

15. The method of claim 14, further comprising routing the response data through the second optimisation system and routing the optimised response data across the WAN to the optimisation system.

16. The method of claim 15, further comprising compressing the response data at the second optimisation system and decompressing the optimised response data at the optimisation system.

17. The method of claim 16, further comprising encrypting the response data at the second optimisation system and decrypting the optimised response data at the optimisation system.

18. A system comprising:

one or more processors;

memory;

a client coupled to the one or more processors and the memory;

a database server coupled to the one or more processors and the memory, the database server including database server software configured to receive query data generated by the client;

an optimisation system coupled between the client, the database server, the one or more processors, and the memory, the optimisation system configured to;

receive the query data from the client and send the query data to the database server;

receive response data corresponding to the query data from the database server;

decode the query data and/or the response data to generate content and/or context data of the query data and/or the response data, the content and/or the context data specifying how the client and/or the server understands the query data and/or the response data;

analyse the query data received from the client;

apply rules to the response data that is received from the database server based on the analysis of the query data in order to generate optimised response data at the optimisation system, and speed up interaction between the client and the database server software, wherein the rules are applied to the response data and the optimised response data is generated after the response data has been generated by the database server and after the response data has been provided to the optimisation system from the database server.

19. The system of claim 18, wherein the query data includes an actual query that the client has asked to be run or a request for data that the client has asked for.

20. The system of claim 18, wherein context of the query data is selected from a group consisting of whether a query, included as part of the query data, is a part of a series of requests generated by the client, a relationship between the requests, and a combination of these.

21. The system of claim 18, wherein context of the query data includes environmental details selected from a group consisting of which server a request included as part of the query data is going to, which user and workstation sent the request, network link speeds, and a combination of these.

22. The system of claim 18, wherein the optimisation system is further configured to determine effectiveness of specific rules applied to specific requests based on context of the response data in order to either change the parameters of the rules or enable or disable one or more of the rules.

23. The system of claim 18, wherein the optimisation system is further configured to optimise the interaction between the client and the database server software to enable a practical connection to be made over a slow link or a high latency link including the Internet, optimising the interaction further including speeding up flow of data between the client and the database server software, causing the cessation of the flow of data, obviating the need for data to flow, or managing the flow of data.

24. The system of claim 18, wherein the query data and the response data include database management server requests and responses.

25. The system of claim 18, wherein the optimisation system is further configured to apply the rules based on factors including initiator and server addresses or locations, time of day, configuration, and server load.

26. The system of claim 18, wherein the optimisation system is further configured to apply the rules at different points in a request/response stream.

27. An optimization system comprising:

means for routing query data from a client to database server software of a database server through an optimisation system implemented on a computing device;

means for routing response data corresponding to the query data provided by the database server software to the optimisation system,

means for decoding the query data and/or the response data to generate content and/or context data of the query data and/or the response data, the content and/or the context data specifying how the client and/or the server understands the query data and/or the response data;

means for analysing the query data;

means for applying rules to the response data based on analysis of the query data, in order to generate optimised response data and speed up interaction between the client and the database server software, wherein the rules are applied to the response data and the optimised response data is generated after the response data has been generated by the database server and after the response data has been provided to the optimisation system from the database server.