Reboot Reduction Infrastructure for Software Modification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Software modification reboots cause significant customer pain and financial loss due to downtime and productivity loss in enterprises and unwanted disruptions for users, especially with frequent security updates.
Innovation Solution
A reboot reduction infrastructure that allows applications to detect and shut down applications with files in use, saving user data and application state, and then restart them automatically, minimizing disruptions by using APIs to manage the process.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If software modifications are installed to improve security and functionality, then system reliability is improved, but user disruption and downtime increase
Solution Approach 1:
The system performs preliminary actions by detecting which applications are using files that need to be modified before the installation begins. It proactively shuts down these applications in advance, prepares the modification, and then reinstates them after installation, preventing the need for user-initiated reboots and reducing overall downtime.
Solution Approach 2:
The modification installation system serves itself by automatically managing the shutdown and restart of applications without requiring user intervention. The system independently detects file conflicts, manages application lifecycle, and restores application states, making the entire modification process self-contained and user-free.
2Ease of manufacture
If applications are shut down to allow file modifications, then modification installation is enabled, but application availability and productivity decrease
Solution Approach 1:
The system dynamically adjusts application availability by temporarily shutting down applications only when file modifications are required, and automatically restarting them when modifications are complete. This dynamic management ensures modifications can be installed while minimizing the duration of application unavailability, thus maintaining productivity.
Solution Approach 2:
The system temporarily discards application execution state by shutting down applications during modification installation, then recovers the state by automatically restarting the applications and restoring their previous operational context. This allows modification installation while minimizing permanent loss of productivity.
3Reliability
If frequent security updates are applied to improve system protection, then system security is enhanced, but user disruption and operational downtime increase
Solution Approach 1:
The update system operates autonomously by automatically detecting which applications need to be shut down for security updates, performing the shutdowns, installing updates, and restarting applications without requiring user action. This self-service approach enables frequent security updates while maintaining user continuity and operational smoothness.
Solution Approach 2:
The system performs preliminary detection of file conflicts and automatic application shutdowns before security updates are installed, ensuring that updates can be applied smoothly without user interruption. This preliminary preparation enables frequent security updates while preserving user operational continuity.
Data Source
AI summary
A reboot reduction infrastructure may be used by applications to make installing modifications as unobtrusive as possible. Applications may register with the reboot reduction infrastructure and use provided APIs to detect which applications and services have files in use, shutdown down those applications with files in use and then restart those applications in a form similar to which they were in when the applications were shut down.