Service Registry Object Pruning via Depth and Format Mapping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Service registry and repository systems face challenges in efficiently managing complex collections of objects, particularly in returning only the required subset of objects while avoiding exposure of internal storage mechanisms and user-defined relationships.
Innovation Solution
A method is introduced that translates database path queries into object queries, returns a hierarchical collection of objects within a specific depth from the root object, and maps objects from a proprietary format into a standard format like Service Definition Object (SDO), thereby limiting the exposure of internal relationships and user-defined relationships.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If the service registry returns the complete collection of objects from the repository, then the user receives all available data, but the user-defined relationships and internal storage mechanisms are exposed and the data transfer becomes inefficient
Solution Approach 1:
The patent extracts only the necessary objects and their essential properties from the complete collection, excluding user-defined relationships and internal storage mechanisms. The pruning mechanism selectively removes unnecessary objects based on the query requirements, returning only the relevant subset to the user.
Solution Approach 2:
The patent segments the complete object collection into relevant and irrelevant portions based on the query parameters. The pruning mechanism divides the data set and selectively returns only the segments that match the query criteria, excluding segments containing user-defined relationships.
2Loss of information
If the service registry returns all objects in the collection, then no data is lost, but the query performance deteriorates and unnecessary data is transferred
Solution Approach 1:
The patent extracts only the essential objects needed to answer the query, removing unnecessary objects from the result set. This extraction process maintains data completeness for the required information while eliminating redundant data that would slow down query performance.
3Ease of operation
If the service registry exposes user-defined relationships to users, then the internal storage mechanism becomes transparent, but security and data integrity are compromised
Solution Approach 1:
The patent introduces a pruning mechanism as an intermediary between the repository and the user. This mediator translates user queries into repository queries, retrieves the complete set, and then prunes it to remove user-defined relationships before returning results, thus protecting data integrity while maintaining ease of operation.
4Loss of information
If the service registry returns the complete object collection, then all information is available, but the network bandwidth is wasted transferring unnecessary data
Solution Approach 1:
The patent extracts and returns only the necessary objects and their essential properties, excluding unnecessary data such as user-defined relationships. This extraction minimizes the amount of data transferred over the network while ensuring all required information is available to the user.
Data Source
AI summary
This invention relates to a service registry and repository system, method and computer program product for accessing objects in an object repository. There is provided a method of managing an object database for objects comprising: receiving an object query; querying the object database using the object query; receiving a hierarchical collection of objects including a root object; and returning only those objects that are within a specific depth of the root object and that do not represent user-defined relationships. The returning step maps the objects from a proprietary object format into a standard object format and optionally the standard object format is the Service Definition Object format (SDO).