Hybrid Data Replication Switching Between Snapshot and Continuous Modes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current database replication technologies are limited by mutual exclusivity between continuous and snapshot replication methods, which can compromise performance and flexibility, especially in environments where switching between these methods is necessary based on varying activity levels.
Innovation Solution
A hybrid data replication system that combines snapshot and continuous replication approaches, allowing automatic switching between them while maintaining transactional consistency, enabling flexible replication strategies without impacting performance or data integrity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If continuous replication is used, then data availability and near real-time protection are improved, but resource consumption and system overhead increase
Solution Approach 1:
The system dynamically switches between continuous and snapshot replication modes based on real-time conditions such as data change rates, network status, and resource availability. This allows the replication mechanism to adapt its resource consumption level while maintaining appropriate data availability, resolving the contradiction between reliability and energy use.
Solution Approach 2:
The system changes the replication parameter (continuous vs. snapshot) based on varying operational conditions. When data change rates are low or resources are constrained, it switches to snapshot replication; when real-time protection is critical, it uses continuous replication. This parameter adjustment resolves the contradiction by matching resource consumption to actual needs.
2Use of energy by moving object
If snapshot replication is used, then resource consumption is reduced, but data freshness and real-time protection capability deteriorate
Solution Approach 1:
The system dynamically adjusts the replication mode based on the required data freshness. When applications require real-time data, the system switches to continuous replication; when near-real-time is sufficient, it uses snapshot replication. This dynamic adaptation resolves the contradiction between resource consumption and data freshness.
3Productivity
If materialization is performed before replication, then replication can proceed immediately, but system downtime and unavailability increase
Solution Approach 1:
The system performs preliminary actions (snapshot creation, log preparation) in the background before switching to continuous replication, minimizing the impact on system availability. By preparing replication data in advance without requiring full materialization downtime, the system achieves both fast replication initiation and high availability.
4Adaptability or versatility
If switching between replication methods is enabled, then flexibility and adaptability are improved, but system complexity increases
Solution Approach 1:
The system uses feedback mechanisms to automatically monitor replication performance, data change rates, and resource usage, then switches between continuous and snapshot replication based on this feedback. This automated feedback-based switching provides flexibility without requiring complex manual configuration or intervention, resolving the contradiction between adaptability and system complexity.
Data Source
AI summary
System, method, computer program product embodiments and combinations and sub-combinations thereof for hybrid data replication are described. Aspects include identifying a type of database data replication, the type including a combination of replication approaches, and managing replication based on the identified type, including coordinated switching from one replication approach to another automatically with transactional consistency maintained among source and target databases.