Plugin Version Management for Legacy On-Premise Applications
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Legacy on-premises applications transitioning to a cloud environment face challenges in plugin management, including limited flexibility and increased risk due to the lack of direct user access and potential malware introduction, as well as complexities in version compatibility and data migration.
Innovation Solution
A plugin installer service is implemented in the cloud environment, allowing users to select and manage plugins through a frontend interface, with the plugin installer service handling installation, upgrade, and removal, while maintaining plugins in a secure cloud environment and using plugin containers to manage plugin payloads, and a plugin catalog service ensures compatibility with application instances.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If users directly access and manage plugins on on-premises computing systems, then plugin management flexibility is improved, but security risk increases due to potential malware introduction
Solution Approach 1:
The patent introduces a plugin catalog service and plugin installer service as intermediaries between users and the application. Users interact with the frontend interface to select plugins from an approved catalog, and the installer service automatically handles deployment. This intermediary layer eliminates direct user access to the computing system, preventing malware introduction while maintaining plugin management flexibility through centralized control and approval workflows.
2Productivity
If legacy on-premises applications are transitioned to cloud environment, then accessibility and scalability are improved, but plugin management complexity increases due to lack of direct user access
Solution Approach 1:
The patent implements automated self-service mechanisms where the plugin installer service automatically retrieves plugins from the catalog, validates compatibility with the application version, and deploys them without requiring user intervention. The system autonomously handles version matching, dependency resolution, and installation, transforming a complex manual process into a simplified automated workflow that reduces management complexity while maintaining cloud-based accessibility.
Solution Approach 2:
The plugin catalog service and installer service are designed as universal components that work across multiple application instances and versions. The catalog stores standardized plugin metadata and compatibility information, while the installer service universally handles deployment for different applications, reducing the need for application-specific customization and simplifying management across the cloud environment.
3Productivity
If plugins are installed without version compatibility verification, then installation speed is improved, but system reliability deteriorates due to version conflicts
Solution Approach 1:
The patent implements preliminary version compatibility verification through the plugin catalog service, which pre-stores compatibility information between plugins and application versions. Before installation, the installer service automatically queries the catalog to verify compatibility, resolving version conflicts in advance. This preliminary check prevents unreliable installations while maintaining speed by eliminating the need for complex runtime compatibility testing and manual version matching.
Data Source
AI summary
Various examples are directed to systems and methods for managing a plugin at a cloud-implemented database management application. A service at the cloud environment may receive from a first user a request to install a first plugin to a database management application executing at the cloud environment in at least one container. The service may determine a build version of the database management application and access a plugin catalog record for the first plugin. The plugin catalog record may comprise an indication of a first plugin version associated with the build version of the database management application. The service may access first plugin version installation data and install the first plugin version.