Resource Adapter Proxy for Stateful Desktop Software in Distributed Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Desktop software applications, designed for single-user, stateless operations, face challenges in migrating to Service Oriented Architectures (SOA) and web applications experience limitations such as latent communication, weak presentation layers, and lack of standards, making it difficult to integrate them into distributed enterprise systems without significant modifications.
Innovation Solution
The integration of desktop software into a distributed enterprise system is achieved through the use of a Resource Adapter acting as a smart proxy, managed by a Resource Manager, which allows for seamless interaction and resource allocation, enabling stateful behavior without altering the application code or workflows, and employs a self-healing mechanism to handle failures proactively.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If desktop software is migrated to Service Oriented Architecture, then system integration and distributed operation are improved, but application complexity and modification requirements increase
Solution Approach 1:
The patent introduces a Resource Adapter as an intermediary component that sits between the desktop application and the SOA infrastructure. This adapter handles resource management, state tracking, and communication protocols, allowing the application to remain relatively simple while achieving sophisticated distributed operation. The adapter translates between the application's simple interface and the complex SOA requirements.
2Adaptability or versatility
If web applications are used for enterprise services, then accessibility and network distribution are improved, but communication latency and presentation layer weakness increase
Solution Approach 1:
The Resource Adapter pre-loads and caches application instances and their associated state information before they are needed. By maintaining ready-to-use instances in memory with their state preserved, the system eliminates the need for repeated initialization and reduces communication latency when users access the application, while still maintaining web-based accessibility.
3Device complexity
If stateless service architecture is used, then system simplicity and scalability are improved, but stateful application behavior and user experience deteriorate
Solution Approach 1:
The patent segments the system into two distinct layers: a stateless service infrastructure layer that handles scalability and simplicity, and a state management layer implemented through Resource Adapters that handle user-specific state. This segmentation allows the backend to remain simple and scalable while the adapter layer provides sophisticated stateful behavior, effectively resolving the contradiction between stateless architecture and stateful user experience.
Data Source
AI summary
A resource manager service, system, apparatus and method manages resources for a user group of at least one user by utilizing a resource adapter. The resource adapter serves as a smart proxy to mimic the user of a desktop software application preserving the interaction model with the application. Embodiments of the invention allow integration of desktop software in a distributed enterprise system, as a service, without requiring non-trivial modifications to the application code or to alter its workflows in any material way. A resource manager service, system, apparatus and method treat instances of the resource adapters, smart proxies, as finite but reusable resources that can be allocated and “bound” to a given user for an unspecified duration.


