Gateway Client Migration Control for Continuous Database Service
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional database migration schemes cause disruptions and prolonged outages by disconnecting electronic connections to both source and target databases, leading to delays and resource-intensive reconnections, which affect the availability of electronic data and services.
Innovation Solution
A gateway client maintains connections to both the source and target databases during migration, managing read and write operations to minimize disruptions and conserve resources by pausing operations temporarily and resuming them gradually.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If electronic connections are disconnected during database migration, then data can be migrated from source to target database, but service disruptions occur and reconnections are required
Solution Approach 1:
The patent introduces a proxy server as an intermediary component that maintains continuous electronic connections with both the source database and target database. The proxy server acts as a mediator that redirects connection requests during migration, allowing applications to access the target database through the proxy without breaking existing connections. This resolves the contradiction by enabling data migration while maintaining service availability through the intermediary proxy layer.
Solution Approach 2:
The patent implements preliminary actions by establishing a proxy server before migration begins and pre-configuring it with connection information for both source and target databases. The proxy server is prepared in advance to handle connection redirection, ensuring that when migration occurs, connections can be seamlessly maintained or redirected without service disruption. This preliminary preparation eliminates migration downtime.
2Reliability
If electronic connections are maintained during migration, then service availability is preserved, but connection management complexity increases
Solution Approach 1:
The proxy server serves as a centralized intermediary that simplifies connection management during migration. Instead of requiring complex coordination between multiple components to maintain connections, the proxy server single-handedly manages all connection requests, redirects, and migrations. This intermediary approach reduces overall system complexity despite maintaining continuous connections.
Solution Approach 2:
The proxy server is designed as a universal component that performs multiple functions: maintaining connections, redirecting traffic, coordinating migration, and managing both source and target database access. This multi-functional design consolidates complexity into a single component rather than distributing it across multiple specialized components, making the system easier to manage.
3Productivity
If reconnections are performed after migration, then resources are reallocated, but time is lost and services are disrupted
Solution Approach 1:
The patent ensures continuity of useful action by maintaining electronic connections open throughout the entire migration process. The proxy server keeps connections active with both source and target databases, allowing data access to continue uninterrupted during migration. This eliminates the need for time-consuming reconnections after migration, as connections are never broken in the first place.
Solution Approach 2:
The proxy server as an intermediary enables continuous resource allocation without interruption. It manages the transition of resource usage from source to target database seamlessly, allowing applications to continue accessing data through the proxy while the underlying data location changes. This eliminates downtime and service disruptions associated with resource reallocation.
Data Source
AI summary
A source database and a target database are accessed. The source database contains data to be migrated over to the target database. The read operations from the target database and the write operations to the target database are ceased, while the read operations from the source database and the write operations to the source database are maintained. The data from the source database is replicated to the target database. During the replication, the read operations from the source database are maintained but the write operations to the source database are ceased, while the read operations from the target database and the write operations to the target database are also ceased. After the replication has been completed, the read operations from the source database and the write operations to the source database are ceased. The read operations from the target database and the write operations to the target database are resumed.