Local key-value database synchronization

• US 10,176,242 B2
• Filed: 07/10/2017
• Issued: 01/08/2019
• Est. Priority Date: 10/15/2013
• Status: Active Grant

• Current Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Original Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Inventors: Shams, Khawaja Salman, Pandey, Prashant, Sivasubramanian, Swaminathan, Zaki, Omer Ahmed, Yanacek, David Craig, Olson, Johanna S, de Kock, Hendrik, Wu, Johnny Ying
• Primary Examiner(s): Stevens, Robert
• Application Number:
  US15/645,900
• Publication Number:
  US 20170308559A1
• Time in Patent Office: 547 Days
• Field of Search: 707638
• CPC Class Codes: G06F 16/23 Updating
• CPC Class Codes: G06F 16/235 Update request formulation
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database
• CPC Class Codes: G06F 16/273 Asynchronous replication or reconciliation

Abstract

A remote distributed data store may be configured to process data updates received through invocation of a common API with reference to a common schema. A local data store may also be configured to process updates through the common API with reference to the common schema. Updates to the local data store may be mapped from the local data store schema to the common schema, and applied to the distributed data store. Updates to the distributed data store may be mapped from the common schema to the local data store schema. User identity may be verified to limit data synchronization to authorized users.

Claims

1. A system, comprising:

a memory to store program instructions which, if performed by at least one processor, cause the at least one processor to perform a method to at least;

receive a request to update a first item of a first collection of items stored in the distributed data store, wherein the first collection of items is stored according to a first schema;

receive, from a computing device storing a second collection of items, information indicative of an update to a second item of the second collection of items, wherein the second collection of items is associated with a first user, wherein the update to the second item is based on a second schema;

map the update to the second item based on the second schema to an update to the second item based on the first schema; and

synchronize, in accordance with a synchronization scope restriction that restricts synchronization of items in the first collection of items with the second collection of items to those items in the first collection of items associated with the first user and based at least in part on mapping the update to the second item based on the second schema to the update to the second item based on the first schema, the first item of the first collection of items with the second item of the second collection of items.

2. The system of claim 1, wherein the synchronization scope restriction restricts the synchronization of items in the first collection to those in the first collection of items for which the first user has read privileges.

3. The system of claim 1, wherein to synchronize the first item of the first collection of items with the second item of the second collection of items, the program instructions cause the at least one processor to perform the method to verify an identity of the first user as a user associated with the first collection of items.

4. The system of claim 1, wherein the program instructions cause the at least one processor to perform the method to further:

receive, from another computing device storing a third collection of items, information indicative of another update to a third item of the third collection of items, wherein the third collection of items is associated with a second user, wherein the update to the third item is based on a third schema;

map the update to the third item based on the third schema to an update to the third item based on the first schema; and

synchronize, in accordance with another synchronization scope restriction that restricts synchronization of items in the first collection of items with the third collection of items to those items in the first collection of items associated with the second user and based at least in part on mapping the update to the third item based on the third schema to the update to the third item based on the first schema, the third item of the second collection of items with one or more other items of the first collection of items, wherein the synchronization excludes the update to the first item of the first collection of item as associated with the first user.

5. The system of claim 1, wherein the synchronization of the first item of the first collection of items with the second item of the second collection of items is further performance in accordance with a throughput restriction corresponding to the first user.

6. The system of claim 1, wherein to map the update to the second item based on the second schema to the update to the second item based on the first schema, the program instructions cause the at least one processor to perform the method to map from one or more relational database tables to a key-value collection.

7. The system of claim 1, wherein the distributed data store is a data storage service, wherein the computing device is a client of the data storage service, wherein the request to update the first item of the first collection of items and the information indicative of the update to the second item of the second collection of items may be received according to respective application programming interface (API) calls.

8. A method, comprising:

receiving a request to update a first item of a first collection of items stored in the distributed data store, wherein the first collection of items is stored according to a first schema;

receiving, from a computing device storing a second collection of items, information indicative of an update to a second item of the second collection of items, wherein the second collection of items is associated with a first user, wherein the update to the second item is based on a second schema;

mapping the update to the second item based on the second schema to an update to the second item based on the first schema; and

synchronizing, in accordance with a synchronization scope restriction that restricts synchronization of items in the first collection of items with the second collection of items to those items in the first collection of items associated with the first user and based at least in part on mapping the update to the second item based on the second schema to the update to the second item based on the first schema, the first item of the first collection of items with the second item of the second collection of items.

9. The method of claim 8, wherein the synchronization scope restriction restricts the synchronization of items in the first collection to those in the first collection of items for which the first user has read privileges.

10. The method of claim 8, wherein synchronizing the first item of the first collection of items with the second item of the second collection of items comprises verifying an identity of the first user as a user associated with the first collection of items.

11. The method of claim 8, further comprising:

receiving, from another computing device storing a third collection of items, information indicative of another update to a third item of the third collection of items, wherein the third collection of items is associated with a second user, wherein the update to the third item is based on a third schema;

mapping the update to the third item based on the third schema to an update to the third item based on the first schema; and

synchronizing, in accordance with another synchronization scope restriction that restricts synchronization of items in the first collection of items with the third collection of items to those items in the first collection of items associated with the second user and based at least in part on mapping the update to the third item based on the third schema to the update to the third item based on the first schema, the third item of the second collection of items with one or more other items of the first collection of items, wherein the synchronization excludes the update to the first item of the first collection of item as associated with the first user.

12. The method of claim 8, wherein the synchronization of the first item of the first collection of items with the second item of the second collection of items is further performance in accordance with a throughput restriction corresponding to the first user.

13. The method of claim 8, wherein mapping the update to the second item based on the second schema to the update to the second item based on the first schema comprises mapping from one or more relational database tables to a key-value collection.

14. The method of claim 8, wherein the distributed data store is a data storage service, wherein the computing device is a client of the data storage service, wherein the request to update the first item of the first collection of items and the information indicative of the update to the second item of the second collection of items may be received according to respective application programming interface (API) calls.

15. A non-transitory, computer-readable storage medium, storing program instructions that when executed by one or more computing devices, causes the one or more computing devices to implement:

receiving a request to update a first item of a first collection of items stored in the distributed data store, wherein the first collection of items is stored according to a first schema;

receiving, from a computing device storing a second collection of items, information indicative of an update to a second item of the second collection of items, wherein the second collection of items is associated with a first user, wherein the update to the second item is based on a second schema;

mapping the update to the second item based on the second schema to an update to the second item based on the first schema; and

synchronizing, in accordance with a synchronization scope restriction that restricts synchronization of items in the first collection of items with the second collection of items to those items in the first collection of items associated with the first user and based at least in part on mapping the update to the second item based on the second schema to the update to the second item based on the first schema, the first item of the first collection of items with the second item of the second collection of items.

16. The non-transitory, computer-readable storage medium of claim 15, wherein the synchronization scope restriction restricts the synchronization of items in the first collection to those in the first collection of items for which the first user has read privileges.

17. The non-transitory, computer-readable storage medium of claim 15, wherein, in synchronizing the first item of the first collection of items with the second item of the second collection of items, the program instructions cause the one or more computing devices to implement verifying an identity of the first user as a user associated with the first collection of items.

18. The non-transitory, computer-readable storage medium of claim 15, wherein the program instructions cause the one or more computing devices to further implement:

receiving, from another computing device storing a third collection of items, information indicative of another update to a third item of the third collection of items, wherein the third collection of items is associated with a second user, wherein the update to the third item is based on a third schema;

mapping the update to the third item based on the third schema to an update to the third item based on the first schema; and

synchronizing, in accordance with another synchronization scope restriction that restricts synchronization of items in the first collection of items with the third collection of items to those items in the first collection of items associated with the second user and based at least in part on mapping the update to the third item based on the third schema to the update to the third item based on the first schema, the third item of the second collection of items with one or more other items of the first collection of items, wherein the synchronization excludes the update to the first item of the first collection of item as associated with the first user.

19. The non-transitory, computer-readable storage medium of claim 15, wherein, in mapping the update to the second item based on the second schema to the update to the second item based on the first schema, the program instructions cause the one or more computing devices to implement mapping from one or more relational database tables to a key-value collection.

20. The non-transitory, computer-readable storage medium of claim 15, wherein the distributed data store is a data storage service, wherein the computing device is a client of the data storage service, wherein the request to update the first item of the first collection of items and the information indicative of the update to the second item of the second collection of items may be received according to respective application programming interface (API) calls.