Selective Database Object Synchronization via Graph Snapshots

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current database systems face challenges in selectively synchronizing and managing incremental changes across different database instances, particularly in propagating destructive changes and ensuring data integrity, which is inefficient and resource-intensive.

Innovation Solution

A system and method for selective synchronization of database objects, involving the creation of snapshots of records, comparison with previous snapshots, and targeted updates, using graph configurations and boundary identifiers to manage and propagate incremental changes, allowing for selective deployment and reversion of database records.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If full clones or full updates of database instances are made, then data integrity and completeness are ensured, but computational resources and time consumption increase significantly

Engineering Contradiction:
Improvedata integrityVSAvoidcomputational resources
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent segments database records into object record sets grouped by object boundary identifiers, allowing selective synchronization of only modified sets rather than entire databases. This segmentation enables incremental updates that maintain data integrity while reducing computational resource consumption.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary actions by collecting and comparing object record sets before synchronization. Snapshots are taken and compared to identify only the modified record sets that need to be propagated, avoiding unnecessary processing of unchanged data.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If full clones or full updates of database instances are made, then data integrity and completeness are ensured, but synchronization time increases significantly

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

Solution Approach 1:

By dividing the database into manageable object record sets with unique object boundary identifiers, the system can synchronize only the segments that have changed, dramatically reducing synchronization time while preserving data integrity through structured comparison and selective propagation.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary collection and comparison of object record sets before synchronization. By pre-identifying which record sets are modified through comparison with previous snapshots, the system avoids time-consuming full database scans and only processes necessary changes.

Inventive Principle:
Principle #10Preliminary action

3Use of energy by moving object

If incremental changes are propagated selectively, then computational resources and time are reduced, but identifying and tracking modified records becomes more complex

Engineering Contradiction:
Improvecomputational resourcesVSAvoidsynchronization mechanism complexity
Core Design Contradiction:
Use of energy by moving objectVSDevice complexity

Solution Approach 1:

The patent introduces object boundary identifiers as unique segmentation keys that simplify the tracking of modified records. By organizing records into sets keyed by these identifiers, the system reduces the complexity of identifying changes to comparing discrete, well-defined record sets rather than navigating complex database relationships.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system uses feedback mechanisms where snapshots are compared with previous snapshots to automatically identify modified object record sets. This feedback loop provides clear information about what needs to be synchronized, simplifying the tracking complexity through systematic comparison results.

Inventive Principle:
Principle #23Feedback

4Productivity

If destructive changes are propagated to destination instances, then data updates are maintained, but data integrity requirements require accurate identification of impacted records

Engineering Contradiction:
Improvedata update efficiencyVSAvoidimpacted record identification accuracy
Core Design Contradiction:
ProductivityVSMeasurement precision

Solution Approach 1:

The system segments destructive changes into specific object record sets identified by object boundary identifiers. This segmentation enables precise tracking of which records are affected by destructive changes, allowing accurate identification of impacted records while maintaining efficient propagation of updates.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary comparison of object record sets before propagation to identify destructive changes in advance. By pre-comparing snapshots and identifying modified sets, the system ensures accurate tracking of impacted records while maintaining efficient update propagation.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11709862B2Selective synchronization of database objects
Publication Date: 2023.07.25 GRAV1TY INC
  • US11709862B2 patent drawing
  • US11709862B2 patent drawing
  • US11709862B2 patent drawing

AI summary

Implementations described herein relate to methods, systems, and computer-readable media to selectively synchronize database objects. In some implementations, a method includes receiving a request to synchronize records that include a corresponding root record and one or more connected records from a first database instance to a second database instance, wherein the request includes a specified graph configuration and an object boundary identifier; collecting the one or more records by traversing a corresponding graph configuration associated with each of the one or more root records; generating a snapshot that includes the one or more records into one or more object record sets based on a corresponding object boundary identifier associated with each of the one or more root records and the one or more connected records; publishing the snapshot to the second database instance; and updating the second database instance.