Gregory S. Briggs
Engineering at 5 Ave, Seattle, WA

8510344, Aug 13, 2013

Aug 27, 2010

12/870531

Gregory J. Briggs - Seattle WA, US
Vincent M. Rohr - Woodinville WA, US

Amazon Technologies, Inc. - Reno NV

G06F 7/00, G06F 17/30

707802, 707803, 707804

A blob transaction component is a tiered middleware framework component that facilitates data transactions across arbitrary data blobs in an optimistically consistent manner. The component receives a request to transact data across multiple stored data blobs. For each stored data blob, the component creates a duplicate data blob. The component then creates a record blob that includes a pointer to the duplicate data blob. The stored data blob is then modified by the component to point to the record blob using optimistic locking. The component then creates a new data blob that includes modified data. The component further updates the record blob to include a pointer to the new data blob using optimistic locking. Following locking of the record blob, the stored data blob is updated with the modified data by the component, and the record blob, the duplicate data blob, and the new data blobs are deleted.

8402061, Mar 19, 2013

Aug 27, 2010

12/870466

Gregory J. Briggs - Seattle WA, US
Vincent M. Rohr - Woodinville WA, US

Amazon Technologies, Inc. - Reno NV

G06F 17/30

707791, 707706, 707736, 707758, 707781, 707802

A tiered middleware framework for transacting data between an application layer and a data storage layer includes modular components. The tiered middleware framework is implemented when the arrangement of the modular components enables the tiered middleware framework to meet or exceed certain data transaction criteria. However, when the data transaction criteria are not met by the tiered middleware framework with arrangement of the modular components, the modular components in the tiered middleware framework is rearranged.

8510304, Aug 13, 2013

Aug 27, 2010

12/870587

Gregory J. Briggs - Seattle WA, US
Vincent M. Rohr - Woodinville WA, US

Amazon Technologies, Inc. - Reno NV

G06F 7/00, G06F 17/30

707736, 707741, 707742, 707743, 707744

A transactionally consistent indexer is a tiered middleware framework component that updates a transactional index for a data blob according to a data transaction requested by an application. The transactionally consistent indexer determines index entries to be added or removed from a transaction index based on the application request. The transactionally consistent indexer further inserts each index entry to be added into the transaction index. With respect to each index entry to be removed, the transactionally consistent indexer uses a time stamp or version number of the index entry for ensuring optimistic concurrency during deletion. The transactionally consistent indexer then updates a data blob that is associated with each index entry to be added or each index entry to be removed based on the application request.

8621161, Dec 31, 2013

Sep 23, 2010

12/888731

Gregory J. Briggs - Seattle WA, US

Amazon Technologies, Inc. - Reno NV

G06F 12/00

711152, 711117, 711156, 711162

A data object may be moved from a source data store to a destination data store via replication. The replication is initiated when an original data object in a source data store that is capable of being both read from and being written to is read. Following the read, the original data object is then duplicated to a destination data store. The duplicate data object is provided with a state that indicates the duplicate object is duplicated from the source data store and can be read but cannot accept a data write. Subsequently, the state of the original data object is changed to can be read but cannot be written to using optimistic locking. Further, the state of the duplicate data object is also modified to being capable of both read from and written to with the use of optimistic locking. The replication is completed with the deletion of the original data object from the source data store.