Network Routing Logic for Near Real-Time Data Center Failover
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data center failover systems, reliant on DNS updates, can take hours to propagate changes, leading to significant revenue loss due to prolonged unavailability and failed client requests during data center failures.
Innovation Solution
Implementing a networked computer system with replicated redirect tables and network routing logic that allows for immediate switching to a backup data center, bypassing the need for DNS propagation, enabling near real-time rerouting of client requests.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If DNS updates are used for data center failover, then the system is easy to implement, but the failover time is prolonged (taking hours to propagate)
Solution Approach 1:
The patent segments the failover process by introducing a redirect table that separates the routing decision logic from the DNS system. The redirect table is maintained at the data center level and can be updated independently and immediately, while DNS records remain unchanged. This segmentation allows the routing information to be updated locally without waiting for DNS propagation, thus reducing failover time while maintaining ease of implementation through the use of standard DNS infrastructure for long-term routing.
Solution Approach 2:
The patent introduces a redirect table as an intermediary mechanism between the client and the data center. This redirect table acts as a local cache or mediator that stores current routing information and can be updated immediately when a failover occurs. The client first checks the redirect table for routing decisions, and only falls back to DNS lookup when necessary. This intermediary layer enables rapid failover by providing immediate access to updated routing information without waiting for DNS propagation.
2Stability of the object's composition
If DNS cache refresh time is set to hours for stability, then DNS system is stable, but client requests fail during data center unavailability
Solution Approach 1:
The patent implements preliminary action by pre-populating redirect tables with routing information before failover occurs. The redirect table is maintained and updated in advance at the data center level, so when a failover event happens, the routing information is already prepared and immediately available. This eliminates the need to wait for DNS cache refresh during critical failover scenarios, ensuring service continuity while maintaining DNS stability.
Solution Approach 2:
The patent introduces dynamics by making the redirect table updateable and dynamic, allowing it to change in real-time based on data center availability. While DNS records remain static and stable for long-term routing, the redirect table can be dynamically updated to reflect current operational status of data centers. This dynamic redirect table enables the system to adapt quickly to changes in data center availability, ensuring reliable service routing without compromising DNS system stability.
3Measurement precision
If DNS entry propagation is waited for before switching data centers, then routing accuracy is maintained, but revenue loss increases due to prolonged downtime
Solution Approach 1:
The patent applies local quality by implementing routing decision-making at the local data center level through redirect tables, rather than relying on centralized DNS propagation. Each data center maintains its own redirect table with local routing information that can be updated independently and immediately. This localised approach ensures routing accuracy is maintained through the redirect table mechanism while enabling immediate failover action, thus preventing revenue loss without sacrificing routing precision.
4Reliability
If a backup data center is maintained for failover, then system reliability is improved, but the complexity of managing multiple data centers increases
Solution Approach 1:
The patent implements self-service by enabling the backup data center to automatically assume the role of the primary data center through the redirect table mechanism. When a failover event occurs, the backup data center's routing information is automatically updated in the redirect table, and clients are automatically redirected without requiring complex manual configuration or management intervention. This self-service approach maintains high system reliability through automated failover while reducing the operational complexity of managing multiple data centers.
Data Source
AI summary
A networked computer system provides a way to quickly switch to a backup data center when a primary data center fails. Each data center includes a redirect table that specifies a geographical area corresponding to each user. The redirect table is replicated on one or more data centers so that each data center has the same information. When a data center fails, the redirect table in one of the non-failed data centers is updated to specify a new data center for each client that used the failed data center as its primary data center. A network dispatcher recognizes that the failed data center is unavailable, and routes a request to the backup data center. Network routing logic then issues a redirection command that causes all subsequent requests from that client to be redirected directly to the backup data center.