Blockchain-as-a-Service Virtual Node Data Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Centralized databases face issues such as single points of failure, dependency on network connectivity, limited data access, and lack of redundancy, leading to potential data loss and management challenges.
Innovation Solution
A blockchain-as-a-service (Baas) provider manages virtual nodes to store and manage data, using blockchain technology to ensure data redundancy and accessibility through a decentralized system, where data is stored in a shared storage area and appended to a blockchain without the actual data, allowing for efficient data management and access.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If data is stored in a centralized database, then data management is easy and control is simplified, but the system has a single point of failure and lacks fault tolerance
Solution Approach 1:
The patent divides the centralized database into multiple decentralized nodes distributed across different locations. Each node stores copies of the data, eliminating the single point of failure while maintaining data accessibility. This segmentation transforms the monolithic centralized structure into a resilient distributed network.
Solution Approach 2:
The patent creates multiple copies of the data across different nodes in the decentralized network. Instead of storing data in a single location, identical copies are replicated across multiple independent nodes, ensuring that data remains accessible even if some nodes fail.
2Reliability
If data is stored in a centralized database, then network connectivity dependency is reduced, but access time increases with slower connections
Solution Approach 1:
The patent segments the centralized data storage into multiple distributed nodes geographically dispersed across the network. This segmentation allows users to access data from the nearest or most available node, reducing network latency and access time while maintaining reliability.
Solution Approach 2:
The patent adds a spatial dimension to data storage by distributing nodes across multiple locations rather than concentrating them in a single central location. This dimensional change enables parallel access paths and reduces network dependency by providing multiple routes to data.
3Quantity of substance
If data is stored in a centralized database, then data redundancy is minimized, but data loss is difficult to retrieve
Solution Approach 1:
The patent implements multiple copies of data across decentralized nodes, creating intentional redundancy. If data is lost or corrupted at one node, identical copies exist at other nodes, enabling automatic retrieval without manual intervention or complex backup restoration processes.
Solution Approach 2:
The patent prepares for potential data loss by pre-distributing copies of data across multiple nodes before any loss occurs. This beforehand cushioning ensures that redundancy is already in place, allowing immediate retrieval of lost data from surviving nodes without requiring manual backup operations.
4Reliability
If data is stored in a decentralized blockchain system, then fault tolerance and redundancy are improved, but system complexity increases
Solution Approach 1:
The patent implements a universal data structure and protocol that works across all decentralized nodes. This universality allows the same mechanisms to handle multiple functions including data storage, validation, and retrieval, reducing the need for node-specific complexity while maintaining fault tolerance.
Solution Approach 2:
The patent changes key parameters of the system by using cryptographic hashing and pointer references instead of storing complete data copies in each block. This parameter change reduces the complexity of data synchronization and validation across nodes while maintaining the integrity and fault tolerance of the decentralized system.
5Loss of time
If actual data is stored in blockchain blocks, then data accessibility is improved, but blockchain size and processing time increase significantly
Solution Approach 1:
The patent extracts the actual data from the blockchain blocks and stores it in separate external storage systems. Only pointers or references to this external data are stored in the blockchain, dramatically reducing blockchain size and processing time while maintaining data accessibility through the pointer references.
Solution Approach 2:
The patent introduces an intermediary layer between the blockchain and the actual data storage. This intermediary consists of pointers that reference external data locations, allowing the blockchain to maintain its integrity and immutability while avoiding the performance penalties of storing large amounts of actual data within blocks.
Data Source
AI summary
An example operation may include one or more of hosting a first virtual node in a blockchain-as-a-service (Baas) provider, hosting a second virtual node in the Baas provider, and controlling transmission of information between the first virtual node and the second virtual node along an internal signal path of the Baas provider, wherein the information corresponds to a block in a blockchain that includes an entry for the first and second virtual nodes.