# US 2003/0200209 A1 · System and method for routing database requests to a database and a cache

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2003/0200209 A1
- Document ID: US20030200209A1
- Status: Published application
- Kind: A1
- Application number: 10/458,382
- Filed: 2003-06-11
- Published: 2003-10-23
- Earliest claimed: 2000-11-15
- Inventors: Erik Richard Smith; Paul Alan Conley
- Web page: https://patentgrep.com/patent/US20030200209A1

## CPC

- G06F 16/24539: {using cached or materialised query results}
- G06F 16/24524: {Access plan code generation and invalidation; Reuse of access plans}
- Y10S 707/99933: Query processing, i.e. searching
- Y10S 707/99938: Concurrency, e.g. lock management in shared database
- Y10S 707/99952: Coherency, e.g. same view to multiple users
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- Y10S: TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS

## Abstract

A system and method for routing database requests from application logic to a cache and a database, including receiving a database request from the application logic, determining whether the database request is informational or transactional, routing the database request to the cache if the database request is informational, and routing the database request to the database if the database request is transactional. A first example embodiment includes a database which is accessed using a first driver, a cache, and a second driver which determines whether database requests received from application logic are informational or transactional, where informational database requests are routed to the cache and transactional database requests are routed to the database using the first driver.

## Claims

### Claim 1

A method for processing database requests from application logic, comprising:
(a) receiving a database request;
(b) determining whether said database request is informational or transactional;
(c) routing said database request to a cache if said database request is informational; and
(d) routing said database request to a database if said database request is transactional.

### Claim 2 (depends on 1)

The method of claim 1, wherein said database request includes a transaction isolation level, said method further comprising determining whether said transaction isolation level is greater than a first threshold, and if so, routing said database request to said database.

### Claim 3 (depends on 1)

The method of claim 1, wherein said database request includes a concurrency setting, said method further comprising determining whether said concurrency setting is less than a second threshold, and if so, routing said database request to said database.

### Claim 4 (depends on 1)

The method of claim 1, wherein said database request is routed to said cache using a second driver, said database request is routed to said database using a first driver, and said first driver is a slave to said second driver.

### Claim 5 (depends on 1)

The method of claim 1, wherein said determining whether said database request is informational or transactional comprises determining whether said database request is read only, and if so, identifying said database request as informational, and if not, identifying said database request as transactional.

### Claim 6 (depends on 1)

The method of claim 1, wherein said database request includes a reference to target data, and wherein said method further comprises determining whether said target data is stored within said cache, and if not, routing said database request to said database.

### Claim 7 (depends on 1)

The method of claim 1, wherein said method further comprises determining whether said database request is suitable for processing by said cache, and if not, routing said database request to said database.

### Claim 8 (depends on 1)

The method of claim 1, wherein said database request includes a reference to target data, and wherein said routing said database request to said cache comprises determining whether said cache is remote from the application logic, and if so, sending said database request to said cache and determining whether said target data is stored within said cache, and if not, routing said database request to said database.

### Claim 9 (depends on 1)

The method of claim 1, wherein said database stores a memory portion and said cache stores a subset of said memory portion, wherein said method further comprises determining whether said database request changes said subset stored in said database, and if so, updating said subset stored in said cache.

### Claim 10 (depends on 9)

The method of claim 9, wherein said database request comprises an SQL request, and wherein said subset is changed if said SQL request is an INSERT, UPDATE, or DELETE command.

### Claim 11 (depends on 1)

The method of claim 1, wherein said database stores a memory portion and said cache stores a subset of said memory portion, wherein said method further comprises polling said database to determine whether said subset stored in said database has changed, and if so, updating said subset stored in said cache.

### Claim 12 (depends on 1)

The method of claim 1, further comprising:
(e) detecting changes to said database; and
(f) replicating said changes in said cache.

### Claim 13

A system for processing a database request from application logic, wherein target data associated with the database request is stored in a database, and wherein the database is accessed using a first driver, said system comprising:
a cache; and
a second driver to determine whether the database request is informational or transactional,
wherein informational database requests are routed to said cache using said second driver and transactional database requests are routed to the first driver.

### Claim 14 (depends on 13)

The system of claim 13, wherein said cache comprises a main memory database.

### Claim 15 (depends on 14)

The system of claim 14, wherein said cache further comprises a secondary disk cache coupled to said main memory database.

### Claim 16 (depends on 13)

The system of claim 13, wherein said cache stores relational data.

### Claim 17 (depends on 13)

The system of claim 13, wherein the application logic loads said second driver, and said second driver provides an application programming interface (API) for the application logic.

### Claim 18 (depends on 17)

The system of claim 17, wherein the database requests comprise Structured Query Language (SQL) requests.

### Claim 19 (depends on 18)

The system of claim 18, wherein said second driver supports the Open Database Connectivity (ODBC) standard.

### Claim 20 (depends on 18)

The system of claim 18, wherein said second driver supports the Java Database Connectivity (JDBC) standard.

### Claim 21 (depends on 13)

The system of claim 13, wherein said cache communicates with said second driver according to Hypertext Transfer Protocol (HTTP).

### Claim 22 (depends on 13)

The system of claim 13, wherein said cache supports XML Query Language (XQL).

### Claim 23 (depends on 13)

The system of claim 13, wherein said second driver calls the first driver to establish a connection with the database.

### Claim 24 (depends on 13)

The system of claim 13, further comprising:
means for detecting changes to said database; and
means for replicating said changes in said cache.

### Claim 25

Computer executable software code, comprising:
code to receive a database request from application logic;
code to determine whether said database request is informational or transactional;
code to route said database request to a cache if said database request is informational; and
code to route said database request to a database if said database request is transactional.

### Claim 26 (depends on 25)

The software code of claim 25, wherein said database request includes a transaction isolation level, said software code further comprising code to determine whether said transaction isolation level is greater than a first threshold, and if so, to route said database request to said database.

### Claim 27 (depends on 25)

The software code of claim 25, wherein said database request includes a concurrency setting, said software code further comprising code to determine whether said concurrency setting is less than a second threshold, and if so, to route said database request to said database.

### Claim 28 (depends on 25)

The software code of claim 25, wherein code to determine whether said database request is informational or transactional comprises code to determine whether said database request is read only, and if so, to identify said database request as informational, and if not, to identify said database request as transactional.

### Claim 29 (depends on 25)

The software code of claim 25, wherein said database request includes a reference to target data, and wherein said software code further comprises code to determine whether said target data is stored within said cache, and if not, to route said database request to said database.

### Claim 30 (depends on 25)

The software code of claim 25, wherein said software code further comprises code to determine whether said database request is suitable for processing by said cache, and if not, to route said database request to said database.

### Claim 31 (depends on 25)

The software code of claim 25, wherein said database request includes a reference to target data, and wherein said code to route said database request to said cache comprises code to determine whether said cache is remote from the application logic, and if so, to send said database request to said cache and to determine whether said target data is stored within said cache, and if not, to route said database request to said database.

### Claim 32 (depends on 25)

The software code of claim 25, wherein said database stores a memory portion and said cache stores a subset of said memory portion, wherein said software code further comprises code to determine whether said database request changes said subset stored in said database, and if so, to update said subset stored in said cache.

### Claim 33 (depends on 32)

The software code of claim 32, wherein said database request comprises an SQL request, and wherein said subset is changed if said SQL request is an INSERT, UPDATE, or DELETE command.

### Claim 34 (depends on 25)

The software code of claim 25, wherein said database stores a memory portion and said cache stores a subset of said memory portion, wherein said software code further comprises code to poll said database to determine whether said subset stored in said database has changed, and if so, to update said subset stored in said cache.

### Claim 35 (depends on 25)

The software code of claim 25, further comprising:
code to detect changes to said database; and
code to replicate said changes in said cache.

### Claim 36 (depends on 35)

The software code of claim 35, wherein said code to replicate said changes in said cache comprises code to notify said cache of said changes.
