Amazon Technologies, Inc.

Sanjay Shanthakumar

Murali Brahmadesam

Saleem Mohideen

Arijit Choudhury

Navaneetha Krishnan Thanka Nadar

Sudhir Konduru

Jan Engelsberg

Praveen Kannan

Aravind Kumar Kumar

Tate Andrew Certain

James Christopher Sorenson

Akshat Vig

Douglas Brian Terry

Somasundaram Perianayagam

Sharatkumar Nagesh Kuppahally

Alexander Richard Keyes

Oren Yossef

Richard Shawn Bice

Hao He

Chase Kernan

Derek William Richard Chen-Becker

Ramanathan Padinjarel Somanathan

Grant Alexander McAlister

Rashmi Krishnaiah Setty

James Laurence Finnerty

Abhijeet More

Ray Manpreet Singh Matharu

Akanksha Fouzdar

Nanda Kaushik

Gajanan Sharadchandra Chinchwadkar

Ahmad Mohammad Radi Ahmad Alsmair

Haritabh Gupta

Murtaza Doctor

Asmita Barve

Sanket Vishram Chandorkar

Raghavendran Gururajan

Amit Krishnan

Kiran Pillarisetty

Sambhavi Raghuraman

Awisha Makwana

Timothy Matthew Lewis

Davor Prugovecki

Hina Naseer

Karthikeyani Palanisami

Replication of a client-managed table may be configured across shards of system-managed tables in a database system for improved query performance. A client-managed table may be identified to replicate as a complete copy of the table respectively collocated with two or more shards of one or more other system-managed tables. The complete copy may be stored in respective storage volumes of the two or more shards of the one or more other system-managed tables. Metadata for performing access requests at a database system may be updated to identify the client-managed table as collocated with the two or more shards of the one or more other system-managed tables.

Configuring replication across shards of scalable database tables for improved query performance

Shard management may be implemented for scalable database tables. A table may be identified as aligned with another table of the database according to a common shard key across multiple shards that are mapped to respective storage volumes of a data store of the database according to a placement hierarchy. Different portions of the table may be stored across the shards as respective table slices with corresponding portions of the other table as respective other table slices with same values of the shard key. Metadata for performing access requests to the database may be updated to identify individual ones of the table slices stored with individual ones of the other table slices as respective table slice groups that are mapped to respective ones of the shards in the placement hierarchy.

Shard management for scaling database tables

Replicas may be added to a multi-leader replica group for a data set. A new replica may be added to a group of replicas by copying a version of the data set according to a point in time to the new replica. As updates may occur at different ones of the replicas when the new replica is added, updates that occurred at a source replica for the snapshot and other replicas may be replicated by the different replicas according to the point in time at which the snapshot is created without blocking updates at any of the replicas in the replica group.

Adding replicas to a multi-leader replica group for a data set

A geographically distributed system using a hybrid, multi-master design is disclosed. The system may use global tables, for which both reads and writes may be performed locally, but with a single region serving as a master region. All strongly consistent reads and writes may be sent to the master region, whereas eventually consistent reads and writes may be performed in any region with a replica. The master region may not be statically assigned but may move from region to region. The master region may be assigned manually by client preference or may be assigned and updated automatically based on the time of day or workload characteristics.

Multi-region, multi-master replication of database tables

Growing community of inventors

Milpitas, CA, United States of America

Sanjay Shanthakumar