Amazon Technologies, Inc.

Michael Paris

Richard Threlkeld

Rohan Deshpande

Michael B Willingham

Jeffrey H Bailey

Karthik Saligrama Shreeram

Christopher Nathan Dowling

Lisa Meenhee Shon

Antoine Francois Charles Boyer

Mohit Srivastava

Amit Patel

Yash Patel

Server-specified subscription filters for long-lived client requests to fetch data in response to events. In one aspect, the techniques encompass a method performed by a set of one or more computing devices. The method includes the step of receiving a long-lived request to fetch data in response to events sent by a client computing device. The method further includes receiving a server-specified subscription filter for the long-lived request and executing the long-lived request. Executing the long-lived request includes creating a persistent function that uses the server-specified subscription filter to map a source event stream to a response event stream. The response event stream is provided to the client computing device. The server-specified subscription filter facilitates filtering of events fetched for the long-lived request in a way that may not be possible or impractical if the subscription client were required to specify the filter in the long-lived request.

Server-specified filters for long-lived client requests to fetch data in response to events

A technology is provided for a fan out for a subscription. A mutation may be received at a data proxy from an application. The mutation may be sent to the data source via a data access resolver associated with the data proxy. Results for the mutation may be received. At least one subscription may be identified which matches combinations of fields in the results for the mutation. A message for the at least one subscription regarding the mutation may be sent to a messaging service to enable the messaging service to publish the message to devices subscribed to at least one topic for the at least one subscription.

Subscription fan out

A technology is provided for conflict resolution in a data proxy for a mutation. A mutation may be received at a data proxy from an application, and the data proxy is in a service provider environment. The mutation may be sent to be processed by a data store via a data access resolver. A conflict message may be received at the data proxy via the data access resolver for a conflict mutation at the data store for the mutation. The conflict may be resolved at the data proxy using a conflict resolution function in the data proxy.

Conflict resolution in a data proxy

A technology is provided for synchronizing data with delayed subscriptions. A request may be received at a data proxy for a data snapshot for an application that has been offline at the client. A subscription may be held for a pre-determined amount of time after the request for the snapshot. The data snapshot may be sent to the client. The data for the subscription may be sent after the pre-determined amount of time.

Synchronizing data with delayed subscriptions

A technology is provided for mutations with immediate feedback. A mutation may be received at a data proxy from an application. The mutation may be sent to a data source via a data access resolver associated with the data proxy. Results of the mutation may be received from the data source. A subscription may be triggered based on receiving the results of the mutation. A message may be sent via a topic provided by the subscription by using a messaging service such that the messaging service publishes the message with the mutation to devices subscribed to the topic.

Growing community of inventors

Seattle, WA, United States of America

Michael Paris