Share-Based Database Replication via Dependency Graph Analysis

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing database replication systems face challenges with high costs and latency due to the replication of entire databases across networks, which is inefficient and resource-intensive.

Innovation Solution

Implementing share-based database replication, which filters out unnecessary objects and replicates only the relevant portions of the database, reducing replication costs and latency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If entire database is replicated across network regions, then data safety and accessibility are improved, but replication cost and latency increase

Engineering Contradiction:
Improvedata safetyVSAvoidreplication cost
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent extracts and replicates only the necessary share objects and their dependencies rather than the entire database. The system identifies and replicates only the minimal set of database objects required to satisfy the share permissions, eliminating unnecessary data replication and reducing network costs while maintaining data safety.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent segments the database replication process into identifying share objects, determining their dependencies, and replicating only those specific objects. This segmentation allows selective replication of necessary data portions while excluding unnecessary data, thereby reducing replication costs and improving efficiency.

Inventive Principle:
Principle #1Segmentation

2Reliability

If entire database is replicated across network regions, then data safety and accessibility are improved, but replication latency increases

Engineering Contradiction:
Improvedata accessibilityVSAvoidreplication latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent extracts only the essential share objects and their dependencies for replication, excluding unnecessary database objects. This extraction approach reduces the volume of data to be replicated across network regions, thereby decreasing replication latency while ensuring that all necessary data for accessibility is present.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent performs preliminary analysis to identify share objects and their dependencies before replication begins. By determining the minimal replication set in advance, the system avoids unnecessary data transmission and reduces replication latency while maintaining complete data accessibility for the share.

Inventive Principle:
Principle #10Preliminary action

3Loss of energy

If selective replication of database portions is implemented, then replication cost and latency are reduced, but system complexity increases

Engineering Contradiction:
Improvereplication costVSAvoidsystem complexity
Core Design Contradiction:
Loss of energyVSDevice complexity

Solution Approach 1:

The system automatically identifies share objects, determines their dependencies, and selects what needs to be replicated without manual intervention. This self-service approach to selective replication reduces the perceived complexity for users while the underlying system handles the complex logic of determining minimal replication sets.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system uses feedback from share permission definitions to automatically determine which database objects need replication. By monitoring share object definitions and their dependencies, the system dynamically adjusts the replication set, making the complexity manageable through automated feedback-driven decision making.

Inventive Principle:
Principle #23Feedback

4Productivity

If selective replication of database portions is implemented, then replication efficiency is improved, but measurement and detection difficulty increases

Engineering Contradiction:
Improvereplication efficiencyVSAvoiddependency tracking
Core Design Contradiction:
ProductivityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent performs preliminary detection of share objects and their dependencies before replication begins. By establishing the replication set in advance through automated dependency analysis, the system improves replication efficiency while managing the complexity of dependency tracking through upfront detection rather than during the replication process.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12222828B2Share-based replication
Publication Date: 2025.02.11 SNOWFLAKE INC
  • US12222828B2 patent drawing
  • US12222828B2 patent drawing
  • US12222828B2 patent drawing

AI summary

The subject technology determines a set of share objects in a replication group. The subject technology, for each object from the set of share objects, determines a set of permissions for a set of objects of databases that has been granted to each share object from the replication group. The subject technology, for each permission from the set of permissions, determines a set of dependencies, the set of dependencies comprising a second set of objects. The subject technology generates a graph structure based at least in part on the set of share objects, the set of permissions, and the set of dependencies. The subject technology traverses at least a portion of the graph structure to determine a final set of dependencies for replication. The subject technology performs a replication process based at least in part on the final set of dependencies.