Proactive Node Scaling via Predictive Data Tagging

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In stateful environments with stateful REST APIs, horizontal scaling is inefficient as data replication from a source node to a new node is done blindly without considering data usability or ongoing activities, leading to prolonged replication times and performance degradation in production workloads.

Innovation Solution

The system infers the context of ongoing statefulness on the source node, tags data based on usage levels, and predicts the probability of usage to selectively replicate critical data to a target node while retaining less critical data, ensuring the target node becomes fully stateful within a short period.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data replication is performed blindly without considering data usability or ongoing activities, then all data is replicated to the new node, but replication time is prolonged and production workload performance degrades

Engineering Contradiction:
Improvedata completenessVSAvoidreplication time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary analysis of data usage patterns and ongoing activities before initiating replication. By predicting which data will be needed in the near future and identifying ongoing operations, the system prepares a selective replication plan in advance, replicating only necessary data to minimize replication time while maintaining data completeness for operational continuity

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The replication process is segmented into different categories: data being used by REST APIs, data with predicted high usage probability, and data with predicted low usage probability. This segmentation allows the system to replicate different portions of data with different priorities and timing, reducing overall replication time while ensuring critical data is available

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If all data is replicated to ensure the new node is fully stateful, then the new node can operate independently, but replication time increases and source node performance degrades

Engineering Contradiction:
Improvenode independenceVSAvoidscaling efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The system applies partial replication by selecting and replicating only the subset of data that is necessary for the new node to become operational. By using prediction models to identify data with low near-future usage probability, the system replicates less data than the traditional all-or-nothing approach, thereby improving scaling efficiency while still enabling the new node to handle its designated workload independently

Inventive Principle:
Principle #16Partial or excessive action

3Extent of automation

If data replication is performed during production workload, then the new node can be created, but source node performance degrades due to resource consumption

Engineering Contradiction:
Improvehorizontal scaling capabilityVSAvoidsource node performance
Core Design Contradiction:
Extent of automationVSPower

Solution Approach 1:

The system performs preliminary identification and tagging of data that should be replicated before the actual replication begins. By using prediction models to pre-determine which data needs replication based on usage patterns and ongoing activities, the system minimizes the computational overhead during the replication process itself, reducing impact on source node performance while maintaining automated scaling capability

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system uses the source node's own operational data and usage patterns to make intelligent decisions about what to replicate. By leveraging existing monitoring and prediction infrastructure, the system self-determines the replication strategy without requiring external intervention, enabling automated scaling while optimizing resource usage to minimize performance degradation

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12099478B2Method and system for proactively managing horizontal scaling of a node
Publication Date: 2024.09.24 DELL PROD LP
  • US12099478B2 patent drawing
  • US12099478B2 patent drawing
  • US12099478B2 patent drawing

AI summary

A method for managing data replication includes: identifying data being used by an application programming interface (API), in which the data is stored in a source device; tagging the data based on a usage level of the data by the API; obtaining a predicted probability of the usage level of the data; making a first determination that the data is tagged as important data and the predicted probability of the usage level of the data is low; and replicating, based on the first determination, the data from the source device to a target device.