Distributed Datastore State-Based Location

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing distributed datastore systems face challenges such as significant overhead at core control components, limited scalability, security concerns due to centralized control, and vulnerability to central points of failure and malicious attacks.

Innovation Solution

A state-based distributed datastore system that determines a data unit identifier based on a data operation request, retrieves system state data, and identifies a distributed datastore satisfying a predefined condition to store data, thereby distributing data storage and improving scalability and security.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If all data requests are processed through a core control component, then centralized security control is achieved, but system overhead increases and scalability is limited

Engineering Contradiction:

Improvesecurity controlVSAvoidsystem overhead

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the centralized control architecture into distributed control nodes. Each node independently manages data requests using locally stored system state data, eliminating the single point of overhead at the core control component while maintaining security through distributed validation of data location information.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent extracts the system state data from the core control component and stores it locally at distributed data nodes. This extraction removes the bottleneck of centralized processing while preserving the security function, as each node can independently verify data locations using its local state information.

Inventive Principle:

Principle #2Taking out (Extraction)

2Loss of information

If a core control component stores a list of stored retrievable data objects, then data location tracking is enabled, but a central point of failure and vulnerability is created

Engineering Contradiction:

Improvedata location trackingVSAvoidcentral point of failure

Core Design Contradiction:

Loss of informationVSReliability

Solution Approach 1:

The patent segments the centralized data location registry into distributed data location information stored at multiple independent nodes. Each node maintains local knowledge of data locations relevant to its jurisdiction, eliminating the single point of failure while preserving complete data location tracking capability through the collective knowledge of the distributed network.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent implements local quality by allowing each distributed node to store and process data location information locally rather than relying on a centralized registry. This distributes the critical function of data location tracking across multiple locations, improving reliability while maintaining the ability to track all data objects in the system.

Inventive Principle:

Principle #3Local quality

3Adaptability or versatility

If multiple services use a common core control component, then resource sharing is achieved, but security is compromised when services are owned by different entities

Engineering Contradiction:

Improveresource sharingVSAvoidsecurity

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent segments the common control component into multiple independent control nodes, each serving specific services or entities. This allows resource sharing across the distributed network while maintaining security boundaries, as each node independently validates and enforces access controls for its designated services without exposing other entities' data.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces distributed data location information as an intermediary layer between services and storage nodes. This intermediary enables resource sharing by allowing services to query and access data across the network while maintaining security through validated, policy-based access control enforced at each distributed node rather than a single shared control point.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS12242494B2Distributed datastores with state-based data location

Publication Date: 2025.03.04 LUCIANO CHARLES J

AI summary

A method of operating on a data unit stored in a distributed datastore system is provided. The method includes determining, based on a data operation request specifying data stored in the distributed datastore system, a data unit identifier associated with the specified data; retrieving system state data representing a state of the distributed datastore system at a time associated with an initial generation of the data unit identifier; determining, based on the data operation request and the system state data, a distributed datastore satisfying a predefined datastore condition, wherein the predefined datastore condition is based on availability of the distributed datastore to store the data at the first time; and transmitting a query to the distributed datastore to determine whether a data unit generated from the data is stored on the distributed datastore, based on satisfaction of the predefined datastore condition by the distributed datastore.