Context-Mapped Container Deployment for Controlled Application Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Cloud computing architecture-based commerce applications face complexity due to tight coupling with databases and jobs frameworks, leading to disruptions during updates, which can negatively impact businesses, especially when traditional container orchestration deployments are static and do not allow for dynamic conditional shutdowns or updates.
Innovation Solution
Implement a system that allows for dynamic application updates by using a shutdown API to manage the upgrade process, enabling conditional stops and synchronized shutdowns across nodes, allowing backend jobs to complete or pause before deployment, and supporting updates within or outside maintenance windows.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If traditional container orchestration deployment is used, then deployment simplicity is maintained, but application disruption and business impact increase
Solution Approach 1:
The patent implements dynamic conditional shutdown logic that allows the system to adaptively control application deployment based on real-time conditions. The shutdown API enables conditional decisions about whether to shut down applications during updates, allowing the system to dynamically adjust deployment behavior to minimize disruption while maintaining simplicity.
Solution Approach 2:
The system performs preliminary checks before deployment by evaluating shutdown conditions through the shutdown API. This preliminary action determines whether the application should be shut down before the update is applied, allowing for proactive prevention of disruptions while maintaining a simple deployment process.
2Device complexity
If static container shutdown is used, then system simplicity is maintained, but deployment flexibility and control decrease
Solution Approach 1:
The shutdown API serves as an intermediary layer between the deployment system and the application containers. This intermediary provides conditional shutdown control without adding significant complexity to the overall system, enabling flexible deployment decisions while maintaining relative system simplicity.
Solution Approach 2:
The system changes the shutdown parameter from a static fixed state to a dynamic conditional state. By introducing conditional parameters that evaluate deployment context, the system gains flexibility in controlling application shutdowns without fundamentally complicating the container orchestration mechanism.
3Productivity
If application updates are deployed without conditional shutdown control, then deployment speed is maintained, but job completion and data integrity are compromised
Solution Approach 1:
The shutdown API implements a feedback mechanism that provides information about application state and deployment conditions. This feedback allows the system to make informed decisions about conditional shutdowns, ensuring that backend jobs can complete or be properly paused while maintaining deployment speed through automated decision-making.
Solution Approach 2:
The system performs preliminary evaluation of shutdown conditions before executing the deployment. This preliminary action ensures that necessary jobs are identified and can complete or be paused appropriately before the update is applied, maintaining both deployment speed and job completion integrity through proactive planning.
Data Source
AI summary
Systems and methods are provided for determining, at an operator executed on a server that is separate from an application, whether to perform an update of the application. The operator may perform an upgrade precheck when it is determined that the update to the application is to be performed. The precheck may include determining whether a database migration is to be performed as part of the update to the application, and receiving an update mode and an update type to determine the upgrade to the application. The operator may provide to the application via an application program interface (API), one or more application shutdown configuration parameters for the update based on the received update mode and update type of the upgrade precheck. The operator may deploy the update to the application based on the determined update mode and update type.