Event-Driven Failover Using Replica Event Stores
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data center architectures face challenges in ensuring continuous service availability and preventing data loss due to failures, particularly in event-driven systems where efficient failover mechanisms are lacking.
Innovation Solution
A system comprising two data centers with synchronized main and replica event stores and processors, where a management system detects failures and directs event processors to retrieve and process events from either the main or replica event store based on configuration, ensuring seamless failover and minimizing data loss.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a primary data center processes events from its main event store, then service availability is maintained, but if the primary data center fails, service interruption occurs
Solution Approach 1:
The patent implements a replica event store in the secondary data center that mirrors the main event store of the primary data center. This copying mechanism ensures that event data is available in both locations, allowing seamless failover when the primary data center fails, thus maintaining service availability without requiring complex distributed consensus protocols
Solution Approach 2:
The system performs preliminary synchronization of the replica event store with the main event store before any failure occurs. This advance preparation ensures that when failover is needed, the secondary data center already has the necessary event data ready for immediate processing, eliminating the need for complex real-time data recovery mechanisms
2Reliability
If events are retrieved from the main event store during failover, then data consistency is maintained, but retrieval time increases
Solution Approach 1:
The replica event store acts as an intermediary during failover operations. Instead of directly accessing the main event store from the secondary data center (which would cause network latency and consistency issues), the pre-synchronized replica serves as a local copy that provides both data consistency and fast access, eliminating the trade-off between consistency and retrieval time
3Reliability
If the system switches to a secondary data center upon failure, then service continuity is maintained, but system complexity increases
Solution Approach 1:
The system uses configuration parameters associated with event processors to determine failover behavior. By changing operational parameters (such as which event store to access and which data center to route to) rather than restructuring the entire system architecture, the patent achieves service continuity with minimal complexity
Solution Approach 2:
Event processors are designed with universal functionality to operate with either the main event store or the replica event store depending on configuration. This multi-functionality allows the same processor to serve primary and secondary roles, reducing the need for dedicated failover hardware and simplifying the overall system architecture
Data Source
AI summary
A system determines that a primary event processor, included in a primary data center, is associated with a failure. The primary event processor is included in the primary data center and configured to process first events stored in a main event store of the primary data center. The system identifies a secondary event processor, in a secondary data center, that is to process one or more first events based on the failure. The primary event processor and the secondary event processor are configured to process a same type of event. The system causes, based on a configuration associated with the primary or secondary event processor, the one or more first events to be retrieved from one of the main event store or a replica event store. The replica event store is included in the secondary data center and mirrors the main event store of the primary data center.