ELASTIC DATA STORAGE SYSTEM

• US 20180268013A1
• Filed: 03/17/2017
• Published: 09/20/2018
• Est. Priority Date: 03/17/2017
• Status: Active Grant

• Current Assignee: Apple Inc.
• Original Assignee: Apple Inc.
• Inventors: JADIDI, Amir H., PSENICNIK, Rudolf
• Granted Patent: US 10,642,821 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 12/0868 Data transfer between cache memory and other subsystems, e.g. storage devices or host systems
• CPC Class Codes: G06F 12/0875 with dedicated cache, e.g. instruction or stack
• CPC Class Codes: G06F 12/0891 using clearing, invalidating or resetting means
• CPC Class Codes: G06F 16/22 Indexing; Data structures therefor; Storage structures
• CPC Class Codes: G06F 16/2282 Tablespace storage structures; Management thereof
• CPC Class Codes: G06F 16/2358 Change logging, detection, and notification replication G06F16/27
• CPC Class Codes: G06F 16/2453 Query optimisation
• CPC Class Codes: G06F 2212/465 Structured object, e.g. database record
• CPC Class Codes: G06F 2212/601 Reconfiguration of cache memory

Abstract

Disclosed herein are techniques for implementing a database system that provides flexible organizational aspects while retaining the ability to process and respond to database queries in an efficient manner. In particular, the techniques involve utilizing characteristics of both entity-attribute-value (EAV) database technologies and relational database technologies to provide a hybrid approach that exploits a large number of their benefits while eliminating a large number of their deficiencies. According to some embodiments, the techniques can involve implementing at least one central storage repository (configured to implement an EAV-style database), where the central storage repository provides information to at least one distributor to enable the establishment of at least one cached table (implemented in accordance with relational-style databases) within at least one cached storage device. In turn, the cached storage device can process fetch-based queries issued by client computing devices in a highly efficient manner.

Claims

1. A computing device configured to update distributed cached tables associated with a database, the computing device comprising:

at least one processor; and

at least one memory configured to store instructions that, when executed by the at least one processor, cause the computing device to carry out steps that include;

receiving and executing at least one database change query;

analyzing the at least one database change query against cached table storage configuration information to determine whether an update to at least one cached table is required; and

in response to determining that the update to the at least one cached table is required;

providing, to at least one distributor associated with the cached table storage configuration information, database delta information that reflects the execution of the at least one database change query.

2. The computing device of claim 1, wherein the at least one database change query comprises a database update query, a database insertion query, or a database deletion query.

3. The computing device of claim 1, wherein the cached table storage configuration information identifies at least one cached table storage that stores the at least one cached table.

4. The computing device of claim 3, wherein the at least one cached table storage services fetch queries issued by client computing devices.

5. The computing device of claim 1, wherein the update to the at least one cached table is required if the at least one database change query modifies data that corresponds to the at least one cached table.

6. The computing device of claim 1, wherein, in response to receiving the database delta information, the at least one distributor causes the at least one cached table to be updated to reflect the database delta information.

7. The computing device of claim 1, wherein the update to the at least one cache table involves creating, updating, or deleting the at least one cache table.

8. The computing device of claim 1, wherein the database includes at least one revisions table that tracks different database change queries received at the computing device to enable snapshots of the database to be captured and restored via a single database change query.

9. At least one non-transitory computer readable storage medium configured to store instructions that, when executed by at least one processor included in a computing device, cause the computing device to update distributed cached tables associated with a database, by carrying out steps that include:

receiving a fetch query for data stored in the database;

analyzing aspects of the fetch query to identify costs and benefits associated with establishing at least one cached table for the query; and

in response to determining that the benefits exceed the costs;

updating cached table storage configuration information associated with the database to reflect the fetch query, and

providing, to at least one distributor, (1) the cached table storage configuration information, and (2) data associated with the fetch query, to cause the at least one distributor to establish the at least one cached table within at least one cached table storage.

10. The at least one non-transitory computer readable storage medium of claim 9, wherein the costs are based on an amount of storage space required to store a copy of the data associated with the fetch query within the cached table.

11. The at least one non-transitory computer readable storage medium of claim 9, wherein the costs are based on a number of conditions that are included in the fetch query.

12. The at least one non-transitory computer readable storage medium of claim 9, wherein the benefits are based on a reduction in processing that will be achieved by carrying out similar and subsequent fetch queries using the cached table.

13. The at least one non-transitory computer readable storage medium of claim 9, wherein the data includes data that is not specifically targeted by the fetch query, but is included in at least one database table that is targeted by the fetch query.

14. The at least one non-transitory computer readable storage medium of claim 9, wherein the at least one cached table storage services fetch queries issued by client computing devices.

15. A method for updating distributed cached tables associated with a database, the method comprising:

at a distribution computing device;

receiving, from a database manager, (1) database delta information that reflects an execution of at least one database change query, and (2) cached table storage configuration information;

identifying, based on (1) the database delta information, and (2) the cached table storage configuration information, appropriate changes to be propagated to at least one cached table storage, wherein the at least one cached table storage includes at least one cached table associated with the database delta information;

generating at least one cached table update that, when issued to the at least one cached table storage, causes the appropriate changes to be propagated to the at least one cached table; and

issuing the at least one cached table update to the at least one cached table storage.

16. The method of claim 15, wherein the at least one cached table update causes at least one new cached table to be generated within the at least one cached table storage.

17. The method of claim 15, wherein the at least one cached table update causes at least one entry to be added to, updated within, or removed from the at least one cached table.

18. The method of claim 15, wherein the at least one cached table includes a cached table that comprises a flattened representation of data associated with the at least one database change query.

19. The method of claim 15, wherein the at least one cached table includes a cached table that comprises a flattened representation of joined data from two different database tables associated with the at least one database change query.

20. The method of claim 15, further comprising:

receiving a confirmation from the at least one cached table storage that the at least one cached table update is successfully executed; and

forwarding the confirmation to the database manager.