Master-Slave Data System Ring Topology for High Availability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data center configurations face inefficiencies in data access due to slow and inefficient data migration across centers, particularly in applications where read operations outnumber write operations, leading to potential interruptions and performance issues.
Innovation Solution
A data system architecture featuring a ring topology with one read/write master server handling write and consistent read requests and multiple read master servers for normal read requests, each connected to a slave server, ensuring efficient data replication and access without interruptions by designating specific servers for write operations and utilizing a ring structure for data replication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data migration is performed across data centers to provide fault tolerance, then availability is improved, but data access speed and efficiency deteriorate
Solution Approach 1:
The system segments data access operations into two types: normal read requests handled by local read master servers within the same data center, and consistent read requests handled by the remote read master server in the other data center. This segmentation allows most read operations to proceed quickly without cross-data-center migration, while only consistency-critical operations incur the latency of remote access.
Solution Approach 2:
The patent introduces a read master server in each data center that acts as an intermediary for read requests. This intermediary can satisfy normal read requests locally without requiring data migration from the other data center, thereby maintaining fast access speed while still providing fault tolerance through the backup read master server.
2Reliability
If data is replicated across multiple data centers for high availability, then system reliability is improved, but data migration overhead increases
Solution Approach 1:
The system implements local quality by allowing each data center to independently handle normal read requests using its local read master server. This eliminates the need for continuous data migration across data centers for routine operations, reducing migration overhead while maintaining availability through the distributed architecture.
Solution Approach 2:
The patent applies partial action by performing data migration only when necessary - specifically for consistent read requests that require data from the other data center. Normal read requests are satisfied locally without migration, thus minimizing the time and resources spent on data migration while still providing high availability.
3Device complexity
If a traditional master-slave configuration is used with single-direction data migration, then system simplicity is maintained, but read operation efficiency deteriorates in read-heavy applications
Solution Approach 1:
The read master server in each data center serves multiple functions: it handles normal read requests locally, acts as a backup for the other data center's read master, and can participate in failover scenarios. This multi-functionality improves read operation efficiency without significantly increasing system complexity.
Solution Approach 2:
The patent adds a new dimension to the traditional single-direction migration model by implementing bidirectional read capabilities. Each data center has a read master server that can serve reads locally and also provide reads to the other data center, creating a two-dimensional read access pattern that dramatically improves efficiency for read-heavy applications.
Data Source
AI summary
The present teaching relates to a system, method, medium for a data system, which comprises a plurality of data centers with one read/write master server designated to handle write and consistent read requests and a plurality of read master servers designated to handle normal read requests, wherein the master servers form a ring structure and each is connected to a corresponding slave server. When a data access request is received, a read master communication unit invokes one of the plurality of read master servers in the data system if the received data access request is a normal read request, a main master communication unit invokes the read/write master server if the received data access request is either a write request or a consistent read request. When a response is received from the invoked handling master server, a response processing unit responds to the data access request based on the received response.