US 12,105,692 B1
Shard management for scaling database tables
Aravind Kumar Kumar, Sammamish, WA (US); Praveen Kannan, San Jose, CA (US); Grant A McAlister, Morro Bay, CA (US); Saleem Mohideen, Saratoga, CA (US); Raghavendran Gururajan, Redmond, WA (US); Navaneetha Krishnan Thanka Nadar, Bothell, WA (US); Jan Engelsberg, Sammamish, WA (US); James Laurence Finnerty, Sarasota, FL (US); Murali Brahmadesam, Tiruchirappalli, TN (US); and Sanjay Shanthakumar, Newark, CA (US)
Assigned to Amazon Technologies, Inc., Seattle, WA (US)
Filed by Amazon Technologies, Inc., Seattle, WA (US)
Filed on Sep. 30, 2022, as Appl. No. 17/937,424.
Int. Cl. G06F 7/00 (2006.01); G06F 16/22 (2019.01); G06F 16/25 (2019.01)
CPC G06F 16/2272 (2019.01) [G06F 16/256 (2019.01)] 20 Claims
OG exemplary drawing
 
1. A system, comprising:
at least one processor; and
a memory, storing program instructions that when executed by the at least one processor, cause the at least one processor to implement a database service, configured to:
receive a request that causes a first table of a database to be aligned with a second table of the database according to a specified shard key across a plurality of shards that are mapped to respective storage volumes of a data store for the database according to a placement hierarchy;
store different portions of the first table across the plurality of shards as respective first table slices aligned with corresponding portions of the second table as respective second table slices with same values of the shard key; and
update metadata for performing access requests to identify individual ones of the first table slices stored with individual ones of the second table slices as respective table slice groups, wherein the respective table slice groups are mapped to respective ones of the plurality of shards in the placement hierarchy.