Cloud On-Premise Compatibility Framework Version Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The integration of cloud-based and on-premise applications faces challenges due to differing release cycles, with cloud-based applications updating frequently while on-premise applications update less frequently, leading to complexity in managing multiple versions across various entities.
Innovation Solution
A compatibility framework is provided that maintains a single code base to support all on-premise application versions, allowing the cloud-based application to execute instructions based on the version used by the requesting entity, and manages enhancements or bug fixes by associating them with unique identifiers to maintain backward compatibility.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If cloud-based application deploys frequent updates, then application functionality and features are improved, but complexity of managing multiple versions across on-premise applications increases
Solution Approach 1:
The patent segments the monolithic application codebase into modular microservices that can be independently versioned, developed, and deployed. Each microservice represents a functional unit that can be updated without requiring updates to the entire application system, thereby reducing the complexity of managing multiple versions across on-premise installations.
Solution Approach 2:
The patent implements dynamic version management where the system automatically adapts to different version combinations of cloud and on-premise applications. The version compatibility layer dynamically determines which version of each microservice to execute based on the requesting on-premise application's version, eliminating the need for static version matching and manual update coordination.
2Ease of manufacture
If on-premise application updates are delayed, then change management and cost control are improved, but compatibility with cloud-based application features deteriorates
Solution Approach 1:
The patent creates a universal compatibility layer that serves multiple functions: it acts as a translation layer between different version protocols, a feature gateway that exposes cloud features to on-premise applications, and a version abstraction layer. This single multi-functional component enables on-premise applications to access cloud features regardless of version mismatches, maintaining adaptability while allowing delayed updates.
Solution Approach 2:
The patent introduces an intermediary compatibility service that sits between the cloud-based application and on-premise applications. This mediator translates feature requests from older on-premise versions into appropriate calls to newer cloud microservices, enabling feature compatibility without requiring on-premise applications to be updated to match the cloud version.
3Reliability
If multiple version identifiers are maintained, then backward compatibility is improved, but instruction set complexity increases
Solution Approach 1:
The patent changes the parameter representation from maintaining separate instruction sets for each version to using version identifiers as parameters that route to appropriate microservice instances. Instead of having different code paths for each version, the system uses version numbers as routing parameters that dynamically select the appropriate microservice implementation, reducing instruction set complexity while maintaining backward compatibility.
Data Source
AI summary
Systems and methods are described herein for receiving, by a server computer associated with a cloud-based application, a request via a network from a requesting device associated with an on-premise application, for at least one feature associated with an application service provided by the cloud-based application, the request including a requester identifier and a requested feature identifier, determining, by the server computer associated with the cloud-based application, a version identifier for the request based on the requester identifier, accessing, by the server computer associated with the cloud-based application, instructions for the cloud-based application which include instructions associated with a plurality of version identifiers, each version identifier associated with at least one feature identifier, parsing, by the server computer associated with the cloud-based application, the instructions for the cloud-based application to determine a subset of instructions associated with the version identifier of the request and the requested feature identifier, executing, by the server computer associated with the cloud-based application, the subset of instructions associated with the version identifier of the request and the requested feature identifier, and returning, by the server computer associated with the cloud-based application, a response to the requesting device via the network, indicating that at least one feature associated with the application service provided by the cloud-based application has been executed.