Anchored Data Fabric Lifecycle Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Large-scale distributed business applications face significant computing resource drains due to the need to manage and maintain large numbers of real-time data objects, as existing key-value store solutions require explicit removal or refreshing of objects to maintain persistence and availability.
Innovation Solution
A fault-tolerant and efficient data replication and caching mechanism, referred to as a 'data fabric,' allows for autonomous, distributed Object life-cycle management by anchoring objects to a scope with a defined lifecycle, enabling efficient insertion, deletion, and management of objects across multiple computer systems and networks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If explicit removal or refreshing of objects is implemented to maintain persistence and availability, then data availability is improved, but computing resource consumption increases
Solution Approach 1:
The patent implements anchored life-cycle management where objects automatically inherit their lifecycle from anchor objects. When an anchor object is removed, all dependent objects are automatically removed without requiring explicit removal operations. This self-service mechanism eliminates the need for continuous monitoring and manual management, reducing computing resource consumption while maintaining data availability through the anchor-based persistence model.
Solution Approach 2:
The system performs preliminary anchoring actions where objects are pre-associated with anchor objects that define their lifecycle. This preliminary action establishes the dependency relationship in advance, so that when the anchor object is removed, the dependent objects are automatically cleaned up. This prevents resource leaks without requiring continuous active management or periodic refreshing operations.
2Quantity of substance
If large numbers of objects are managed in real-time streaming, then data coverage is improved, but system complexity increases
Solution Approach 1:
The patent merges the lifecycle management of multiple dependent objects into a single anchor object. Instead of managing each object's lifecycle independently, the system combines their lifecycle control through the anchor relationship. When an anchor object is removed, all dependent objects are automatically removed in a single operation, significantly reducing system complexity while managing large numbers of objects in real-time streaming scenarios.
Solution Approach 2:
The anchor object serves as an intermediary that mediates the lifecycle management between the system and large numbers of dependent objects. The anchor object absorbs the complexity of tracking and managing multiple objects, providing a simplified interface where a single removal operation can manage the lifecycle of numerous dependent objects. This intermediary approach reduces system complexity while maintaining comprehensive object management.
Data Source
AI summary
Embodiments manage a lifecycle of distributed data objects from at least a first data fabric node. Embodiments receive a request from a publisher to anchor a scope. Embodiments anchor the scope to an anchor in the first data fabric node to generate an anchored scope, where the anchor includes a previously published first object and a corresponding first lifecycle and anchoring the scope includes registering interest in the first lifecycle of the anchor. Embodiments publish, by the first data fabric node, scope metadata corresponding to the anchored scope. Embodiments then receive a request from the publisher to publish a second object into the anchored scope to define an anchored object, the anchored object including the first lifecycle.