Fallback Application Layer for Non-Disruptive Software Upgrades
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current high availability and near zero downtime solutions for software upgrades and configuration changes in computer systems require system outages for data synchronization and do not ensure data integrity during maintenance, as they focus on technical redundancy rather than application-level redundancy.
Innovation Solution
Implementing a fallback system with a primary and fallback application layer that maintains system availability by redirecting users to the fallback layer during upgrades, ensuring data integrity through protection modes and synchronized data layers, allowing non-disruptive software upgrades or configuration changes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If technical redundancy (storage mirroring and additional server hardware) is used for high availability, then system reliability is improved, but device complexity increases and data semantics are not preserved
Solution Approach 1:
The patent creates a fallback application layer that copies the operational state and data semantics of the primary application layer. This copy maintains application-level redundancy rather than just technical hardware redundancy, allowing the system to restore service by switching to the fallback layer while preserving data meaning and business logic.
Solution Approach 2:
The system is segmented into distinct primary and fallback application layers, each capable of independent operation. This segmentation allows the fallback layer to be maintained separately and activated when the primary layer requires maintenance, providing high availability without requiring complete system redundancy.
2Manufacturing precision
If the system is taken out of service for upgrades, then manufacturing precision (data integrity) is improved, but loss of time (downtime) increases
Solution Approach 1:
The fallback application layer is prepared in advance with synchronized data before the primary layer needs maintenance. This preliminary action ensures that when the primary layer is taken offline for upgrades, the fallback layer is already ready to immediately take over, eliminating downtime while maintaining data integrity through pre-synchronized state.
Solution Approach 2:
The system maintains a cushion of readiness by keeping the fallback application layer synchronized and ready to activate. This beforehand cushioning ensures that if the primary layer fails or requires maintenance, there is already a prepared backup state that can immediately restore service without data loss or downtime.
3Productivity
If near zero downtime solutions are implemented, then productivity is improved, but measurement precision (data synchronization accuracy) deteriorates due to finite system outage requirements
Solution Approach 1:
The system implements feedback mechanisms that continuously monitor and compare data between the primary and fallback application layers. This feedback ensures data synchronization accuracy is maintained while allowing the fallback layer to remain ready for immediate activation, achieving both high productivity and precise data synchronization without requiring finite outages.
Data Source
AI summary
A computer system includes a processor, an application layer, and a data layer. The application layer includes a primary application layer, and at times of system upgrade or configuration change, a fallback application layer. The data layer includes a first layer that is not affected by a software upgrade or a configuration change, a second data layer that is modified by the software upgrade or the configuration change, and a third data layer that is available to users during the upgrade. The system, and in particular the fallback application layer and the third data layer, allow the system to be available to users during the software upgrade or system configuration change.