Blockchain Hot Cold Asset Storage for Database Bottlenecks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Centralized databases face issues such as single points of failure, high dependency on network connectivity, limited access due to data redundancy, and increased resource consumption with large shared ledgers, leading to performance bottlenecks and increased operational costs.

Innovation Solution

Implementing a blockchain network with a shared ledger that utilizes hot and cold asset storage repositories, where hot assets are cached for fast access and cold assets are stored with pointers in the shared ledger, reducing data duplication and resource usage through asset classification rules.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If a centralized database stores all data at a single location, then data redundancy is minimized and security control is simplified, but the system becomes highly dependent on network connectivity and creates performance bottlenecks during high traffic

Engineering Contradiction:
Improvedata storage managementVSAvoiddatabase access speed
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The patent segments the centralized database into multiple distributed nodes across a blockchain network. Each node maintains a copy of the shared ledger, eliminating the single-point bottleneck while preserving data consistency through cryptographic hashing and consensus mechanisms. This segmentation allows parallel access from multiple locations simultaneously.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent transitions from a single-dimensional centralized storage model to a multi-dimensional distributed network architecture. Data is replicated across multiple spatial dimensions (different nodes) while maintaining logical consistency through the blockchain's immutable ledger structure, enabling access from multiple dimensions simultaneously without conflict.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Quantity of substance

If a centralized database maintains a single copy of data, then storage space is optimized, but data loss is difficult to retrieve and requires manual operation from back-up storage

Engineering Contradiction:
Improvedata storage spaceVSAvoiddata recovery capability
Core Design Contradiction:
Quantity of substanceVSReliability

Solution Approach 1:

The patent implements automatic copying of data across multiple distributed nodes in the blockchain network. Each node maintains an identical copy of the shared ledger through cryptographic verification, eliminating the need for manual backup operations. If data is lost or corrupted at one node, identical copies exist at other nodes for immediate recovery.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent establishes redundant data copies across multiple nodes before any data loss can occur. This proactive duplication creates a cushion against potential failures, ensuring that data recovery is automatic and instantaneous rather than requiring manual intervention after loss has occurred.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

3Reliability

If a blockchain network stores complete copies of large shared ledgers at each node, then data access is decentralized and reliable, but resource consumption increases and performance bottlenecks occur

Engineering Contradiction:
Improvedata access reliabilityVSAvoidnode resource consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent extracts only the essential cryptographic elements (hashes, merkle roots, transaction signatures) from the complete blockchain ledger and stores these condensed representations at each node. The full transaction details are retained in the immutable blockchain history, allowing nodes to verify data integrity without storing exhaustive copies of all historical data, significantly reducing resource consumption.

Inventive Principle:
Principle #2Taking out (Extraction)

4Adaptability or versatility

If a centralized database experiences high traffic, then more users can access data simultaneously, but bottlenecks occur and response time increases

Engineering Contradiction:
Improveconcurrent access capabilityVSAvoiddatabase response time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent segments the monolithic centralized database into multiple independent distributed nodes that can process transactions in parallel. Each node independently validates and processes transactions from the shared ledger, eliminating the single-point bottleneck and enabling linear scaling of concurrent access capacity as more nodes join the network.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent fundamentally changes the system parameter from centralized single-point processing to distributed parallel processing across multiple nodes. This parameter change transforms the scalability characteristic, allowing the system to handle increasing traffic loads by simply adding more nodes to the network rather than upgrading a single central server.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS11200260B2Database asset fulfillment chaincode deployment
Publication Date: 2021.12.14 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US11200260B2 patent drawing
  • US11200260B2 patent drawing
  • US11200260B2 patent drawing

AI summary

An example operation may include one or more of receiving, by a blockchain node or peer, a deploy chaincode blockchain transaction, and in response establishing a cold asset storage repository comprising pointers to each of the assets of a blockchain stored in a shared ledger, each of the assets comprising a key-value pair, establishing a hot asset storage repository of predetermined size and configured to store a subset of the assets of the blockchain, and configuring asset classification rules to organize hot asset storage and cold asset storage.