Amazon Technologies, Inc.

Dropbox, Inc.

Tushar Jain

Don Johnson

Peter Sirota

Gaurav D Ghare

Ashish Kumar Agrawal

Robert Frederick

Jeffrey Barr

Anurag Windlass Gupta

Jakub Kulesza

Alan Geller

Michael Dwan

Yi Wei

Deepak Agarwal

Eric Michael Wagner

Aaron Mohrman

Stefano Stefani

Aleksandras Surna

Tina Wen

Pierpaolo Baccichet

Kyle Consalus

Zelaine Fong

Maxime Larabie-Bélanger

Ryan Joshua Pearl

Daniel Lowe Wheeler

Alexander J Sydell

Guarav D Ghare

Zelanie Fong

Embodiments are provided for a dropsite. In some embodiments, information is received on a creation location and a date and time of creation of a content item, and a determination is made if (i) the date and time of creation is within a predefined span of time, and (ii) the creation location is within a predefined geographical area to permit association of the content item with a shared folder whose inclusion criteria match said date and time and geographic location.

Dropsite for shared content

A distributed database system may perform a single phase commit for transactions involving updates to multiple databases of the distributed database system. A client request may be received that involves updates to multiple database of the distributed database system. The updates may be performed at a front-end database and a back-end database. Log records indicating the updates to the front-end database may be sent to the back-end database. The log records and the updates performed at the back-end database may be committed together as a single phase commit at the back-end database. In the event of a system failure of the front-end database, log records may be requested and received from the back-end database. A restoration of the front-end database may be performed based, at least in part, on the received log records.

Single phase transaction commits for distributed database transactions

Techniques are described for facilitating use of sequences of invocable services in a configurable manner, including by providing a metering service that tracks the use of invocable services by other invocable services or applications. In at least some situations, the invocable services are fee-based Web services or other fee-based network-accessible services, and are made available by providers of the services for use by others in exchange for fees defined by the service providers. The described techniques facilitate use of a sequence of such invocable services by applications in a manner configured by the creators of the applications and providers of the services, including to allow the application creators to define pricing terms that will be used to determine fees that end users of the applications will be charged for use of the invocable services via the applications.

Integration of sequences of invocable services

Techniques are described for facilitating use of invocable services by applications in a configurable manner. In at least some situations, the invocable services are Web services or other network-accessible services that are made available by providers of the services for use by others in exchange for fees defined by the service providers. The described techniques facilitate use of such invocable services by applications in a manner configured by the developers of the applications, including to allow the application developers to configure pricing terms that will be used to determine fees that end users of the applications will be charged for use of the invocable services via the applications. In some situations, the configured pricing terms for a service specify fees for end users that differ in one or more ways from the defined fees charged by the provider of that service.

Providing configurable pricing for use of invocable services by applications

Techniques are described for facilitating use of invocable services by applications in a configurable manner. In at least some situations, the invocable services are Web services or other network-accessible services that are made available by providers of the services for use by others in exchange for fees defined by the service providers. The described techniques facilitate use of such invocable services by applications in a manner configured by the application providers and the service providers, including to track use of third-party invocable services by applications on behalf of end users and to allocate fees that are charged end users between the applications and the services as configured by the providers of the applications and services. In some situations, the configured pricing terms for a service specify fees for end users that differ in one or more ways from the defined fees charged by the provider of that service.

Using configured application information to control use of invocable services

Techniques are described for facilitating interactions between computing systems, such as in accordance with usage models that are configured for available services by the providers of the services. In some situations, the services are Web services, and an electronic Web service ('WS') marketplace is provided via which third-party WS providers make their WSes available to third-party WS consumers who purchase access to those WSes via the electronic marketplace based on configured usage models selected by the consumers. Some or all of the one or more usage models configured for an available WS may each have associated use prices and/or non-price use conditions, and if so access to those WSes using those usage models may be provided only if a consumer requesting access provides appropriate payment and otherwise satisfies the specified use conditions for a selected usage model.

Controlling access to services via usage models

A distributed data warehouse system may maintain data blocks on behalf of clients in multiple clusters in a data store. Each cluster may include a single leader node and multiple compute nodes, each including multiple disks storing data. The warehouse system may store primary and secondary copies of each data block on different disks or nodes in a cluster. Each node may include a data structure that maintains metadata about each data block stored on the node, including its unique identifier. The warehouse system may back up data blocks in a remote key-value backup storage system with high durability. A streaming restore operation may be used to retrieve data blocks from backup storage using their unique identifiers as keys. The warehouse system may service incoming queries (and may satisfy some queries by retrieving data from backup storage on an as-needed basis) prior to completion of the restore operation.

Streaming restore of a database from a backup system

Event notifications can be provided to a user across multiple client devices or platforms. If a user takes action on one device, notifications on all devices can be updated to reflect the action. For example, notifications can be indexed by topic and time sequence (or other sequence), and multiple notifications related to the same topic can be consolidated at a server or the client so that current information can be presented to the user.

Notification feed across multiple client devices

Using configured application pricing to determine end user fees for use of invocable services

Providing configurable use by applications of sequences of invocable services

Growing community of inventors

Bellevue, WA, United States of America

Tushar Jain