SaaS Runtime Engine for Legacy Application Cloud Migration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Legacy software applications often fail to take advantage of cloud environments due to compatibility issues, running inefficiently or not being well-suited to cloud configurations, necessitating a method to adapt and migrate them for optimal cloud operation.
Innovation Solution
A system comprising a scanning engine, compatibility engine, and runtime engine that automatically enables non-SaaS capable applications to operate in a cloud environment by identifying necessary SaaS capabilities, replicating the application, and providing SaaS functionality without altering core components, thus transforming them into SaaS capable applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If legacy applications are migrated to cloud environment, then accessibility and scalability are improved, but compatibility issues and operational efficiency deteriorate
Solution Approach 1:
The patent introduces a SaaS runtime engine as an intermediary layer between legacy applications and the cloud environment. This runtime engine provides necessary SaaS capabilities (tenancy services, operations services, business services) to legacy applications without requiring modifications to their core components, thereby enabling cloud deployment while maintaining application compatibility and reliability
Solution Approach 2:
The patent segments the SaaS implementation into distinct functional components: tenancy services for multi-tenant isolation, operations services for application management, and business services for core functionality. This segmentation allows legacy applications to selectively adopt only the SaaS capabilities they need, improving compatibility while maintaining cloud accessibility
2Adaptability or versatility
If non-SaaS applications are transformed to SaaS capable applications, then SaaS functionality is improved, but system complexity increases
Solution Approach 1:
The patent creates a universal SaaS runtime engine that can serve multiple legacy applications with different requirements. This runtime engine provides a standardized set of SaaS capabilities (tenancy, operations, business services) that can be applied across diverse applications, reducing the need for application-specific modifications and thereby limiting the increase in system complexity
Solution Approach 2:
The patent replicates the necessary SaaS functionality through the runtime engine rather than modifying each legacy application's core code. This copying approach allows SaaS capabilities to be added as an external layer, maintaining the original application architecture while providing enhanced SaaS functionality
3Adaptability or versatility
If core components of legacy applications are altered to enable SaaS functionality, then SaaS operation is improved, but application reliability deteriorates
Solution Approach 1:
The SaaS runtime engine acts as an intermediary that interfaces with legacy applications without altering their core components. It provides SaaS functionality through external services (tenancy, operations, business services) while leaving the original application logic intact, thereby maintaining reliability while enabling SaaS operation
Solution Approach 2:
The patent performs preliminary analysis using a scanning engine and compatibility engine to identify what SaaS capabilities are needed before deployment. This preliminary action allows the system to configure the runtime engine appropriately without requiring subsequent modifications to the legacy application's core components, preserving reliability while enabling SaaS functionality
Data Source
AI summary
A system that transforms non-SaaS applications into tenant-aware SaaS applications is disclosed, which analyzes the non SaaS applications to determine which intercepts to external libraries need to be translated into SaaS intercepts that utilize SaaS tenancy services, SaaS operations services, and/or SaaS business services. The system transforms the non-SaaS applications into SaaS applications by providing intercept handlers that call SaaS services on demand when the transformed SaaS application throws a transformed SaaS interrupt.