Cross-Regional Database Synchronization via Replicator Component

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Multi-regional active/active databases face challenges in real-time or near-real-time synchronization of data between regional server arrangements where multiple masters are not allowed to directly access and write to each other's databases, leading to inefficiencies and potential data redundancy.

Innovation Solution

Implementing a replicator component that cross-replicates data written in one regional server to a read replica in another region, ensuring synchronization without redundant copying back into the original database, and utilizing a data copy utility to write this data into the secondary database at predetermined cadences or when the replica is full.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If multiple masters are not allowed to directly access and write to each other's databases, then data consistency is maintained, but real-time or near-real-time synchronization cannot be achieved

Engineering Contradiction:

Improvedata consistencyVSAvoidsynchronization speed

Core Design Contradiction:

ReliabilityVSSpeed

Solution Approach 1:

The patent introduces a data copy utility as an intermediary component that receives data from a first database, processes it, and writes it to a second database. This mediator enables synchronization between databases that would otherwise not allow direct master-to-master access, resolving the contradiction by providing a controlled indirect path for data exchange while maintaining consistency.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The synchronization process is segmented into discrete operations: data identification, data copying, and conditional writing. The data copy utility operates in predetermined cadences or when the replica is full, breaking down the continuous synchronization requirement into manageable discrete steps that maintain consistency while enabling eventual near-real-time sync.

Inventive Principle:

Principle #1Segmentation

2Reliability

If data is copied back into the original database after replication, then synchronization is ensured, but redundant data copies are created

Engineering Contradiction:

ImprovesynchronizationVSAvoiddata redundancy

Core Design Contradiction:

ReliabilityVSLoss of substance

Solution Approach 1:

The patent applies partial action by selectively copying only certain data from the first database to the second database based on predetermined conditions. The data copy utility does not replicate all data unnecessarily, but instead performs targeted copying in predetermined cadences or when the replica is full, achieving synchronization while minimizing redundant data copies.

Inventive Principle:

Principle #16Partial or excessive action

Solution Approach 2:

The system changes the parameter of data copying frequency from continuous to predetermined cadences or event-driven (when replica is full). This parameter change optimizes the synchronization process by reducing unnecessary copying operations while still ensuring data consistency between databases.

Inventive Principle:

Principle #35Parameter changes

3Productivity

If regional databases operate independently, then equipment efficiency is maximized, but uninterrupted database access cannot be guaranteed during failures

Engineering Contradiction:

Improveequipment efficiencyVSAvoiduninterrupted access

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The patent establishes continuous data copying operations from the first database to the second database through the data copy utility. This continuous action ensures that even if one database fails, the other can continue to serve requests, guaranteeing uninterrupted database access while maintaining equipment efficiency through the asynchronous copying mechanism.

Inventive Principle:

Principle #20Continuity of useful action

Solution Approach 2:

The system prepares for potential failures by maintaining a secondary database that is continuously updated with copied data. This beforehand cushioning ensures that if the primary database fails, the secondary database is already prepared to take over, guaranteeing uninterrupted access without affecting the efficiency of the primary system during normal operation.

Inventive Principle:

Principle #11Beforehand cushioning (Prior cushioning)

Data Source

PatentUS10795913B2Synching and reading arrangements for multi-regional active/active databases

Publication Date: 2020.10.06 CAPITAL ONE SERVICES LLC

AI summary

Improvements enabling real-time or near-real-time synching of data of one region's DB with another region's DB, especially when server arrangements associated therewith do not allow multiple masters to access and write to their respective DBs. Further, the examples are directed to improvements enabling synching of data from one regional server arrangement to another and vice versa, without replicating a same write data redundantly back into the DB which had originally written such data.