Distributed Global Entity Synchronization via Peer-to-Peer Protocol
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for maintaining shared data items across multiple geographically disparate computing systems face challenges in ensuring data availability and synchronization, particularly in the presence of system failures or long latencies, leading to inefficiencies and potential data inconsistencies.
Innovation Solution
Implementing a peer-to-peer synchronization protocol that allows any source peer to distribute local global entity modifications to one or more remote peers, using an entity synchronization engine at each cluster to manage shared data and employing specialized data structures for synchronization, thereby reducing the reliance on conventional replication techniques.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Manufacturing precision
If a centralized repository is used to store shared data items, then data consistency is improved, but system reliability deteriorates because a single point of failure prevents access to shared data
Solution Approach 1:
The patent divides the centralized repository into multiple distributed replicas across different computing systems. Each replica maintains a copy of the shared data item, eliminating the single point of failure while preserving data consistency through synchronization mechanisms. This segmentation allows the system to tolerate failures at individual nodes while maintaining overall availability.
Solution Approach 2:
The patent introduces a quorum-based intermediary mechanism that mediates between multiple replicas to ensure data consistency. When a write operation occurs, the system requires acknowledgment from a quorum number of replicas before confirming the operation. This intermediary layer coordinates updates across distributed replicas, maintaining consistency without relying on a single centralized repository.
2Reliability
If exact copies of data items are stored at each computing system, then system reliability is improved, but data consistency deteriorates when modifications occur at multiple locations
Solution Approach 1:
The patent implements dynamic role assignment where computing systems can switch between being primary (write-capable) and secondary (read-only) nodes based on operational needs and failure conditions. This dynamic behavior allows the system to adapt to changing conditions, maintaining consistency by controlling which nodes can modify data at any given time while preserving availability through flexible node role transitions.
Solution Approach 2:
The patent employs feedback mechanisms through quorum-based acknowledgment systems that monitor and coordinate updates across replicas. When a modification is made, the system receives feedback from other replicas to determine whether the quorum threshold is met, ensuring consistency before confirming the operation. This feedback loop prevents conflicting modifications while maintaining system availability.
3Manufacturing precision
If a master-slave architecture is used to manage data changes, then data consistency is improved, but system reliability deteriorates due to dependency on the master system
Solution Approach 1:
The patent inverts the traditional master-slave hierarchy by allowing any node to become the primary writer through quorum-based consensus rather than designating a fixed master. This inversion eliminates the single point of failure inherent in master-slave architectures while maintaining consistency through the quorum mechanism. Any node can assume the writer role temporarily, distributing the master function across all nodes dynamically.
Solution Approach 2:
The patent enables nodes to self-manage their role transitions and data synchronization without relying on a centralized master. Each node independently monitors the system state and can initiate write operations or assume primary status when appropriate, with the quorum mechanism providing self-service coordination. This eliminates dependency on a master system while maintaining consistency through distributed self-organization.
4Manufacturing precision
If quorum-based techniques are used to manage updates, then data consistency is improved, but system complexity increases due to coordination overhead
Solution Approach 1:
The patent uses parameter changes by adjusting the quorum threshold dynamically based on system conditions, such as the number of active replicas and failure patterns. By changing the quorum parameter adaptively, the system maintains consistency with minimal coordination overhead. This parameter adjustment allows the quorum mechanism to scale efficiently without proportionally increasing complexity, optimizing the balance between consistency and system simplicity.
Data Source
AI summary
Methods, systems and computer program products for data protection across computing infrastructure comprising a plurality of geographically distant computing clusters. The geographically distant computing clusters form a distributed system comprising clusters that are assigned into availability zones. Disaster recovery policies are maintained in each of the availability zones. A first cluster detects a modification of a disaster recovery policy. The modification of the disaster recovery policy that occurred at the first cluster is to be communicated over a wide area network. Synchronization of the disaster recovery policy is accomplished by carrying out a peer-to-peer communication protocol over the wide area network. The peer-to-peer communication protocol comprises issuing a first synchronization request message from a source peer, receiving the first synchronization request message at a remote peer, and issuing a synchronization response message by the remote peer, which in turn is transmitted over the wide area network to the source peer.