Passive Real-Time Order State Replication for High-Availability Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional high-availability computing systems face vulnerabilities to data corruption and latency issues during failures, with existing replication and recovery solutions either risking data loss or introducing unacceptable bottlenecks.
Innovation Solution
A passive real-time order state replication and recovery system that uses a separately hosted application to continuously update the order state of a supported system via reliable transport protocols, minimizing latency and avoiding internal application logic vulnerabilities.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If internal application logic is used to maintain persistent order state in memory, then recovery speed is improved, but data reliability deteriorates due to vulnerability to data corruption
Solution Approach 1:
A passive replication application is introduced as an intermediary component that maintains a separate copy of the order state. This mediator receives data from the supported system and upstream system, maintains persistence independently, and provides recovery information without being part of the core application logic, thus resolving the contradiction between fast recovery and data reliability.
Solution Approach 2:
The invention creates a duplicate copy of the order state in a separate passive replication application. This copy serves as a backup that can be quickly restored without affecting the primary system's data integrity, allowing fast recovery while maintaining reliability through the separation of primary and backup data storage.
2Reliability
If active applications are placed on the data flow path to provide replication and recovery services, then data reliability is improved, but system latency worsens due to introduced bottlenecks
Solution Approach 1:
The passive replication application acts as a mediator that operates independently from the main data flow path. It receives data through separate mechanisms (data flow and acknowledgment flow) and maintains replication without intercepting or blocking the primary data processing, thus maintaining both reliability and speed.
Solution Approach 2:
The system implements selective replication where only necessary data elements (order state information) are replicated through the passive application, while the full data stream continues uninterrupted through the supported system. This partial action approach maintains reliability for critical data without creating bottlenecks for the entire system.
3Reliability
If traditional replication solutions are implemented, then data persistence is improved, but processing time worsens due to large amounts of processing required for order state recovery
Solution Approach 1:
The passive replication application continuously maintains an up-to-date copy of the order state in advance, so that when recovery is needed, the information is already prepared and available immediately. This preliminary action eliminates the need for time-consuming reconstruction of order state during recovery events.
Solution Approach 2:
By maintaining a pre-synchronized copy of the order state in the passive replication application, the system enables instant recovery without requiring extensive processing to reconstruct data. The copy is kept current through continuous synchronization, allowing rapid restoration when failures occur.
Data Source
AI summary
A system and method for passive real-time order state replication and recovery. Upstream data is received from an upstream system via a reliable transport, the upstream data also received by a supported system. Downstream data is received from the supported system via the reliable transport. Data acknowledgements are received from the supported system acknowledging receipt of the upstream and downstream data. A replicated current order state of the supported system is continuously updated in real-time based on the received upstream data, downstream data and the data acknowledgements. A recovery request is received after the supported system has experienced an outage. The current order state is restored to the supported system by transmitting a recovery message to the supported system containing the replicated current order state.