Observable Data Object for Graph Data Unmarshalling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems face inefficiencies in transparent asynchronous on-demand unmarshalling of graph data, particularly in recreating graph structures on client devices without maintaining the graph structure during data transfer from graph databases, leading to unnecessary re-creation and potential synchronization issues across different platforms.
Innovation Solution
A Graphs Manager is implemented to inspect the authoritative model, generate client-side object models using reflection, and provide metadata for reconstructing graph objects on the client device, along with an observable data object to check for local existence before retrieving data from the server, optimizing data retrieval and reducing the need for platform-specific model rewriting.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If graph data is transferred from graph database to client device without maintaining graph structure, then data transfer simplicity is improved, but unnecessary re-creation of graph structures is required on client side
Solution Approach 1:
The patent applies preliminary action by pre-generating client-side object models and metadata on the server side before data transfer. The Graphs Manager inspects the authoritative model and creates ready-to-use client-side representations, so that when data is transferred to the client device, the structural framework is already in place, eliminating the need for time-consuming re-creation of graph structures on the client side.
2Reliability
If graph structure is maintained during data transfer, then synchronization across platforms is improved, but data transfer complexity increases
Solution Approach 1:
The patent uses an intermediary approach by introducing metadata as a mediator between the server-side graph database and client-side applications. The Graphs Manager generates metadata that describes the graph structure, which travels with the data during transfer. This metadata acts as an intermediary that enables automatic reconstruction of graph structures on the client side without requiring complex transfer protocols, thus maintaining synchronization while keeping data transfer relatively simple.
3Adaptability or versatility
If client device retrieves all graph data from server, then data availability is improved, but unnecessary data transfer occurs for locally existing objects
Solution Approach 1:
The patent implements feedback by having the observable data object check with the client device's local storage to determine whether a copy of the requested data object already exists. This feedback mechanism allows the system to adapt its data retrieval behavior: if the object is already present locally, no additional data transfer occurs; if not, the data is retrieved from the server. This eliminates unnecessary data transfer and energy consumption while maintaining data availability when needed.
4Adaptability or versatility
If platform-specific model rewriting is performed, then platform compatibility is improved, but development time and complexity increase
Solution Approach 1:
The patent applies the copying principle by generating client-side object models that are platform-specific copies tailored to each target platform's requirements. The Graphs Manager inspects the authoritative model and creates appropriate client-side representations for different platforms (e.g., Java, Python, JavaScript) based on metadata. This allows platform compatibility to be achieved through automated code generation and model transformation, significantly reducing development time and complexity compared to manual model rewriting for each platform.
Data Source
AI summary
Implementations of the disclosure provide for receiving, by a processing device, a request for a first data object associated with graph data elements and a metadata of a graph model, inspecting an observable data object to identify whether a copy of the first data object exists on a storage device associated with the processing device, responsive to failing to identify the copy of the first data object on the storage device, transmitting a service request to a host computer for the graph data elements, the service request comprising an identifier of the first data object, responsive to receiving the graph data elements from the host computer, retrieving, from the storage device, the metadata identified by a first reference stored in the observable data object, generating the first data object using the graph data elements and the metadata, and presenting the first data object on a display device.