Stateless Connector for Stateful Backend Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Organizations face difficulties in building and deploying mobile applications that interact with stateful backend systems, requiring significant effort to update the backend system to expose data for stateless applications, which is time-consuming, resource-intensive, and risky, often leading to hesitancy in deploying mobile applications on cloud platforms.
Innovation Solution
A stateless connector is generated and deployed automatically by recording user interactions with an application server, allowing mobile applications to connect to stateful backend systems without modifying the underlying backend system, thereby simplifying backend systems and making them more resilient, portable, and scalable.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the backend system is updated to expose data for stateless applications, then mobile applications can be deployed, but the update process is time-consuming, resource-intensive, and risky
Solution Approach 1:
The patent introduces an intermediary layer (gateway or adapter) between the stateful backend system and stateless mobile applications. This intermediary handles protocol translation and data exposure without requiring modifications to the existing backend system, thus resolving the contradiction by enabling stateless application support while avoiding time-consuming and risky backend updates.
Solution Approach 2:
The system is segmented into distinct layers: the existing stateful backend system remains unchanged, while a separate intermediary layer is introduced to handle stateless request processing. This segmentation allows the backend to maintain its original functionality while the new layer provides adaptability for mobile applications, eliminating the need for risky backend modifications.
2Adaptability or versatility
If the backend system is updated to accommodate stateless requests, then mobile applications can connect, but the complexity and risk of the update increase
Solution Approach 1:
By introducing an intermediary layer, the patent isolates the complexity of protocol translation and data exposure logic away from the backend system. The backend remains simple and unchanged, while the intermediary handles the complexity of accommodating both stateful and stateless protocols, thus resolving the contradiction between adaptability and system complexity.
3Adaptability or versatility
If developers focus on backend system updates, then data exposure for mobile applications is achieved, but development time and resources are consumed
Solution Approach 1:
The intermediary layer is designed to automatically handle data exposure and protocol translation without requiring manual backend modifications. This self-service approach enables data accessibility for mobile applications while freeing developers from time-consuming backend update tasks, thus resolving the contradiction between adaptability and development productivity.
4Adaptability or versatility
If the backend system is modified to support both stateful and stateless protocols, then versatility is improved, but the system becomes less resilient and portable
Solution Approach 1:
The patent segments the protocol handling functionality into a separate intermediary layer, keeping the backend system dedicated to its original stateful protocol. This segmentation maintains the backend's resilience and portability by preventing protocol-related complexities from being introduced, while the intermediary layer provides the necessary protocol support capability for mobile applications.
Solution Approach 2:
The intermediary layer acts as a mediator that handles protocol translation between stateful backend and stateless mobile applications. This isolation protects the backend system's reliability and portability by preventing protocol-related modifications, while still achieving versatility through the intermediary's protocol support capabilities.
Data Source
AI summary
Disclosed herein are system, method, and computer program product embodiments for building a stateless connector to a stateful backend system. The stateless connector allows developers to deploy mobile applications that interact with the stateful backend system without refurbishing the backend system to accommodate stateless design methodologies and access functions. The stateless connector thus provides a bridge between a stateless application and a stateful backend system without requiring any risky and potentially disruptive updates the backend system. The stateless connector may be generated and deployed automatically based on a recording of user interactions with stateful application server. This saves an enormous amount of time and effort in the application development process and allows application developers to focus their time and efforts on the presentation components and business logic of the mobile application.