Layered Database Failover for Telecom Read Availability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current cellular network data repositories face challenges in achieving extremely high read availability (99.99999%) due to inflexible and difficult-to-implement customized configurations, making it hard to scale and upgrade.
Innovation Solution
A high read availability system utilizing a layered database architecture with a primary, hot backup, and tepid backup database, asynchronously replicating data across logically linked yet physically separate layers, ensuring data availability through a novel backup scheme that leverages standard SQL servers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If customized configurations and programming are used in data repositories, then read availability of 99.99999% can be achieved, but the system becomes inflexible and difficult to implement and scale
Solution Approach 1:
The system divides the database into multiple independent tiers (hot standby tier and warm standby tier), each with specific replication roles. This segmentation allows the system to achieve high availability through structured redundancy while maintaining flexibility in managing and upgrading individual tiers independently.
Solution Approach 2:
The patent changes the operational parameters of standard SQL servers by configuring them in specific tiers with different replication settings (synchronous for hot standby, asynchronous for warm standby). This allows off-the-shelf databases to achieve 99.99999% availability without customization by changing how they are deployed and configured rather than modifying the software itself.
2Reliability
If customized configurations and programming are used in data repositories, then read availability of 99.99999% can be achieved, but implementation and scaling become difficult
Solution Approach 1:
The system uses universal, off-the-shelf SQL servers that can be deployed across multiple tiers with different configurations. These standard databases serve multiple functions (primary, hot standby, warm standby) through replication, eliminating the need for customized database software and simplifying implementation and scaling.
Solution Approach 2:
The system establishes hot standby and warm standby databases in advance with pre-configured replication relationships. When failures occur, failover to these pre-prepared standbys is immediate, achieving 99.99999% availability without requiring complex real-time reconfiguration or customization during operations.
3Adaptability or versatility
If standard SQL servers are used without customization, then flexibility and ease of implementation improve, but achieving 99.99999% read availability becomes difficult
Solution Approach 1:
The patent adds a temporal dimension to database availability by creating multiple tiers with different replication time characteristics (synchronous hot standby for immediate failover, asynchronous warm standby for later recovery). This multi-dimensional approach allows standard SQL servers to achieve 99.99999% availability through architectural design rather than software customization.
Solution Approach 2:
The system creates multiple copies of the primary database across different tiers (hot standby copy, warm standby copy) with different replication characteristics. These copies provide redundancy and failover capability, enabling standard SQL servers to achieve enterprise-grade availability through replication rather than customization.
4Reliability
If layered database architecture with multiple backup tiers is implemented, then data availability and flexibility improve, but system complexity increases
Solution Approach 1:
The replication between tiers is configured to operate autonomously using standard SQL server capabilities. The hot standby tier synchronously replicates from primary, and the warm standby tier asynchronously replicates from primary or hot standby, creating a self-managing hierarchical structure that reduces operational complexity despite the multi-tier architecture.
Data Source
AI summary
The present disclosure generally relates to providing extremely high read availability for data repositories within a telecommunication network. Systems described herein implement a novel architecture and backup scheme in connection with non-customized data servers to provide at least 99.99999% read availability within a telecommunication network. In one or more examples, the novel architecture includes a primary database and hot backup database that mirrors the primary database. Additionally, the novel architecture further includes a tepid backup database that stores asynchronous snapshot replications of the primary database that are sent to the tepid backup database out-of-band. In the event of a cascading failure that affects the primary database and the hot backup database, the best snapshot replication stored by the tepid backup database is initialized to service a read request that would otherwise have failed.