Data Management System Dependency Resolution
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current storage systems face challenges in efficiently managing dependencies between managed and backend objects, leading to inconsistencies and the need for manual synchronization of data, especially when backend data changes independently of managed data.
Innovation Solution
A computer-implemented method determines dependencies between managed and backend objects, receives backend notifications, and updates identified managed objects based on these dependencies, using business logic to generate tasks and route notifications to task managers for synchronization.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual synchronization methods are used to keep managed data consistent with backend data, then data consistency can be maintained, but system management efficiency deteriorates due to manual intervention requirements
Solution Approach 1:
The system implements automatic dependency resolution where the notification router automatically identifies affected managed objects and routes notifications without manual intervention. The dependency graph structure enables the system to self-manage synchronization by automatically determining which managed objects depend on changed backend objects and routing notifications accordingly, eliminating the need for manual synchronization while maintaining data consistency.
Solution Approach 2:
The system establishes a feedback mechanism where backend object changes generate notifications that are routed back to affected managed objects. The notification router continuously monitors backend objects, detects changes, and automatically feeds back notifications to the appropriate managed objects based on dependency relationships, creating a closed-loop system that maintains consistency automatically.
2Reliability
If comprehensive dependency tracking is implemented between managed and backend objects, then data consistency is improved, but system complexity increases due to the need to monitor and manage numerous dependencies
Solution Approach 1:
The system segments the complex dependency management task into distinct functional components: a dependency graph structure that stores relationships, a notification router that processes changes, and task managers that execute actions. This segmentation allows each component to handle specific aspects of dependency tracking independently, reducing overall system complexity while maintaining comprehensive dependency monitoring.
Solution Approach 2:
The notification router acts as an intermediary between backend objects and managed objects. Instead of directly managing complex relationships between all backend and managed objects, the notification router mediates by receiving notifications from backend objects, consulting the dependency graph, and routing notifications to appropriate managed objects. This intermediary simplifies the system architecture by centralizing the complexity in a single manageable component.
3Extent of automation
If automatic notification routing is implemented to synchronize managed data with backend data, then manual intervention is eliminated, but the initial system setup complexity increases due to dependency graph construction
Solution Approach 1:
The system performs preliminary action by pre-construction of the dependency graph during system initialization. All dependency relationships between backend objects and managed objects are established in advance and stored in the dependency graph structure. This preliminary setup enables the notification router to automatically resolve dependencies during runtime without requiring complex real-time analysis, trading initial setup effort for simplified ongoing operation.
Data Source
AI summary
A method, computer program product, and computing system for determining, at the computing device, one or more dependencies associated with a plurality of managed objects and a plurality of backend objects. One or more backend notifications associated with one or more backend objects of the plurality of backend objects may be received. One or more managed objects of the plurality of managed objects associated with the one or more backend objects of the one or more backend notifications may be identified, based upon, at least in part, the one or more dependencies associated with the plurality of managed objects and the plurality of backend objects. The one or more identified managed objects of the plurality of managed objects may be updated based upon, at least in part, the one or more backend notifications.