SYSTEM FOR PROVIDING SCALABLE IN-MEMORY CACHING FOR A DISTRIBUTED DATABASE

• US 20100174863A1
• Filed: 03/15/2010
• Published: 07/08/2010
• Est. Priority Date: 11/30/2007
• Status: Abandoned Application

• Current Assignee: Oath Inc. (Verizon Communications Inc.)
• Original Assignee: Yahoo! Inc. (Apollo Global Management, Inc.)
• Inventors: Srivastava, Utkarsh, Ramakrishnan, Raghu, Silberstein, Adam, Fonseca, Rodrigo, Cooper, Brian F.
• Application Number:
  US12/724,260
• Publication Number:
  US 20100174863A1
• Time in Patent Office: Days
• US Class Current: 711/113
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor

Abstract

A system is described for providing scalable in-memory caching for a distributed database. The system may include a cache, an interface, a non-volatile memory and a processor. The cache may store a cached copy of data items stored in the non-volatile memory. The interface may communicate with devices and a replication server. The non-volatile memory may store the data items. The processor may receive an update to a data item from a device to be applied to the non-volatile memory. The processor may apply the update to the cache. The processor may generate an acknowledgement indicating that the update was applied to the non-volatile memory and may communicate the acknowledgment to the device. The processor may then communicate the update to a replication server. The processor may apply the update to the non-volatile memory upon receiving an indication that the update was stored by the replication server.

Claims

1. A method for providing scalable in-memory caching for a distributed database, the method comprising:

receiving a data update from a client, the data update to be applied to a database;

applying the data update to a cache, wherein the cache contains a cached copy of the database;

generating an acknowledgement, wherein the acknowledgment indicates that the data update was applied to the database;

providing the acknowledgement to the client;

communicating, by a processor after providing the acknowledgement, the data update to a replication server; and

applying the data update to the database upon receiving an indication that the data update was stored by the replication server.

2. The method of claim 1 wherein an external process instructs the processor to provide the data update to the replication server.

3. The method of claim 1 wherein communicating, by the processor after providing the acknowledgement, the data update to the replication server further comprises, communicating, by the processor after providing the acknowledgement and after a period of time, the data update to the replication server.

4. The method of claim 1 wherein the database comprises a distributed database.

5. The method of claim 1 further comprising publishing, by the replication server, the data update to a plurality of databases.

6. The method of claim 1 wherein the cache is integrated with the database.

7. The method of claim 1 wherein applying the data update to the cache further comprises:

determining whether the data update comprises an indication that the data update should be applied to the cache; and

applying the data update to the cache if the data update comprises the indication that the data update should be applied to the cache, otherwise not applying the data update to the cache.

8. A method for providing partitioned in-memory caching for a distributed database, the system comprising:

partitioning a database into a plurality of tablets, wherein each of the tablets comprises one or more records of the database;

storing each tablet on one of a plurality of storage units, each of the storage units associated with a local disk and a cache, wherein each cache comprises a cached copy of data stored on the associated storage unit;

receiving an update to a record of the database from a client;

determining the storage unit containing the record;

communicating the update to the determined storage unit;

applying the update to the cache associated with the determined storage unit;

generating an acknowledgement indicating that the update was applied to the record in the database;

providing the acknowledgement to the client;

communicating, after providing the acknowledgement, the update to a replication server; and

writing the update to the local disk of the determined storage unit upon receiving an indication that the update was properly handled by the replication server.

9. The method of claim 8 wherein each record further comprises a sequence number and wherein generating the acknowledgement indicating that the update was applied to the record in the database further comprises:

increasing the sequence number of the record; and

generating an acknowledgment comprising the increased sequence number of the record.

10. The method of claim 8 wherein the replication server comprises a transaction bank.

11. The method of claim 8 wherein writing the update to the local disk of the determined storage unit upon receiving an indication that the update was properly handled by the replication server further comprises:

waiting a period of time for the indication that the update was properly handled by the replication server; and

writing the update to the local disk of the determined storage unit if the indication is received within the period of time, otherwise not writing the update to the local disk of the determined storage unit.

12. The method of claim 8 further comprising publishing, by the replication server, the data item to a plurality of databases.

13. The method of claim 8 wherein the update further comprises a key and wherein determining the storage unit containing the record further comprises hashing the key of the update to determine the storage unit containing the record.

14. The method of claim 8 wherein applying the update to the cache associated with the determined storage unit further comprises:

determining whether the update comprises an indication that the update should be applied to the cache; and

applying the update to the cache if the update comprises the indication that the update should be applied to the cache, otherwise not applying the update to the cache.

15. A system for providing scalable in-memory caching for a distributed database, the system comprising:

a cache operative to store a cached copy of a plurality of data items;

an interface, the interface coupled to the cache, and the interface operative to communicate with a plurality of devices and at least one replication server;

a non-volatile memory, the non-volatile memory coupled to the cache, the non-volatile memory operative to store the plurality of data items;

a processor, the processor coupled to the non-volatile memory, the interface and the cache, the processor operative to receive, via the interface from a device of the plurality of devices, an update to one of the plurality of data items stored in the non-volatile memory, apply the update to the cache, generate an acknowledgement indicating that the update was applied to the non-volatile memory, provide, via the interface to the device of the plurality of devices, the acknowledgement, communicate, via the interface after providing the acknowledgement, the update to the replication server, and apply the data update to the non-volatile memory upon receiving an indication that the update was stored by the replication server.

16. The system of claim 15 wherein an external process instructs the processor to communicate, via the interface after providing the acknowledgment, the update to the data item to the replication server.

17. The system of claim 15 wherein the processor is further operative to communicate, after providing the acknowledgement and after a period of time elapses, the update to the data item to the replication server.

18. The system of claim 15 wherein the non-volatile memory stores a portion of a distributed database.

19. The system of claim 15 wherein the replication server is operative to publish the data item to a plurality of databases.

20. The system of claim 15 wherein the replication server comprises a transaction bank.