Amazon Technologies, Inc.

Microsoft Technology Licensing, LLC

Srivaths Badrinath Copparam

Timothy Andrew Rath

Wei Xiao

Akshat Vig

Rama Krishna Sandeep Pokkunuri

William Alexander Stevenson

Rajaprabhu Thiruchi Loganathan

Clarence Wing Yin Ng

Maximiliano Maccanti

David S Callahan

Ian A McAllister

Delane Robert Hewett

Christoph Ponath

Mackenzie Steele

Arnold Neil Blinn

Donald Marcus Gillett

Brian R Daugherty

Marius Ionescu

Sirius Kuttiyan

Vijay Narula

Maximliano Maccanti

Stuart James Dent

A system that implements a data storage service may store data for a database table in multiple replicated partitions on respective storage nodes. In response to a request to back up a table, the service may back up individual partitions of the table to a remote storage system independently and (in some cases) in parallel, and may update (or create) and store metadata about the table and its partitions on storage nodes of the data storage service and/or in the remote storage system. Backing up each partition may include exporting it from the database in which the table is stored, packaging and compressing the exported partition for upload, and uploading the exported, packaged, and compressed partition to the remote storage system. The remote storage system may be a key-value durable storage system in which each backed-up partition is accessible using its partition identifier as the key.

Backup of partitioned database tables

A system that implements a data storage service may store data for database tables in multiple replicated partitions on respective storage nodes. In response to a request to back up a table, the service may export individual partitions of the table from the database and package them to be independently uploaded (e.g., in parallel) to a remote storage system (e.g., a key-value durable storage system). Prior to uploading the exported and packaged partitions to the remote storage system, the service may verify that the exported and packaged partitions can be subsequently restored, which may include unpackaging and/or re-inflating the exported and packaged partitions to create additional unpackaged copies of the partitions, re-importing the additional unpackaged copies of the partitions into the database (e.g., as additional replicas), and/or comparing checksums generated for the exported partitions with checksums generated for the additional unpackaged copies of the partitions.

Verification of database table partitions during backup

A system that implements a data storage service may store data for database tables in multiple replicated partitions on respective storage nodes. In response to a request to restore a given table that was backed up in a remote storage system (e.g., key-value durable storage system), the service may create a new table, and may import a copy of each of the partitions of the given table from the remote storage system into the new table. The request to restore the table may specify a modified value for a configuration parameter for the table or for one of its partitions. The service may apply the new configuration parameter value to the table or its partitions during the restore operation. The new configuration parameter value may indicate an increase or decrease in storage capacity or throughput capacity, and its application may automatically trigger a partition split or move operation.

Restoring partitioned database tables from backup

Service provisioning tasks can be performed to provision or deprovision services for users, reconcile overlapping services, and apply effective service properties. A service can be provisioned by receiving a request to provision the service for a user, reconciling new service properties with current service properties, from one or more service instances, to determine effective service properties, and applying the effective service properties as properties to use for the service for the user. A service can also be provisioned by receiving a request to provision the service for a user, storing a new service instance, and reconciling the new service instance with one or more previously stored service instances for the same service to determine effective service properties. A service provisioning system can perform provisioning operations for one or more internal and external service providers.

Syndication of multiple service instances

Various embodiments provide techniques for determining a value share of a mobile transaction for one or more entities associated with the mobile transaction. Examples of mobile transactions include purchases of content such as applications, games, video, audio, graphics, and so on. In one or more embodiments, value share rules can be created and reconfigured. The value share rules specify a share of a transaction value (e.g., a percentage of revenue generated from a purchase of content) that an entity involved in a particular mobile transaction is credited with. In one example scenario, a user of a mobile device purchases an application for the mobile device. A value share rule can be applied to the application purchase amount to determine a share of the application purchase amount that is to be credited to a mobile operator that provides service for the mobile device.

Value determination for mobile transactions

Methods and systems for reviewing content items created by users for presentation in association with a website are provided. Automatic scrubbing (followed by manual review, if necessary) of user-created content items that have yet to be presented in association with a website is provided as is manual review of user-created content items that have already been presented in association with a website at the request of a user.

Reviewing user-created content before website presentation

A Domain Name System (DNS) service provider may be engaged to host DNS service for a domain. Before providing service for a domain, the service provider may wish to verify that the entity that set up the service is the owner, or authorized controller, of the domain. The service provider gives the entity some information, such as a particular pair of name servers, and instructs the entity to have the domain registrar put the information into the name server (NS) record(s) for the domain. The service provider then queries NS for the domain and compares the NS record(s) returned with the information provided to the entity. If the NS records match the information given to the entity, then the service provider concludes that the entity has control over the domain, and uses the DNS records provided by the entity to provide service.

Validating change of name server

Growing community of inventors

Issaquah, WA, United States of America

Srivaths Badrinath Copparam