Database Migration with Dual-Store No-Downtime Operation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing database migration techniques in cloud-based services result in downtime, disrupting customer processes during the transition from an initial data store to a target data store.
Innovation Solution
Implementing a distributed computing system with an initial and target data store, where a portion of the data is migrated while ensuring the primary data store status is open, and new data entities are created only in the initial data store if the key is not present in the target store, allowing seamless transitions without downtime.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If all data is migrated from the initial data store to the target data store, then data completeness is improved, but system downtime increases
Solution Approach 1:
The patent segments the data migration process by maintaining two data stores (initial and target) simultaneously and migrating data in portions rather than all at once. The system divides the migration into phases where different data entities can be migrated independently, allowing the process to continue without complete system downtime.
Solution Approach 2:
The patent implements preliminary actions by setting up the target data store before migration begins and pre-configuring the dual-data-store architecture. This allows the system to have the target store ready and operational before data migration completes, preventing downtime rather than reacting to it after migration starts.
2Ease of manufacture
If data migration is performed traditionally, then data store transition is completed, but customer process functionality is disrupted
Solution Approach 1:
The patent introduces an intermediary mechanism by maintaining both the initial and target data stores simultaneously during migration. This dual-store architecture acts as a mediator that allows customer processes to continue accessing data through the initial store while migration occurs in the background, then transitions to the target store without disruption.
Solution Approach 2:
The patent changes the operational parameters of the data store system by allowing both stores to coexist with different statuses (open/closed, primary/secondary). This enables flexible control where the initial store remains operational for customer processes while the target store is prepared and gradually populated, then swapped without service interruption.
3Speed
If the entire data set is migrated at once, then migration speed is improved, but system complexity increases
Solution Approach 1:
The patent segments the data set into different entities and portions that can be migrated independently rather than moving the entire data set as one unit. This segmentation allows parallel migration of different data portions, maintaining speed while reducing the complexity of managing a single large migration operation.
Data Source
AI summary
Techniques for enabling efficient data migration between data stores with no downtime are disclosed. A distributed computing system can be implemented with an initial data store and a target data store. During the migration of a portion of the data from the initial data store to the target data store, the distributed computing system can receive requests to create data entities or launch workflow instances at the data stores. The system can determine whether the initial data store or the target data store has been designated the primary data store for handling the requests. The system can also determine whether the initial data store or the target data store contain a key associated with the request. If the key is present in either of the data stores, the system may abort the creation of the data entity.