Migration Gateway for Zero-Downtime Database Cluster Cutover

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for migrating strongly consistent distributed database clusters often result in downtime, disrupting database operations and compromising consistency due to the inability to maintain direct communication between source and destination environments.

Innovation Solution

A zero-downtime migration technique involving the use of a DNS service and a migration gateway to facilitate communication between source and destination database members, coupled with dynamic provisioning and deprovisioning of database members to maintain consensus and consistency, ensuring seamless transitions without downtime.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional migration methods are used to move distributed database clusters from source to destination environment, then the migration can be completed, but downtime occurs and database operations are disrupted

Engineering Contradiction:
Improvedatabase service availabilityVSAvoidmigration downtime
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent provisions destination database members in advance before the actual migration occurs. These destination members are prepared with the necessary infrastructure and configuration, allowing them to immediately take over database requests once the migration is initiated, thereby eliminating downtime.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces a migration gateway as an intermediary component that facilitates communication between source and destination database members during the migration process. This gateway enables seamless data synchronization and request routing, ensuring continuous database availability throughout the migration.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Manufacturing precision

If database members are updated with new images during migration, then the destination environment can be synchronized with the source, but processing database requests simultaneously may compromise consistency

Engineering Contradiction:
Improvedatabase consistencyVSAvoiddatabase request processing capability
Core Design Contradiction:
Manufacturing precisionVSProductivity

Solution Approach 1:

The patent segments the database cluster into multiple independent database members that can operate autonomously. This segmentation allows the cluster to maintain consensus through distributed agreement protocols, enabling some members to be updated while others continue processing requests, thus maintaining both consistency and productivity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements dynamic provisioning and deprovisioning of database members during migration. The system can dynamically adjust the number and state of database members based on migration progress, allowing flexible updates while maintaining the required quorum for consensus and continuous request processing.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS12547595B2Mechanism for zero downtime migration of strongly consistent distributed database clusters
Publication Date: 2026.02.10 ORACLE INT CORP
  • US12547595B2 patent drawing
  • US12547595B2 patent drawing
  • US12547595B2 patent drawing

AI summary

A distributed database service can be migrated from a source environment to a destination environment. The distributed database service can be associated with a database and database members. the source environment can include source database members such that each source database member includes a respective image of the database. Migrating the distributed database service can include provisioning a migration gateway in the source environment. Migrating the distributed database service can also include provisioning a domain name system service in the destination environment. Migrating the distributed database service can also include provisioning a first destination database member in the destination environment. While updating the first destination database member with a respective image of the database, the distributed database service can process a database request.