Blockchain Node Snapshot Replication for Rapid Synchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing blockchain node management systems are time-consuming, labor-intensive, and costly due to the need for CSP-specific tools and skilled personnel, especially when synchronizing nodes across different compute and storage platforms.
Innovation Solution
A system and method for spinning up blockchain nodes using data snapshots that function independently of compute and storage platforms, utilizing a blockchain node management server, node synchronization automation module, downloader and uploader, and snapshot storage to facilitate faster data transfer and node synchronization.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If nodes are synchronized on compute and storage platforms using CSP-specific tools, then node synchronization can be achieved, but the process takes a relatively long time (measured in weeks)
Solution Approach 1:
The system creates compute and storage platforms beforehand with pre-configured snapshots of blockchain nodes. When a new node is needed, the system restores from the pre-created snapshot rather than performing full synchronization, dramatically reducing the time required to bring up new nodes.
Solution Approach 2:
The system uses snapshots as copies of blockchain node data stored on compute and storage platforms. These snapshots can be quickly restored to create new nodes without performing full data synchronization, thereby reducing synchronization time from weeks to minutes.
2Reliability
If CSP-specific tools are used for creating, managing, and restoring nodes, then platform-specific requirements can be met, but labor intensity and operational costs increase
Solution Approach 1:
The system employs a universal node management module that can operate across different compute and storage platforms (AWS, Azure, GCP) without requiring platform-specific tools. This single module handles node creation, management, and restoration universally, reducing operational complexity while maintaining compliance with various CSP requirements.
Solution Approach 2:
The system enables automated node creation and restoration through the universal module that automatically handles all necessary operations. The system can self-manage node provisioning by restoring from snapshots without requiring manual intervention or specialized knowledge of CSP-specific tools, thereby reducing labor intensity.
3Reliability
If full data synchronization is performed for new nodes, then data integrity is ensured, but the process is time-consuming and exceeds service level agreements
Solution Approach 1:
The system performs the time-consuming snapshot creation in advance during node maintenance windows. When a new node is deployed, the system simply restores the pre-created snapshot, which ensures data integrity while dramatically improving deployment speed from full synchronization to quick restoration.
Solution Approach 2:
Instead of performing full data synchronization, the system uses snapshots as efficient copies that capture the complete node state. Restoring these snapshots provides the same data integrity assurance as full synchronization but reduces the process time from weeks to minutes, meeting service level agreements.
Data Source
AI summary
The present disclosure relates to a system and method for synchronizing nodes and snapshot data, independent of cloud infrastructure. The system includes a blockchain node management server, a node synchronization automation module, and a cluster of synchronized blockchain nodes implemented on the cloud. The blockchain node management server generates a new node, and the node synchronization automation module, using an automation engine, configures the node, deploys the node onto the blockchain network, and synchronizes the node with other blockchain nodes. A blockchain node synchronizes with the node of the blockchain network, reflects change in data in a chain data disk, and a snapshot of the chain data disk is created. Snapshots of different nodes are synchronized, independent of the infrastructure environment.


