Amazon Technologies, Inc.

Kunal Chopra

Jakub Mateusz Narloch

Mohamed Marzouk Adedoyin Mounirou

Eric Samuel Stone

Shawn Jones

Nikita Pinski

Nicholas Smit

Benjamin Jeffery

Mingzhe Zhu

Ahmed Usman Khalid

Timothy William Bray

Alexander Kulikov

Jamie Christopher Dool

Jesse Marcus Dougherty

Siva Swaroop Palli

Neha Gupta

Tristan Calderbank

Juan Jose Tam-Huang

Techniques for a service provider network to communicatively couple services and/or applications in a serverless computing environment. A pipe component can configure a pipe to integrate two services by transmitting data between services and/or applications using the pipe. The pipe may also be configured to transform how a service processes an event, control timing of event transmissions using the pipe, define an event structure for an event, and/or batch events. Pipes enable an application or service to exchange data with a variety of services provided by the service provider network while controlling what type of data is generated, stored, or transmitted.

Transforming data between cloud entities in an event architecture

Controlling timing of event data transmissions in an event architecture

Integration of cloud entities in an event architecture

Systems and methods are described herein for a service that backs-up and stores events received at an event bus, in order to replay those backed-up events at a later time. In one example, a request to replay an event processed by an event bus may be received, for example, by a service. The event bus may process events by directing individual events to a target to perform an operation on the data. Individual event may include data and metadata indicating attributes of the data. A data object, corresponding to the event may be obtained from an event archive, which stores multiple events organized into a number of data objects according to attributes of the events. An event may be extracted from the data object and sent to the event bus to be reprocessed by the event bus and directed to the target to perform the operation on the data.

Event archiving and replay

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.

Migration of mutable data sets between data stores

Growing community of inventors

Vancouver, Canada

Kunal Chopra