Cross-Ontology Multi-Master Replication for Dynamic Data Consistency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Multi-master database systems face challenges in data replication due to rigid fixed ontologies, which limit flexibility and require human intervention to resolve conflicts, especially in dynamic data processing environments like intelligence analysis.

Innovation Solution

Implementing cross-ontology multi-master replication by using an ontology map to map data types and database changes between sites with different ontologies, allowing for asynchronous replication and maintaining data consistency without requiring a common ontology.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Stability of the object's composition

If a fixed ontology is used in multi-master database systems, then data structure consistency is maintained, but system flexibility and adaptability to dynamic data processing requirements deteriorate

Engineering Contradiction:
Improvedata structure consistencyVSAvoidsystem flexibility
Core Design Contradiction:
Stability of the object's compositionVSAdaptability or versatility

Solution Approach 1:

The patent implements dynamic ontology evolution by allowing ontologies to change over time at different database sites. The system supports ontology versioning where sites can evolve their ontologies independently, and changes are propagated asynchronously to other sites, enabling the system to adapt to dynamic data processing requirements while maintaining operational stability

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent segments the ontology into versioned components that can be independently managed at different database sites. Each site can have its own ontology version, and the system manages multiple ontology versions simultaneously, allowing flexibility at the segment level while maintaining overall system consistency through version control

Inventive Principle:
Principle #1Segmentation

2Reliability

If asynchronous replication is used, then system availability is improved, but conflict resolution complexity and human intervention requirements increase

Engineering Contradiction:
Improvesystem availabilityVSAvoidconflict resolution complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements automated conflict resolution through feedback mechanisms that detect conflicts between concurrent changes and automatically resolve them using predefined rules. The system monitors replication conflicts, applies resolution strategies, and propagates resolved changes without requiring human intervention, thereby reducing complexity while maintaining high availability

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system performs self-service conflict resolution by automatically detecting, analyzing, and resolving conflicts between concurrent database changes from different sites. The automated resolution process eliminates the need for human intervention in most conflict scenarios, reducing operational complexity while preserving system availability

Inventive Principle:
Principle #25Self-service

3Adaptability or versatility

If ontology changes are allowed at one database site, then adaptability is improved, but data replication consistency and system stability deteriorate

Engineering Contradiction:
Improveontology flexibilityVSAvoiddata replication consistency
Core Design Contradiction:
Adaptability or versatilityVSStability of the object's composition

Solution Approach 1:

The patent implements preliminary action by pre-defining ontology versioning schemes and change propagation rules before ontology modifications occur. When ontology changes are made at one site, the system has predetermined mechanisms in place to version the ontology, notify other sites, and propagate changes asynchronously, maintaining consistency while allowing flexibility

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary ontology versioning mechanism that mediates between different database site ontologies. This intermediary layer manages ontology changes, versions, and propagation, allowing one site to change its ontology while maintaining replication consistency across the distributed system through controlled change propagation

Inventive Principle:
Principle #24Intermediary (Mediator)

4Stability of the object's composition

If synchronous replication is used, then data consistency is improved, but system availability and flexibility to handle unavailable databases deteriorate

Engineering Contradiction:
Improvedata consistencyVSAvoidsystem availability
Core Design Contradiction:
Stability of the object's compositionVSReliability

Solution Approach 1:

The patent implements dynamic replication by allowing the system to switch between synchronous and asynchronous replication modes based on availability requirements. When all sites are available, synchronous replication ensures strong consistency; when sites become unavailable, the system dynamically transitions to asynchronous replication with queuing, maintaining availability while preserving consistency guarantees

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS11693877B2Cross-ontology multi-master replication
Publication Date: 2023.07.04 PALANTIR TECHNOLOGIES INC
  • US11693877B2 patent drawing
  • US11693877B2 patent drawing
  • US11693877B2 patent drawing

AI summary

A system and method providing cross-ontology multi-master replication is described. In a first embodiment a method for cross-ontology multi-master replication comprising the steps of: storing a database change comprising a property value, the property value having an exporting site property type as defined in an exporting site ontology for an exporting site; using an ontology map to map the exporting site property type to an importing site property type defined by an importing site ontology for an importing site; transforming the property value to an intermediate property value based on the importing site property type; transforming the intermediate property value to a first round-trip value based on the exporting site property type; and determining whether to export the database change to the importing site based at least in part on a comparison between the property value and the first round-trip value.