Wrapper Libraries for Legacy Application Cloud Migration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Legacy software applications are difficult and costly to migrate to cloud computing environments due to their serial, linear architecture, requiring significant re-factoring and re-writing, which hinders businesses from leveraging cloud benefits like parallel processing and distributed computing.
Innovation Solution
The neuron platform uses wrapper libraries to encapsulate legacy applications, enabling them to operate within a distributed, parallel processing environment, allowing seamless integration with cloud infrastructure for high availability and scalability without extensive re-coding.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If legacy applications are migrated to cloud computing environment through re-factoring and re-writing, then the application can achieve parallel processing and distributed computing capabilities, but the migration cost and time will significantly increase
Solution Approach 1:
The patent introduces a wrapper library as an intermediary layer between the legacy application and the cloud computing environment. This wrapper handles parallel processing coordination, distributed computing management, and cloud infrastructure integration without requiring modifications to the legacy application's core code, thus enabling parallel processing capabilities while avoiding extensive re-factoring time
Solution Approach 2:
The patent segments the migration process into two independent parts: the legacy application code remains unchanged while the wrapper library is separately developed and configured. This segmentation allows the application to gain cloud-native parallel processing capabilities through the wrapper without requiring time-consuming re-writing of the entire application
2Adaptability or versatility
If legacy applications are migrated to cloud computing environment through re-factoring and re-writing, then the application can achieve distributed computing capabilities, but the migration cost will significantly increase
Solution Approach 1:
The wrapper library serves as a cost-effective intermediary that provides distributed computing capabilities through standardized interfaces. Instead of expensive re-factoring to adapt legacy applications to cloud architectures, the wrapper handles distribution, load balancing, and resource allocation, making cloud migration economically viable
Solution Approach 2:
The wrapper library is designed as a universal solution that can be applied to multiple legacy applications with different architectures (Java, .NET, proprietary). This multi-functionality reduces per-application migration costs by using a standardized approach across diverse application portfolios
3Adaptability or versatility
If legacy applications are migrated to cloud computing environment, then the application can leverage cloud benefits, but significant re-factoring and re-writing is required
Solution Approach 1:
The wrapper library acts as an intermediary that absorbs all the complexity of cloud computing integration, including parallel processing coordination, distributed resource management, and cloud infrastructure adaptation. This keeps the legacy application itself simple and unchanged while achieving cloud computing adaptability through the wrapper layer
Data Source
AI summary
A system for operating a legacy software application is presented. The system includes a distributed processing service. A wrapper software object is configured both to receive processing requests to a legacy software application from outside the distributed processing service and to send the processing requests using the distributed processing service. Additionally, an encapsulated software object includes the legacy software application and an exoskeleton connection service. The exoskeleton connection service is both configured to accept processing requests from the distributed processing service, and mapped to an application programming interface of the legacy software application.