Joint Cloud Non-Cloud Management System
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Large enterprises face challenges in migrating existing software applications to cloud computing environments due to compatibility issues with older operating systems, hardware specificity, and unsupported software, making it difficult to leverage cloud computing benefits like scalability and reliability.
Innovation Solution
A joint management system that combines cloud and non-cloud environments through a service management device, cloud orchestration, non-cloud orchestration, and a joint cloud and non-cloud management device, allowing for the scheduling and execution of tasks across both environments, enabling unified management and integration of cloud and non-cloud resources.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If existing software applications are migrated to cloud computing environment, then cloud benefits (lower cost, scalability, reliability) are achieved, but compatibility issues arise due to older operating systems, hardware specificity, and unsupported software
Solution Approach 1:
The patent introduces a cloud gateway as an intermediary component that sits between the legacy application environment and the cloud computing environment. This gateway translates communication protocols, data formats, and authentication mechanisms, enabling legacy applications to interact with cloud services without requiring modification of the original applications. The gateway handles protocol conversion, data transformation, and session management, thereby resolving compatibility issues while maintaining the integrity of both legacy and cloud systems.
Solution Approach 2:
The patent segments the migration process into distinct layers: the legacy application layer remains unchanged, the cloud gateway layer handles translation and integration, and the cloud service layer provides scalable resources. This segmentation allows each layer to be optimized independently - legacy applications continue to run on their original platforms while the gateway manages cloud-specific protocols and the cloud layer delivers scalability and reliability benefits.
2Reliability
If legacy systems are maintained in non-cloud environment, then compatibility and stability are preserved, but cloud benefits (scalability, lower cost) cannot be utilized
Solution Approach 1:
The patent merges the strengths of both legacy and cloud environments by creating a hybrid architecture. Legacy systems that require stability and compatibility remain in the on-premises environment, while cloud services provide scalable computing resources, storage, and specialized services. The cloud gateway orchestrates workloads between these environments, moving appropriate tasks to the cloud while maintaining critical legacy functions locally, thereby achieving both reliability and improved operational efficiency.
3Productivity
If full cloud migration is implemented, then scalability and cloud benefits are maximized, but transformation costs and time increase due to application incompatibility
Solution Approach 1:
The patent implements partial cloud migration rather than complete migration. Critical legacy applications that cannot be easily modified remain on-premises and are accessed through the cloud gateway, while non-critical applications and workloads are migrated to the cloud. This selective approach allows the organization to realize cloud benefits for appropriate workloads without incurring the full cost and time of complete migration, enabling a phased transformation strategy.
Data Source
AI summary
Examples of techniques for jointly managing a cloud and non-cloud environment are disclosed. In one example implementation according to aspects of the present disclosure, a method includes: receiving a request to be executed on one of a cloud resource and a non-cloud resource using one of cloud orchestration and non-cloud orchestration, the request comprising a plurality of tasks; scheduling the first task for execution on the cloud resource by a cloud orchestration device using a joint cloud and non-cloud management device; scheduling the second task for execution on the non-cloud resource by a non-cloud orchestration device using a non-cloud management device; and scheduling the third task for execution on the non-cloud resource by the non-cloud orchestration device using the joint cloud and non-cloud management device.