Hot Data Range Replication for Distributed Key-Value Store Hotspots

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems for managing hotspots in distributed key-value stores face challenges such as labor-intensive manual monitoring, delayed mitigation of hotspots, and ineffective automated solutions that fail to adapt to dynamic data access patterns, leading to inefficient resource utilization and potential system failures.

Innovation Solution

A data platform with a data distributor that dynamically monitors server metrics to identify hot data ranges, replicating them across multiple servers in real-time based on traffic conditions, adjusting the number of replicas to balance load and reduce latency, and automate the process to conserve resources.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual monitoring of hotspots is performed, then system reliability is improved, but labor intensity and operational complexity increase

Engineering Contradiction:
Improvesystem reliabilityVSAvoidoperational complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system performs self-monitoring and self-balancing through automated detection of hotspots and dynamic replication of data ranges. The load balancer automatically identifies hot servers and replicates data without human intervention, making the system self-sufficient in maintaining reliability while reducing operational complexity

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system implements continuous feedback loops where server metrics are monitored, hotspots are detected, and replication decisions are made based on real-time conditions. This feedback mechanism ensures system reliability is maintained through automated responses to changing load conditions

Inventive Principle:
Principle #23Feedback

2Device complexity

If automated hotspot mitigation is implemented, then operational complexity is reduced, but adaptability to dynamic data access patterns deteriorates

Engineering Contradiction:
Improveoperational complexityVSAvoidadaptability to dynamic data access patterns
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The system dynamically adjusts replication factors and data range assignments based on real-time server metrics and access patterns. The load balancer continuously adapts to changing conditions by modifying replication strategies, ensuring both automated operation and adaptability to dynamic data access patterns

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes operational parameters such as replication factor and data range boundaries based on monitored server metrics. These parameter adjustments allow the automated system to adapt to dynamic data access patterns while maintaining low operational complexity

Inventive Principle:
Principle #35Parameter changes

3Reliability

If data replication is increased to balance load, then system reliability is improved, but resource utilization efficiency deteriorates

Engineering Contradiction:
Improvesystem reliabilityVSAvoidresource utilization efficiency
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The system applies partial replication only to hot data ranges that require load balancing, rather than replicating all data. This selective approach improves reliability for critical hotspots while minimizing unnecessary resource consumption and maintaining efficient resource utilization

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS12591590B2Replication of hot data ranges in distributed transactional key-value stores
Publication Date: 2026.03.31 SNOWFLAKE INC
  • US12591590B2 patent drawing
  • US12591590B2 patent drawing
  • US12591590B2 patent drawing

AI summary

A hot server is identified from a plurality of servers based on one or more server metrics associated with the hot server. A hot data range stored by the hot server is identified based on one or more read density metrics. The hot data range comprises a range of data values with a higher volume of access requests compared to other data values stored by the hot server. The hot data range is replicated across a number of additional servers.