Data Subscription Management System for Consistent Data Synchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data management systems face challenges in maintaining data consistency across source and subscribing systems, leading to issues like rogue and orphan data due to inconsistent deletion processes and lack of synchronization.
Innovation Solution
A Data Subscription Management System (DSMS) is implemented to manage data dissemination, prevent rogue data, and ensure data integrity by flagging deletion requests, sending requests for responses to subscribing systems, and only proceeding with deletion after all dependencies are resolved.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If data is distributed to subscribing systems, then data consumption and usage functionality is improved, but data consistency and integrity deteriorate due to rogue copies and orphan data
Solution Approach 1:
The patent implements a feedback mechanism where the source system receives notifications from subscribing systems when they receive or delete data objects. This feedback loop enables the source system to track the status of distributed data and maintain consistency by knowing which copies exist and their current state, thereby preventing rogue copies while allowing widespread data consumption.
Solution Approach 2:
The patent introduces an intermediary notification mechanism that mediates between the source system and subscribing systems. This intermediary communication channel ensures that deletion requests and data status changes are properly propagated and acknowledged, preventing data inconsistency without restricting data distribution to multiple subscribing systems.
2Loss of substance
If source system deletes data locally, then data storage efficiency is improved, but data inconsistency worsens due to rogue copies remaining at subscribing systems
Solution Approach 1:
The patent applies preliminary action by sending deletion notifications to subscribing systems before the source system actually deletes the data locally. This ensures that all subscribing systems have a chance to delete their copies first, preventing rogue copies from remaining. Only after receiving confirmation from all subscribing systems does the source system proceed with local deletion, maintaining both storage efficiency and data consistency.
Solution Approach 2:
The deletion process implements feedback where subscribing systems notify the source system when they have deleted their copies. This feedback mechanism allows the source system to track deletion progress and only perform local deletion after confirming all distributed copies have been removed, thereby eliminating rogue copies while improving storage efficiency.
3Ease of operation
If subscribing systems independently manage their data copies, then system autonomy and operation ease are improved, but data synchronization and consistency deteriorate
Solution Approach 1:
The patent introduces an intermediary notification protocol that mediates between independent subscribing systems and the source system. This intermediary mechanism allows subscribing systems to maintain autonomy in managing their local copies while ensuring synchronization through standardized notification exchanges. The intermediary layer handles the coordination of deletions and updates without compromising system independence.
Solution Approach 2:
The patent implements feedback mechanisms where subscribing systems autonomously manage their data but provide feedback notifications to the source system about their data status. This feedback enables automatic synchronization without requiring centralized control, maintaining system autonomy while ensuring data consistency through automated response to notifications.
4Reliability
If transaction deletion is sent to subscribing systems, then data consistency is improved, but system complexity and operation difficulty worsen due to coordination overhead
Solution Approach 1:
The patent extracts the coordination complexity from the core data management operations by implementing a separate, dedicated notification mechanism. Instead of embedding complex coordination logic within data transactions, the system uses a simplified notification protocol that handles synchronization separately. This extraction reduces the complexity of individual operations while maintaining overall data consistency through the dedicated notification channel.
Solution Approach 2:
The patent uses an intermediary notification system that simplifies the coordination between source and subscribing systems. Rather than requiring complex transaction protocols, the intermediary mechanism handles deletion coordination through simple notification and acknowledgment messages, reducing system complexity while ensuring data consistency across all systems.
Data Source
AI summary
A method includes a digital subscription management system (DSMS) receiving from a source system a request to perform an edit of at least one data object, the DSMS sending a request for response (RFR) to subscribing systems having a copy of the at least one data object, the DSMS receiving a response from the subscribing systems, and the DSMS performing the edit.