Extensible Upgrade Service Automating Application Migration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional application management techniques are time-consuming, error-prone, and resource-intensive, particularly in legacy application migration and microservices architecture-based development, requiring significant efforts across multiple services and components.
Innovation Solution
The extensible upgrade and modification as a service (XuMaaS) system processes modifiers with a canonical structure to execute automated actions for application modification and migration, determining applicable modifiers across multiple applications and environments, and orchestrating these actions for efficient migration and upgrade.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If conventional application management techniques are used for legacy application migration, then application migration can be performed, but the process is time-consuming and resource-intensive
Solution Approach 1:
The system enables self-service automation where the modification orchestration service automatically performs dependency analysis, modifier selection, and application modification without requiring manual intervention. The service autonomously processes migration tasks by executing determined modifiers on target applications, thereby resolving the contradiction between migration capability and time consumption.
Solution Approach 2:
The patent replaces manual mechanical processes (manual dependency determination, manual component modification) with an automated computational system. The modification orchestration service uses algorithmic processing to analyze dependencies, select appropriate modifiers, and execute modifications, substituting human labor with automated mechanical-computational systems to improve productivity and reduce time loss.
2Adaptability or versatility
If conventional application management techniques are used for microservices migration, then similar changes can be applied across multiple services, but significant time and resources are required
Solution Approach 1:
The system implements universality through reusable modifiers that can be applied across multiple microservices and applications. A single modifier can be determined once and then repeatedly applied to various target applications, enabling the same modification operation to serve multiple purposes and contexts, thereby improving adaptability while reducing redundant development effort.
Solution Approach 2:
The system performs preliminary action by determining and preparing modifiers in advance before they are needed for actual application modification. The modification orchestration service pre-processes modification requirements, selects appropriate modifiers, and prepares them for execution, so that when multiple applications need similar changes, the work has already been done once and can be reused, significantly improving productivity.
3Ease of operation
If manual application modification techniques are used, then application changes can be made, but the process is error-prone
Solution Approach 1:
The system implements feedback mechanisms where the modification orchestration service continuously monitors the modification process, validates results, and adjusts its operations based on system responses. The service receives feedback from dependency analysis, modifier execution, and application state changes, using this information to correct errors and ensure accurate modifications, thereby improving reliability while maintaining ease of operation.
Data Source
AI summary
Methods, apparatus, and processor-readable storage media for implementing extensible upgrade and modification as a service are provided herein. An example computer-implemented method includes processing one or more modifiers, wherein each modifier includes an independent processing unit having a given canonical structure and is configured to execute one or more automated actions related to at least one of application modification and application migration; obtaining data pertaining to multiple applications across multiple computing environments; determining, based at least in part on processing at least a portion of the obtained data, at least one of the one or more modifiers applicable for use in executing at least one of the one or more automated actions in connection with at least a portion of the multiple applications; and executing the at least one of the one or more automated actions using the at least one determined modifier.


