Migration Workbench for Refactoring SaaS Database Persistency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Migrating an existing customer base from a previous software product version to a new software product version is difficult, costly, and results in significant downtimes, posing a risk to the continued success of the software product during re-architecting processes.
Innovation Solution
A data migration architecture workbench (DMAW) that enables refactoring application persistency with early migration impact analysis, allowing for optimized migration planning and reduced downtime by assessing and adjusting database tables based on migration test results.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If re-architecting is performed to move to a new platform or restructure microservice layout, then the software product architecture is improved and cleaned up, but migration downtime is extended and migration cost increases
Solution Approach 1:
The system performs preliminary migration impact analysis during the development phase by simulating migration scenarios and calculating migration costs before actual deployment. This allows architects to evaluate different re-architecting options and their migration implications in advance, enabling better planning to minimize actual migration downtime.
Solution Approach 2:
Migration tests are executed during the development phase to generate migration cost assessments and identify potential issues before production migration. This preliminary testing enables optimization of migration strategies and reduces the time required for actual customer migration.
2Adaptability or versatility
If re-architecting is performed to move to a new platform or restructure microservice layout, then the software product architecture is improved and cleaned up, but migration cost increases
Solution Approach 1:
The system calculates migration costs during development by analyzing database table sizes, migration volumes, and resource requirements. This early cost assessment enables stakeholders to make informed decisions about re-architecting options and allocate resources appropriately, avoiding unexpected cost overruns during actual migration.
Solution Approach 2:
The system provides feedback on migration cost implications of architectural decisions during development. By monitoring migration volume weights and resource requirements, the system enables continuous optimization of the re-architecting plan to balance architectural improvements with migration cost constraints.
3Productivity
If database tables are adjusted to generate target database tables for new software product version, then the new software product version is created, but migration complexity increases
Solution Approach 1:
The system performs preliminary migration impact analysis by simulating database table migrations and calculating migration volumes before implementation. This allows the migration team to understand the complexity of transformations required and prepare appropriate migration strategies in advance.
Solution Approach 2:
The system introduces a migration assessment layer that mediates between source and target database schemas. This intermediary analysis layer evaluates migration scenarios, identifies complex transformations, and provides guidance for handling difficult migrations, thereby reducing overall migration complexity.
Data Source
AI summary
The disclosure generally describes methods, software, and systems for re-architecting an existing software product provided as a service. A user input specifying current databases used for an old software product version is received. The user input includes a definition of a target persistency layout including databases assigned for storing a new software product version, the old software product version including one or more database tables and the new software product version including an adjustment to the one or more database tables to generate one or more target database tables. Sizes of the one or more database tables are read from a catalog of a database. A migration assessment of the new software product version is generated based on the sizes of the one or more database tables. A migration test of the one or more database tables is executed using the migration assessment to generate migration test results. An updated adjustment to the one or more database tables is provided based on the migration test results.