Amazon Technologies, Inc.

Benjamin Jeffery

Eric Samuel Stone

Shawn Jones

Kunal Chopra

Mingzhe Zhu

Alexander Kulikov

A transaction directed to a hierarchy of data objects stored in a non-transactional data store may be executed. The transaction may be received and description of the transaction stored in a parent data object of the hierarchy. Upon storing the description of the transaction, the transaction may be acknowledged as committed. Access requests for the hierarchy of data objects may be serviced by accessing the description of the transaction and applying to child data objects in the hierarchy returned for servicing a query directed to the hierarchy. A new transaction that is received may initiate application of the transaction according to the description in the parent data object with respect to child data objects.

Executing transactions for a hierarchy of data objects stored in a non-transactional data store

A secondary index may be implemented for a distributed data set that is strongly consistent. Updates to a distributed data set that add or remove items from the distributed data set may be reflected in the secondary index as part of performing the update. Pointers to items to be added to a distributed data set may be included in the secondary index as part of processing an insertion request for the new items. Pointers to items removed from a distributed data set may be removed from the secondary index as part of processing a deletion request. Changes to the secondary index may be performed so that the secondary index does not fail to identify items that are present in the distributed data set.

Strongly-consistent secondary index for a distributed data set

Migration of mutable data sets between data stores may be implemented. Multiple data sets may be stored at a source data store. Some of the data sets may be identified for migration to a destination data store. Updates to the identified data sets may be blocked while the identified data sets are copied from the source data store to the destination data store. In some embodiments, the copies of the data sets at the destination data store are validated. Updates to the data sets may then be allowed at the destination data store instead of the source data store.

Growing community of inventors

Vancouver, Canada

Benjamin Jeffery