Amazon Technologies, Inc.

Mark Roper

Somasundaram Perianayagam

Alexander Richard Keyes

Akshat Vig

Sharatkumar Nagesh Kuppahally

Oren Yossef

Arijit Choudhury

Akanksha Fouzdar

Shitanshu Aggarwal

James Christopher Sorenson

Tony Petrossian

Sudhir Konduru

Arturo Hinojosa

Joon Ahn

Dharmik Dipakbhai Ghoghari

Yang Nan

Debjyoti Roy

Wen Han Albert Huang

A geographically distributed data store including a number of geographically distributed regions may be implemented using replication groups that include multiple regions configured according to replication criteria. First tier replication of particular changes to data stored in the distributed data store may be performed in compliance with the replication criteria, where management of replication state is performed with respect to replication across the replication groups. Independent of the first tier replication, individual replication groups may implement second tier replication of changes to data where management of replication state is performed with respect to replication within the particular replication group. Replication group configuration may be determined using the replication criteria which may include thresholds for replication resource utilization, replication latency and utilization of data change logs.

Group replication for highly global workloads

A service provider network may provider one or more global cloud services across multiple regions. A client may submit a request to create multiple replicas of a service resource in respective instantiations of a service in the multiple regions. The receiving region of the request may determine the capacities of the multiple regions as to serving respective replicas of the service resource. The receiving region may provide a response to the client based on the determined capacities of the regions.

Capacity management for global resources

Systems and methods are disclosed to implement, in a database system, global table management operations for global tables or objects that are replicated across multiple locations. In embodiments, for a regional replica of a global table, a requested change to a metadata property of the replica (e.g., an attribute data type, a write throughput limit, or a time-to-live setting) is propagated to other replicas of the global table at other locations. In embodiments, before performing the requested management operation, the database system may first verify that the operation can be successfully performed in all locations. In embodiments, the operation may be performed optimistically without verification, and rolled back if it cannot be performed everywhere. In embodiments, to serialize management operations on a global table, the database system may check for other pending management operations via a shared control object, and proceed when any pending operations are finished.

Global table management operations for multi-region replicated tables

Growing community of inventors

Bainbridge Island, WA, United States of America

Mark Roper