Persistent Store Coordinator for Dynamic Data Store Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional object-storage mapping frameworks are limited in dynamic environments, such as desktop settings, where data stores change frequently, and do not support the dynamic addition or removal of persistent data stores, leading to an inability to synchronize the visible data set with client contexts.
Innovation Solution
A persistent store coordinator manages multiple persistent data stores, allowing dynamic addition or removal of data stores and providing a unified façade to client contexts, enabling seamless communication and synchronization of data across multiple sources.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional object-storage mapping frameworks are used with fixed database configuration, then system stability is maintained, but the system cannot adapt to dynamic addition or removal of persistent data stores
Solution Approach 1:
The patent implements dynamic configuration of persistent data stores by allowing the set of databases to change at runtime. The system transitions from a static, fixed configuration to a dynamic one where data stores can be added or removed based on runtime conditions, directly resolving the contradiction between adaptability and stability.
Solution Approach 2:
The patent segments the data storage system into independent, manageable units (individual persistent data stores) that can be dynamically added or removed. This segmentation allows the system to maintain stability at the framework level while enabling flexibility at the data store level, resolving the contradiction between fixed configuration and dynamic adaptation.
2Adaptability or versatility
If the set of persistent data stores is dynamically changing, then system adaptability is improved, but synchronization of the visible data set with client contexts becomes complex
Solution Approach 1:
The patent introduces an intermediary layer (the object-storage mapping framework) that manages the synchronization between dynamically changing data stores and client contexts. This intermediary abstracts the complexity of synchronization, allowing dynamic data store integration while maintaining manageable complexity through centralized coordination.
Solution Approach 2:
The patent creates a universal synchronization mechanism that handles multiple data stores and client contexts through a single, unified approach. This multi-functional synchronization system can adapt to any combination of data stores being added or removed, reducing complexity by providing a single pattern for handling all synchronization scenarios.
3Adaptability or versatility
If traditional fixed configuration is used, then implementation simplicity is maintained, but the system cannot support dynamic environments such as desktop settings where file systems and network resources change frequently
Solution Approach 1:
The patent implements dynamic detection and integration of file systems and network resources in the desktop environment. The system automatically adapts to changing environmental conditions by dynamically adding or removing data stores based on what is available in the desktop environment, moving from static configuration to dynamic adaptation.
Solution Approach 2:
The patent enables the system to automatically detect and integrate new data stores in the desktop environment without manual configuration. The system serves itself by autonomously adapting to the dynamic desktop environment, detecting available resources, and integrating them as persistent data stores, thereby supporting dynamic environments while maintaining ease of implementation.
Data Source
AI summary
Dynamic management of multiple persistent data stores is disclosed. One or more data objects are associated with a client context, e.g., an instance of a client application program. The one or more data objects are retrieved from one or more of a plurality of persistent data stores and provided to the client context in a manner such that the one or more data objects appear to the client context to come from a single source, even if in fact the objects have been retrieved from two or more different persistent stores.