Cross-Shard Table Replication for Faster Database Queries

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing database systems struggle with scaling computational and storage capacity to match varying workloads, leading to disruptions and high costs due to interrupted connections and inefficient resource management.

Innovation Solution

Implementing a database system that supports both client-managed and system-managed tables within a common database, allowing intelligent query routing and dynamic resource allocation to optimize access and processing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If database systems use fixed computational and storage capacity, then system stability is maintained, but the system cannot scale to match varying workloads leading to performance degradation and disruptions

Engineering Contradiction:
Improvescaling capacity to match workloadsVSAvoidconnection stability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements dynamic scaling of database capacity by allowing the system to automatically adjust computational and storage resources based on real-time workload conditions. The database service can scale up or down without disrupting client connections, transforming the static capacity model into a dynamic one that adapts to changing demands while maintaining connection stability.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent segments the database system into independent scalable components including compute nodes, storage nodes, and database services. This segmentation allows individual components to be scaled independently to match specific workload requirements without affecting the entire system, enabling flexible capacity adjustment while maintaining overall system reliability.

Inventive Principle:
Principle #1Segmentation

2Productivity

If database systems scale computational capacity dynamically, then workload matching is improved, but connection disruptions occur causing application interruptions and retries

Engineering Contradiction:
Improveworkload processing capacityVSAvoidconnection continuity
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent implements preliminary scaling actions that are prepared in advance but executed smoothly to avoid disruptions. The system pre-configures scaling capabilities and maintains connection state information, allowing capacity changes to be implemented without forcing client applications to reconnect, thereby maintaining both productivity and connection reliability.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary layer (database service layer) that acts as a mediator between client applications and the underlying computational resources. This intermediary absorbs and manages the complexity of scaling operations, allowing capacity changes at the resource level without propagating disruptions to client connections, thus enabling productivity improvement without connection interruptions.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Ease of manufacture

If database systems allocate resources statically, then resource management is simple, but resource utilization is inefficient leading to wasted capacity and high costs

Engineering Contradiction:
Improveresource management complexityVSAvoidresource utilization efficiency
Core Design Contradiction:
Ease of manufactureVSLoss of energy

Solution Approach 1:

The patent implements feedback mechanisms that continuously monitor workload conditions, resource utilization metrics, and performance indicators. This feedback information is used to automatically adjust resource allocation decisions, enabling the system to optimize utilization dynamically without requiring complex manual management, thus improving efficiency while keeping management relatively simple.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent enables the database system to self-manage resource allocation through automated scaling and load balancing mechanisms. The system independently monitors its own state and adjusts resource distribution without external intervention, eliminating the need for complex manual resource management while maximizing utilization efficiency based on actual workload demands.

Inventive Principle:
Principle #25Self-service

4Adaptability or versatility

If database systems increase scaling flexibility, then workload accommodation is improved, but system complexity increases making management more difficult

Engineering Contradiction:
Improveworkload accommodation flexibilityVSAvoidsystem management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal database service layer that handles multiple functions including scaling, load balancing, connection management, and resource allocation through a single integrated interface. This multi-functional approach allows the system to provide high scaling flexibility while presenting a simplified management interface, reducing the apparent complexity for users despite the sophisticated capabilities underneath.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS12468730B1Configuring replication across shards of scalable database tables for improved query performance
Publication Date: 2025.11.11 AMAZON TECH INC
  • US12468730B1 patent drawing
  • US12468730B1 patent drawing
  • US12468730B1 patent drawing

AI summary

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.