Multi-Type CRDTs for Eventual Consistency Across Active-Active Databases

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional CRDTs struggle to handle multiple incompatible data types in geo-distributed active-active database systems, leading to data type conflicts and inconsistencies without segregating instances, and often require strong communication reliability assumptions.

Innovation Solution

A multi-type conflict-free replicated data type (CRDT) structure that supports multiple incompatible data types by using a priority sequence for internal data types and attributes, allowing for eventual consistency without segregating instances and assuming only ordered, eventual delivery on individual channels.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional CRDTs are used to handle multiple incompatible data types, then data type conflicts and inconsistencies occur, but segregating instances increases system complexity

Engineering Contradiction:

Improvedata consistencyVSAvoidsystem complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments data types into compatible and incompatible categories, allowing the CRDT to handle multiple incompatible data types internally while presenting a unified interface externally. This segmentation resolves conflicts by organizing data types hierarchically rather than requiring instance segregation.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The CRDT structure is designed to be universal by supporting multiple incompatible data types within a single instance through internal type management. This multi-functionality allows the same CRDT to handle different data types (e.g., strings, numbers, objects) without requiring separate instances for each type.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Ease of operation

If strong communication reliability assumptions are made, then conflict resolution is simplified, but system adaptability to various network conditions decreases

Engineering Contradiction:

Improveconflict resolution simplicityVSAvoidnetwork condition adaptability

Core Design Contradiction:

Ease of operationVSAdaptability or versatility

Solution Approach 1:

The CRDT performs self-service by automatically resolving conflicts between multiple incompatible data types through its internal type management mechanism. The system autonomously determines type compatibility and resolves conflicts without requiring external coordination or strong communication assumptions, adapting to various network conditions.

Inventive Principle:

Principle #25Self-service

3Reliability

If specific usage patterns are enforced to avoid data type conflicts, then data integrity is maintained, but ease of operation decreases

Engineering Contradiction:

Improvedata integrityVSAvoidusage flexibility

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The CRDT acts as an intermediary between multiple data types and the external system. It manages type compatibility internally through its multi-type structure, allowing users to operate with any data type without worrying about conflicts. The CRDT mediates type mismatches automatically, maintaining data integrity while providing usage flexibility.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS20250278398A1Method and system for eventual consistency of data types in geo-distributed active-active database systems

Publication Date: 2025.09.04 HUAWEI CLOUD COMPUTING TECHNOLOGIES CO LTD

AI summary

There is provide a method and system for eventual consistency of data types in geo-distributed active-active database systems. A multi-type conflict-free replicated data type (CRDT) structure is provided. The multi-type CRDT structure and method allow a geo-distributed active-active database system to reach eventual consistency on data type conflicts by supporting multiple incompatible data types.