Adapter for Cloud Access to Legacy Applications
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Legacy desktop applications, often developed without cloud collaboration in mind, are difficult to make cloud-accessible due to their reliance on specific technologies and architectures, requiring significant development to adapt them for cloud environments, and existing solutions like VPN tunnels do not offer the advantages of cloud-hosted applications such as mobile and web-based access.
Innovation Solution
A system comprising an adapter installed on a local system with a legacy application, enabling cloud access by synchronizing data between a cloud system and the local application, using APIs to communicate and execute commands in a standard format, thus allowing multiple systems to access the legacy application without specific setup for each system.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If VPN tunnel or remote connection technology is used to provide remote access to legacy desktop applications, then remote access capability is achieved, but mobile and web-based access advantages of cloud-hosted applications are lost and significant configuration complexity is required
Solution Approach 1:
The patent introduces an adapter as an intermediary component that sits between the legacy desktop application and the cloud system. This adapter handles the complexity of communication protocols and data formatting, allowing the legacy application to be accessed via cloud APIs without requiring users to configure VPN tunnels or understand complex network infrastructure. The adapter translates cloud-based requests into application-specific commands automatically.
Solution Approach 2:
The patent creates a cloud-based copy or representation of the legacy application's data and functionality through standardized APIs. Instead of requiring direct connection to the original application via VPN, users interact with a cloud-hosted interface that replicates the application's capabilities. This copying approach enables mobile and web-based access while the original legacy application remains unchanged on-premises.
2Adaptability or versatility
If legacy desktop applications are adapted for cloud environments, then cloud accessibility is improved, but significant development effort and infrastructure management are required
Solution Approach 1:
The patent segments the system into three independent components: the legacy desktop application (remaining on-premises), the adapter (handling communication), and the cloud interface (providing accessibility). This segmentation allows each component to be developed and maintained independently. The legacy application requires no modification, the adapter can be developed separately with minimal effort, and the cloud interface provides standard access points, thereby reducing overall development complexity while achieving cloud accessibility.
3Productivity
If cloud system accesses local application data, then data manipulation capability is achieved, but data integrity and synchronization challenges arise
Solution Approach 1:
The patent implements a feedback mechanism where the adapter continuously monitors changes in the legacy application's data and automatically synchronizes these changes to the cloud system. Conversely, changes made through the cloud interface are fed back to the local application through the adapter. This bidirectional feedback loop ensures data integrity by maintaining consistency between the local and cloud versions of the data without requiring complex manual synchronization processes.
Data Source
Figure 1
Figure 2
Figure 3A
AI summary
A system enabling cloud access to a legacy application, said system comprising a local system and a cloud system, wherein the local system comprises: a locally stored legacy application; a first storage comprising a first data store associated with the application; an adapter configured to retrieve data from the first data store; and a synchronisation engine configured to synchronise the retrieved data with the cloud system; and the cloud system comprises: a second storage comprising a second data store associated with the legacy application; and an application programming interface, API, configured to receive the retrieved data from the local system and update the second data store based on the received data.