Zero Downtime Application Package Deployment via Version Coexistence
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for deploying new application packages on enterprise servers require downtime, disrupting daily business operations and user access, as they necessitate halting current activities to overwrite the existing package.
Innovation Solution
Implementing a system that allows multiple versions of an application package to coexist on the same enterprise server, with different directory structures and unique package names, enabling zero-downtime deployment by controlling user access based on session timing and using a shared pathcode for storage locations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the current application package is overwritten and replaced by the new application package, then the new application specifications and logic can be deployed, but daily business is interrupted and user access is halted
Solution Approach 1:
The patent segments the application package deployment process by maintaining separate coexistence of the current application package and the new application package on the enterprise server. This allows the system to serve both packages simultaneously to different users, enabling deployment without forcing a complete system shutdown or overwriting operation.
Solution Approach 2:
The patent introduces a new dimension to the deployment problem by implementing version control and user-based routing. Instead of a single-dimensional overwrite approach, the system now operates in multiple dimensions: package versioning (current vs. new), user session timing (before vs. after deployment), and selective access routing. This allows simultaneous availability of both packages through different access paths.
2Ease of manufacture
If the current application package is halted to deploy the new package, then the new package can be installed, but downtime occurs and users cannot access the application
Solution Approach 1:
The patent applies preliminary action by deploying the new application package in advance while the current package remains active. The system prepares the new package, stores it on the server, and configures deployment parameters before any user impact occurs. Users continue accessing the current package until administrators determine the deployment is ready, at which point new sessions are routed to the new package.
Solution Approach 2:
The patent ensures continuity of useful action by maintaining uninterrupted user access to application functionality throughout the deployment process. While the package being deployed changes in the background, users experience continuous service availability - either accessing the current package during deployment preparation or the new package after deployment completion, with no downtime interruption.
3Object-affected harmful factors
If the application package is deployed during slow or off-hour times, then downtime disruption is minimized, but productivity is still affected during these windows
Solution Approach 1:
The patent implements dynamics by making the application package assignment flexible and time-dependent. Rather than a static single-package system, the system dynamically routes users to different packages based on deployment status and user session timing. This allows the system to adapt to deployment activities while maintaining productivity, as users can access appropriate packages at different times without complete shutdowns.
Data Source
AI summary
Systems, methods, and other embodiments associated with deploying application packages are described. In one embodiment, a current version of an application package is stored. An enterprise server deploys the current version. Upon a first user signing on to the enterprise server, providing the first user with access to the current version. A modified version of an application package is stored and deployed. Upon a second user signing on to the enterprise server, providing the second user with access to the modified version. The current version and the modified version are simultaneously active on the enterprise server. Subsequent users that sign on are only given access to the modified version and are not permitted access to the current version. Upon the first user signing out, deleting the current version, and causing the modified version to become a new current version.