Integrated Database Node for Automatic Sharding

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional database systems face complexity, scalability issues, and user intervention requirements in sharding, leading to difficulties in automatic scaling, data management, and performance degradation.

Innovation Solution

A database system architecture that embeds shard server, shard routing, and metadata management functionalities within a single node, allowing for automatic sharding and scaling without user input, using a unified virtual machine and process, and providing seamless sharding experiences across all instance sizes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If database systems use conventional sharding architecture with separate nodes for shard server, routing, and metadata management, then functionality is distributed, but system complexity increases and automatic scaling becomes difficult

Engineering Contradiction:
Improvesharding functionalityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent combines shard server, shard routing, and configuration server functionalities into a single integrated node. This merging eliminates the need for separate dedicated nodes for each function, reducing system complexity while maintaining full sharding capabilities. The integrated node can simultaneously perform data storage, request routing, and metadata management.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The integrated node is designed to perform multiple functions: it acts as a shard server for data storage, a routing process for request distribution, and a configuration server for metadata management. This multi-functionality allows a single node type to replace multiple specialized nodes, simplifying the overall system architecture.

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

2Reliability

If database systems require user intervention for sharding configuration and scaling, then control is maintained, but ease of operation decreases and user effort increases

Engineering Contradiction:
ImprovecontrolVSAvoiduser effort
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The integrated node architecture enables automatic sharding and scaling operations without requiring user intervention. The system can autonomously perform configuration, distribute data across nodes, and scale horizontally based on demand, eliminating the need for users to manually configure complex sharding parameters while maintaining system reliability.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system pre-configures sharding capabilities within each integrated node, so that when scaling is needed, the nodes are already prepared to perform routing and metadata management functions. This preliminary setup allows for rapid, automatic scaling without requiring users to perform configuration actions at scaling time.

Inventive Principle:
Principle #10Preliminary action

3Power

If database systems use heterogeneous hardware profiles for different node functions, then specialized performance is achieved, but scalability and automatic provisioning become difficult

Engineering Contradiction:
Improvespecialized performanceVSAvoidscalability
Core Design Contradiction:
PowerVSAdaptability or versatility

Solution Approach 1:

The patent employs homogeneous hardware profiles for all integrated nodes, meaning each node has the same computational resources and capabilities. This homogeneity simplifies automatic provisioning and scaling, as the system can deploy identical node templates without needing to match specialized hardware requirements, while the integrated multi-functionality ensures each node can handle diverse workloads.

Inventive Principle:
Principle #33Homogeneity

Data Source

PatentUS20240427804A1Systems and methods for managing sharded data
Publication Date: 2024.12.26 MONGODB INC
  • US20240427804A1 patent drawing
  • US20240427804A1 patent drawing
  • US20240427804A1 patent drawing

AI summary

A database system may comprise one or more nodes, where each node is embedded with functionality of each of a shard server configured for storing, retrieving, managing, and/or updating data; a shard routing process; and metadata management. A single node running these functionalities allows a database system to provide improved sharding functionality. Nodes may run on a same hardware profile. Database systems described herein may provide enhanced scalability and may appropriately scale without any input on the part of users.