Share Object Replication Across Remote Deployments for Low-Latency Data Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data sharing methods are cumbersome, slow, and inefficient, particularly for smaller entities, as they require data copying and transfer, lack control over data usage, and introduce latency, making it difficult for smaller entities to access valuable data sets from larger corporations.

Innovation Solution

A data exchange platform using cloud computing services allows data providers to create share objects that grant access without copying data, enabling secure and scalable sharing through cloud-based replication of share objects across remote deployments, reducing manual operations and errors.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If data is copied and transferred using existing methods, then data sharing is achieved, but the process becomes cumbersome and slow

Engineering Contradiction:
Improvedata sharing efficiencyVSAvoiddata transfer time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent uses cloud-based replication to create copies of share objects across multiple remote deployments. Instead of transferring actual data, the system replicates metadata and access permissions, allowing simultaneous access to the same data source without physical data movement. This eliminates the time-consuming data copying process while maintaining data sharing functionality.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent introduces a cloud-based data exchange platform as an intermediary between data providers and consumers. This platform manages share objects, handles replication across remote deployments, and coordinates access permissions. By acting as a mediator, it eliminates direct data transfer between parties, reducing transfer time and complexity while maintaining efficient data sharing.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If data is transferred to enable sharing, then access is provided, but control over data usage is lost

Engineering Contradiction:
Improvedata accessVSAvoiddata usage control
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent extracts the control mechanism from the data itself by separating data access permissions from the actual data. Share objects contain only metadata and access permissions, not the actual data. This allows the data provider to maintain control over usage policies while enabling easy access for consumers, as the control logic is embedded in the share object metadata rather than requiring data transfer with embedded restrictions.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent implements a feedback mechanism where the cloud platform continuously monitors and enforces data usage policies defined in share objects. When data is accessed through replicated share objects, the system verifies permissions and logs usage, providing real-time feedback to ensure compliance with the data provider's control requirements. This maintains reliability of data usage control while enabling easy access.

Inventive Principle:
Principle #23Feedback

3Adaptability or versatility

If manual data sharing operations are performed, then data exchange is achieved, but errors increase and scalability decreases

Engineering Contradiction:
Improvedata sharing scalabilityVSAvoidmanual operations complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements self-service automation where the cloud-based platform automatically replicates share objects across remote deployments without requiring manual intervention. When a data provider creates a share object, the system automatically propagates it to all connected remote deployments, manages permissions, and handles updates. This eliminates complex manual operations while enabling scalable data sharing across numerous deployments simultaneously.

Inventive Principle:
Principle #25Self-service

4Ease of operation

If data is transferred between remote deployments, then sharing is enabled, but latency is introduced

Engineering Contradiction:
Improvedata accessibilityVSAvoiddata access speed
Core Design Contradiction:
Ease of operationVSSpeed

Solution Approach 1:

The patent performs preliminary actions by pre-establishing replicated share objects in all remote deployments before data access is needed. The metadata and access permissions are replicated in advance to each location, so when data access is required, no transfer latency occurs. The share objects are already locally available at each remote deployment, enabling immediate data access while maintaining centralized control through the cloud platform.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12591550B2Share replication between remote deployments
Publication Date: 2026.03.31 SNOWFLAKE INC
  • US12591550B2 patent drawing
  • US12591550B2 patent drawing
  • US12591550B2 patent drawing

AI summary

Provided herein are systems and methods for replicating share objects to remote deployments. An example method includes creating a share object for a first deployment of a data sharing platform. The share object includes share object metadata that describes access privileges in the first deployment. The method also includes creating, in a second deployment of the data sharing platform, a replica of the share object. The replica determines access privileges in the second deployment. The method also includes receiving, at the first deployment, a refresh message from the second deployment. The method also includes, in response to receiving the refresh message, transmitting the share object metadata from the first deployment to the second deployment and updating, by a processing device, the replica based on the share object metadata.