Automated Application Migration via Macro-Service Refactoring

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for migrating applications from older to newer environments are time-consuming, labor-intensive, and often result in loss of logic or increased complexity, especially when moving to cloud platforms, due to the need for manual intervention and inadequate automation.

Innovation Solution

A system and method for automated application environment migration using a processor-based approach that assesses, re-factors, and re-platforms application code, utilizing AI for identifying macro-services, continuous integration and deployment frameworks, and security rule implementation to migrate applications with minimal manual input, ensuring business logic preservation and cost reduction.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If applications are migrated by completely reproducing the application in accordance with the newer environment, then the application can be adapted to the new environment, but the migration process becomes time-consuming and labor-intensive

Engineering Contradiction:
Improveapplication adaptability to newer environmentVSAvoidmigration time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent uses automated code generation to create copies of application code that are adapted to the target environment. The system generates migration scripts and refactored code automatically, rather than manually reproducing applications, thus reducing migration time while ensuring proper adaptation to the newer environment

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system performs preliminary assessment and analysis of the source application before migration. It evaluates the application architecture, identifies dependencies, and prepares migration plans in advance, which streamlines the actual migration process and reduces the time required for execution

Inventive Principle:
Principle #10Preliminary action

2Reliability

If manual migration processes are used to ensure logic preservation, then logic accuracy can be maintained, but the migration process becomes complex and requires significant manual intervention

Engineering Contradiction:
Improvelogic preservation accuracyVSAvoidmigration process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The migration system performs self-assessment and self-correction during the migration process. It automatically evaluates the source application, identifies potential logic issues, and applies appropriate transformation rules without requiring constant manual verification, thus maintaining logic accuracy while reducing process complexity

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system incorporates automated testing and validation mechanisms that provide feedback during migration. It verifies that business logic is preserved through automated test cases and comparison algorithms, ensuring reliability while reducing the need for complex manual verification processes

Inventive Principle:
Principle #23Feedback

3Productivity

If automated migration tools are used to reduce manual effort, then migration speed increases, but the ability to handle complex application logic and maintain quality standards decreases

Engineering Contradiction:
Improvemigration speedVSAvoidmigration quality standard
Core Design Contradiction:
ProductivityVSManufacturing precision

Solution Approach 1:

The patent replaces manual mechanical processes with automated intelligent systems. It uses AI-based code analysis, automated refactoring tools, and intelligent mapping algorithms to handle complex application logic, thereby maintaining high migration quality standards while achieving rapid automated migration

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The system dynamically adjusts migration parameters and transformation rules based on the specific characteristics of the source application. It modifies migration strategies, code generation templates, and testing parameters automatically, enabling high-speed automated migration while maintaining quality standards through adaptive parameter optimization

Inventive Principle:
Principle #35Parameter changes

4Loss of energy

If cloud migration is pursued to reduce costs and improve scalability, then total cost of ownership decreases, but the complexity of migrating existing applications to cloud platforms increases

Engineering Contradiction:
Improvetotal cost of ownershipVSAvoidcloud migration complexity
Core Design Contradiction:
Loss of energyVSDevice complexity

Solution Approach 1:

The migration system provides universal functionality that handles multiple migration scenarios and target cloud platforms through a single unified toolset. It supports various cloud environments (AWS, Azure, GCP) and application types with consistent automated processes, reducing the complexity associated with cloud migration while achieving cost savings

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentEP3872627B1System and method for application environment migration
Publication Date: 2024.05.22 HEXAWARE TECHNOLOGIES
  • EP3872627B1 patent drawingFigure 1
  • EP3872627B1 patent drawingFigure 2
  • EP3872627B1 patent drawingFigure 3

AI summary

A method of application environment migration assesses a source application code of a source application environment, ascertains a quantum change for migrating the source application code to a target application code and forecasts an assessment statistic (302) that provides at least one functional readiness (304) and a timeline (306) to complete the migration of the source application code. Further, scans the source application code for identifying a business logic and generates a re-factored code for the source application code by breaking the source application code into macro-services (426a, .., 426n) and repackaging the macro-services (426a, .., 426n) in accordance with the target application code while retaining the business logic. Thereby, updating components of the source application environment as per the forecasted assessment statistic (302) and the re-factored code, and migrating to the target application environment while re-platforming the updated components and the re-factored code of the source application environment.