Database Migration via Intermediate Cloud for Schema Mismatch
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Different cloud deployments, such as public and FedRAMP-compliant clouds, often have mismatched database schema update rates, leading to undesirable schema mismatches during database migration between them.
Innovation Solution
Migrating databases through an intermediate cloud deployment that freezes schema updates until the destination cloud's schema catches up, ensuring both databases match before final migration.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If databases are migrated directly between cloud deployments with different schema update rates, then migration speed is improved, but schema mismatch occurs causing data integrity issues
Solution Approach 1:
The patent introduces an intermediate cloud deployment as a mediator between the source and destination cloud deployments. This intermediate deployment has a frozen schema that acts as a stable reference point, allowing databases to be migrated through a controlled transformation process rather than directly between incompatible schemas, thus resolving the contradiction between migration speed and data integrity
Solution Approach 2:
The patent applies preliminary action by freezing the schema at the intermediate deployment before migration occurs. This preliminary schema stabilization ensures that all schema changes are resolved in advance, allowing the actual migration to proceed quickly without encountering schema mismatches, thereby achieving both speed and reliability
2Adaptability or versatility
If schema updates are continued during migration, then database functionality is maintained, but schema mismatch increases between source and destination clouds
Solution Approach 1:
The patent segments the migration process into distinct phases: a pre-migration phase where the schema is frozen at the intermediate deployment, and a post-migration phase where the destination cloud's schema is updated. This segmentation allows database functionality to be maintained during the frozen phase while ensuring schema compatibility before the final migration, resolving the contradiction between adaptability and precision
3Reliability
If an intermediate cloud deployment is used to freeze schema, then schema mismatch is eliminated, but migration complexity increases
Solution Approach 1:
The patent uses copying by creating a frozen schema copy at the intermediate deployment. This copy serves as a stable template that can be applied to multiple databases during migration, simplifying the complex task of schema alignment across different cloud deployments while ensuring reliable schema matching, thus resolving the contradiction between reliability and complexity
Data Source
AI summary
Methods, systems, and devices for data management are described. A first data source may be identified to move from a source cloud deployment (that operates in accordance with a first release cadence for updating database schema) to a destination cloud deployment (that operates in accordance with second, different release cadence for updating database schema). The first source database is then migrated from the source cloud deployment to an intermediate cloud deployment hosted on the source cloud deployments that allows the schema of the first data source to remain unchanged for a duration of time that the first data source is hosted on the intermediate cloud deployment. The database schema associated with the first data source is then updated to an updated (most recent) database schema in accordance with the second release cadence of the destination cloud deployment, and migrated from the intermediate cloud deployment to the destination cloud deployment.