Front-End Remote Replication to Offload Primary Server Resources
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing remote replication systems consume a large amount of computing and memory resources of the primary server during data transmission between different nodes.
Innovation Solution
Implement a front-end unit to manage data synchronization, allowing the primary server to record and determine to-be-synchronized data without direct access, reducing the need for memory and computing resources by handling replication tasks independently.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the primary server directly manages remote replication, then data synchronization can be performed, but computing resources and memory resources are severely consumed
Solution Approach 1:
The system segments the remote replication function into a独立的 front-end unit that handles data recording, tracking, and synchronization. This separates the replication management tasks from the primary server's core data storage functions, allowing the primary server to focus on reliable data storage while the front-end unit handles the computationally intensive replication tasks.
Solution Approach 2:
The front-end unit acts as an intermediary between the primary server and secondary server. It records data changes, determines to-be-synchronized data, and manages the synchronization process, thereby reducing the direct computational burden on the primary server while ensuring data synchronization reliability.
2Reliability
If the primary server stores all written data, then data availability is ensured, but memory resources are consumed
Solution Approach 1:
The system extracts the function of tracking and managing written data from the primary server and places it in the front-end unit. The front-end unit records data changes and maintains the information needed for synchronization, allowing the primary server to store only the actual data without the overhead of replication management structures.
3Productivity
If the primary server processes write requests and performs remote replication, then complete data management is achieved, but computing resources are consumed
Solution Approach 1:
The system divides data management tasks into two segments: the primary server handles data storage and availability, while the front-end unit handles replication management including tracking written data and determining synchronization needs. This segmentation maintains complete data management functionality while reducing the computational load on any single component.
Solution Approach 2:
The front-end unit autonomously performs replication management tasks including recording data changes, determining to-be-synchronized data based on synchronization rules, and coordinating with the secondary server. This self-service capability eliminates the need for the primary server to directly manage replication, reducing its computing resource consumption.
Data Source
AI summary
A remote replication system includes a primary server, a secondary server, and a front-end apparatus. The front-end apparatus is configured to: receive a write request, and return a write result after determining that data corresponding to the write request is successfully written into the primary server; record data that is successfully written into the primary server each time; and when a preset synchronization rule is met, determine to-be-synchronized data from the recorded data, and send the to-be-synchronized data to the secondary server. The primary server is configured to store the data written by the front-end apparatus. The secondary server is configured to store the to-be-synchronized data sent by the front-end apparatus.