Node-Based Data Store Management with Global Coherency

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current cloud storage systems lack global volume coherency and flexible data management, making them inefficient for arbitrary access and replication across nodes, which hampers robust and flexible storage solutions.

Innovation Solution

A node-based architecture that enables arbitrary access to any node for data representation and access, maintaining global virtual volume coherency and allowing asynchronous replication, with each node capable of caching data coherently and managing write transactions efficiently through overhead data management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a node-based architecture is implemented to enable arbitrary access to any node, then access flexibility and replication capability are improved, but system complexity and coordination overhead increase

Engineering Contradiction:

Improveaccess flexibilityVSAvoidsystem complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system is divided into independent nodes, each capable of autonomous data representation and access. Each node maintains local state and can serve as an access point, eliminating the need for a centralized coordination mechanism and reducing overall system complexity while preserving access flexibility

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Each node in the architecture is designed to perform multiple functions: data storage, data representation, and access point for other nodes. This multi-functionality reduces the need for specialized components and simplifies the overall system structure while enabling arbitrary access patterns

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Reliability

If global virtual volume coherency is maintained across all nodes, then data consistency is improved, but communication overhead and access latency increase

Engineering Contradiction:

Improvedata consistencyVSAvoidaccess latency

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

Each node maintains local virtual volume coherency independently rather than requiring global synchronization. Nodes cache data coherently at the local level, and this local coherency is sufficient for most operations, reducing communication overhead and access latency while maintaining data consistency

Inventive Principle:

Principle #3Local quality

Solution Approach 2:

Nodes perform preliminary data caching and validation before access operations. By pre-loading data into local caches and validating coherency in advance, the system reduces the need for real-time communication during data access, thereby lowering latency while maintaining consistency

Inventive Principle:

Principle #10Preliminary action

3Reliability

If asynchronous replication is implemented between nodes, then system robustness and fault tolerance are improved, but data synchronization complexity and overhead increase

Engineering Contradiction:

Improvefault toleranceVSAvoidsynchronization complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The system implements asynchronous replication by creating copies of data at remote nodes without requiring complex real-time synchronization protocols. Each node independently manages its local copies, and synchronization occurs periodically or on-demand, simplifying the overall synchronization complexity while maintaining fault tolerance

Inventive Principle:

Principle #26Copying

Solution Approach 2:

Each node autonomously manages its own data replication and synchronization without requiring centralized coordination. Nodes independently track their data state and perform replication operations as needed, reducing synchronization overhead and complexity while maintaining system robustness

Inventive Principle:

Principle #25Self-service

4Speed

If each node caches data coherently independently, then access speed and local performance are improved, but memory overhead and cache coordination difficulty increase

Engineering Contradiction:

Improveaccess speedVSAvoidmemory overhead

Core Design Contradiction:

SpeedVSQuantity of substance

Solution Approach 1:

Each node maintains a cache sized and optimized for its local access patterns rather than requiring a centralized cache that all nodes must coordinate with. This local caching strategy improves access speed for local operations while the distributed nature reduces total memory overhead compared to centralized approaches

Inventive Principle:

Principle #3Local quality

Solution Approach 2:

Nodes cache data proactively based on predicted access patterns rather than waiting for actual access requests. By caching data in advance based on locality principles, the system improves access speed while the selective caching approach (caching only frequently accessed data) keeps memory overhead manageable

Inventive Principle:

Principle #16Partial or excessive action

Data Source

PatentUS10498802B1Multi-node data store management

Publication Date: 2019.12.03 DATACORE SOFTWARE CORP

AI summary

A node based architecture that supports arbitrary access to any node in a system for data representation and access, while still providing virtual volume coherency that is global to all of the nodes in the system, and while providing underlying data management services that are also variously accessible from any node in the system.