Contextual Document Replication Engine for Distributed Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional document replication in distributed computing systems is inefficient as the decision on which document to replicate and where is made outside the document's context, leading to increased latency due to remote data access and replication.

Innovation Solution

A contextual replication engine that analyzes documents for references and metadata to determine if and where to replicate them, using a document analyzer, affinity determiner, and automatic document replicator to optimize replication based on the document's context, thereby reducing latency and improving access efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If documents are replicated across multiple nodes for fault tolerance and load balancing, then system reliability and scalability are improved, but replication efficiency and access latency are worsened due to decisions made outside document context

Engineering Contradiction:
Improvefault toleranceVSAvoidaccess latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary analysis of document context, references, and access patterns before replication decisions are made. The contextual replication engine proactively identifies which documents should be replicated to which nodes based on predicted access needs, rather than reacting to actual access requests. This preliminary action ensures documents are already in optimal locations when needed, reducing access latency while maintaining fault tolerance.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms that continuously monitor document access patterns, node performance, and system state. This feedback informs dynamic replication decisions, allowing the system to adapt to changing conditions. By using feedback from actual access patterns and system performance, the replication strategy is continuously optimized to minimize latency while maintaining reliability.

Inventive Principle:
Principle #23Feedback

2Device complexity

If conventional replication decisions are made outside document context, then system simplicity is maintained, but replication efficiency and query processing performance deteriorate

Engineering Contradiction:
Improvesystem simplicityVSAvoidquery processing efficiency
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The patent introduces a contextual replication engine as an intermediary layer between the document storage system and the query processing system. This intermediary analyzes document context, references, and access patterns to make intelligent replication decisions. By placing this mediator in the architecture, the system gains sophisticated replication capabilities without requiring changes to the core storage and query processing components, thus maintaining relative system simplicity while dramatically improving query processing efficiency.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system enables documents to effectively 'self-determine' their replication destinations by analyzing the documents' own context, internal references, and inherent access patterns. The contextual replication engine extracts this information directly from the documents themselves rather than relying on external metadata or manual configuration. This self-service approach allows the system to make highly efficient replication decisions without increasing operational complexity.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS9619539B2Automated document replication in a distributed computing system
Publication Date: 2017.04.11 VMWARE INC
  • US9619539B2 patent drawing
  • US9619539B2 patent drawing
  • US9619539B2 patent drawing

AI summary

In a method of automated document replication in a distributed computing system, a document at a first node of a distributed computing system is analyzed. Based on the analysis, it is determined whether the document has a multi-node affinity. In response to determining that the document has a multi-node affinity, at least one document is automatically replicated between nodes of the distributed computing system. The indicated nodes are indicated based on context of the multi-node affinity of the analyzed document.