Distributed Shared-Data Database Cache Consistency via Selective Timestamps

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Maintaining data consistency across decentralized nodes in distributed databases is challenging due to network latency, hardware issues, and concurrent data access, leading to discrepancies and performance slowdowns when striving for strong consistency.

Innovation Solution

A method involving nodes in a distributed database requesting and managing latest timestamps from other nodes to update or invalidate their caches, ensuring data consistency by reading values from either the cache or storage based on these timestamps, without requiring centralized caching or client modifications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If strong consistency is maintained across all nodes, then data accuracy is improved, but system performance deteriorates

Engineering Contradiction:
Improvedata consistencyVSAvoidsystem performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent applies partial action by requesting timestamps only from nodes that have performed transactions, rather than all nodes. The receiving node identifies which nodes have latest timestamps ahead of its own and requests timestamps only from those specific nodes, reducing unnecessary communication overhead while maintaining consistency where needed.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

Each node independently manages its own cache and determines which timestamps to request based on its own transaction history. The receiving node autonomously identifies nodes with ahead timestamps and requests only those specific timestamps without needing centralized coordination, enabling self-service consistency maintenance.

Inventive Principle:
Principle #25Self-service

2Reliability

If centralized caching is used to maintain consistency, then data accuracy is improved, but scalability deteriorates

Engineering Contradiction:
Improvedata consistencyVSAvoidscalability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent segments the centralized caching function into distributed cache management at each node. Instead of one central cache, each node maintains its own cache independently, and consistency is achieved through selective timestamp requests between nodes, eliminating the scalability bottleneck of centralized caching.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Timestamps serve as intermediaries that carry consistency information between nodes. Rather than nodes directly coordinating cache updates, they exchange timestamp information that mediates the consistency protocol, allowing decentralized cache management while maintaining global consistency.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If frequent timestamp requests are sent to all nodes, then data consistency is improved, but network overhead increases

Engineering Contradiction:
Improvedata consistencyVSAvoidnetwork overhead
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent applies local quality by customizing timestamp requests based on the receiving node's specific situation. Each node determines which external nodes have timestamps ahead of its own and requests only from those nodes, rather than uniformly requesting from all nodes, reducing network traffic proportionally to the actual consistency needs.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS20250225123A1Systems and methods for global consistency in distributed shared-data databases
Publication Date: 2025.07.10 HUAWEI CLOUD COMPUTING TECHNOLOGIES CO LTD
  • US20250225123A1 patent drawing
  • US20250225123A1 patent drawing
  • US20250225123A1 patent drawing

AI summary

Apparatus, systems, and methods for global consistency in distributed shared-data databases may be provided. According to an aspect a method may be provided for ensuring strong consistency in data retrieval. The method includes receiving, by a receiving node of a database, a query for a value of a data item in the database. The method may further include, requesting, by the receiving node, from each node of the plurality of nodes a latest timestamp corresponding to a latest transaction. The method may further include receiving, by the receiving node from said each node of the plurality of nodes, the latest timestamp. The method may further include managing, by the receiving node, a cache of the receiving node based on said each received latest timestamp. The method may further include reading, by the receiving node, the value of the data item.