Object Metadata Routing for Distributed Server Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In distributed computing environments, identifying the server responsible for providing access to an object without relying on centralized dispatching nodes or detailed access-type/object mappings is challenging, especially in scenarios where interdependencies span multiple hierarchical levels, leading to difficulties in efficient and logical support for additional levels of abstraction.
Innovation Solution
The method involves associating metadata with objects to identify the current server responsible for access, allowing requests to be directed to the appropriate server without a centralized dispatching node, using metadata-annotated objects that provide action/address pairs for service requests, enabling distributed and secure access.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a centralized dispatching node is used to identify the server responsible for providing access to an object, then request routing can be managed centrally, but the system creates a single point of failure and increases overhead
Solution Approach 1:
The patent extracts the server identification information from the centralized dispatching node and embeds it directly into metadata associated with each object. This allows requesting entities to determine the responsible server independently without relying on centralized routing, thereby eliminating the single point of failure while reducing routing overhead
Solution Approach 2:
The system enables requesting entities to self-determine the responsible server by retrieving and processing metadata associated with the object. This self-service approach eliminates the need for centralized dispatching, improving reliability by removing the single point of failure and reducing system overhead
2Ease of operation
If detailed mappings of access-type/object pairs to servers are maintained, then accurate request routing is achieved, but the system increases overhead and complexity
Solution Approach 1:
The patent performs preliminary action by pre-computing and storing server identification information in metadata associated with each object. This allows requesting entities to efficiently determine the responsible server through simple metadata retrieval and processing, avoiding the need to maintain and query complex detailed mappings of access-type/object pairs to servers
Solution Approach 2:
The system creates a simplified copy of the routing information by embedding server identification data directly in the object's metadata. This copy contains only the essential information needed for routing, eliminating the need to maintain and process complex detailed mappings while preserving routing accuracy
3Reliability
If centralized dispatching nodes are used to manage access, then access control can be coordinated, but sensitive configuration information must be exposed and security risks increase
Solution Approach 1:
The patent extracts only the necessary server identification information from the centralized dispatching node and places it in object metadata. This allows access control to be coordinated through metadata retrieval without exposing sensitive configuration information that would be required in a centralized dispatching architecture
Solution Approach 2:
The system enables requesting entities to independently determine the responsible server through metadata retrieval and processing. This self-service approach maintains access control reliability while eliminating the need to expose sensitive configuration information to centralized nodes, thereby reducing security risks
Data Source
AI summary
The present application is directed to methods and systems that provide for identification of a server, within a distributed computing environment, through which an object can be accessed. The object is associated with metadata that identifies a server currently responsible for providing access to the object. By these methods and system, a request to access an object can be directed to an appropriate server, without first accessing a centralized dispatching node and without access to detailed mappings of access-type/object pairs to servers in a distributed computing environment.