Offline-Compatible Database Node Data Replication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing database systems face challenges in providing efficient offline support, particularly in scenarios where nodes within a database cluster lose connection, leading to time-consuming rebuilding processes and resource consumption.

Innovation Solution

The implementation of offline-compatible nodes that can perform operations such as data replication and CRUD operations independently while disconnected from the network, reconnecting and synchronizing data upon reconnection, reducing the need for extensive resource allocation and rebuilding.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If nodes are rebuilt from scratch after failure, then data consistency is restored, but time and resources are substantially consumed

Engineering Contradiction:
Improvedata consistencyVSAvoidrebuilding time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements preliminary action by maintaining pre-synchronized copies of data and application code in offline-compatible nodes before network disconnection occurs. When a node fails or disconnects, these pre-prepared resources enable immediate restoration without requiring time-consuming downloads or rebuilds from scratch, thus resolving the contradiction between data consistency and rebuilding time

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses copying by creating and maintaining duplicate copies of database information and application code across multiple nodes including offline-compatible nodes. These copies serve as immediate replacement resources when primary nodes fail, eliminating the need to rebuild from scratch and significantly reducing restoration time while maintaining data consistency

Inventive Principle:
Principle #26Copying

2Reliability

If nodes are rebuilt from scratch after failure, then system integrity is maintained, but resources are substantially consumed

Engineering Contradiction:
Improvesystem integrityVSAvoidresource consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent implements copying by maintaining duplicate copies of data and application code in offline-compatible nodes before network disconnection. When failures occur, these pre-existing copies enable immediate node restoration without requiring resource-intensive downloads or rebuilds from scratch, thus maintaining system integrity while substantially reducing resource consumption

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent applies preliminary action by pre-synchronizing and storing complete node images including data and application code in offline-compatible nodes before network issues occur. This preliminary preparation eliminates the need for resource-intensive rebuild operations later, reducing both time and resource consumption while preserving system integrity

Inventive Principle:
Principle #10Preliminary action

3Productivity

If nodes operate independently offline, then operational continuity is maintained, but data synchronization capability is lost

Engineering Contradiction:
Improveoperational continuityVSAvoiddata synchronization
Core Design Contradiction:
ProductivityVSLoss of information

Solution Approach 1:

The patent implements preliminary action by pre-synchronizing complete data sets and application code to offline-compatible nodes before network disconnection occurs. This allows nodes to operate independently with full functionality maintained, while the pre-stored synchronized data ensures no information loss occurs during offline operation

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses copying by creating and maintaining complete copies of database information and application code in offline-compatible nodes. These copies enable full operational continuity during network disconnection, and the copying mechanism itself preserves all data that would otherwise require network connectivity, thus maintaining both productivity and preventing information loss

Inventive Principle:
Principle #26Copying

Data Source

PatentEP4229521B1Offline support for a database cluster
Publication Date: 2024.07.24 MICROSOFT TECHNOLOGY LICENSING LLC
  • EP4229521B1 patent drawingFigure 1
  • EP4229521B1 patent drawingFigure 2
  • EP4229521B1 patent drawingFigure 3

AI summary

Techniques are described herein that are capable of providing offline support for a database cluster that includes online nodes and an offline-compatible node. For example, an operation may be performed with regard to information, which is stored by the offline-compatible node while the offline-compatible node is not connected to the online nodes via the network, based at least in part on the offline-compatible node being connected to the online nodes. In another example, an operation may be performed with regard to information, which is stored by any one or more of the online nodes while the offline-compatible node is not connected to the online nodes via the network, based at least in part on the offline-compatible node being connected to the online nodes.