Resource Management Broker for Dynamic URI Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current resource management systems face complexity and inefficiency in handling hierarchical collections and dynamic members, leading to barriers in modularity and robustness due to the need for static mapping of URI paths, which is inadequate for dynamic changes in collection members.
Innovation Solution
A resource management system with a broker and multiple providers that receives URI requests, determines the last collection in the hierarchy, and forwards the request directly to the appropriate provider for processing, eliminating the need for static mapping and enabling handling of dynamic changes in collection members.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If static mapping mechanism is used to route URI requests, then the system has a clear routing path, but the system cannot handle dynamic changes in collection members and requires complex provider configuration
Solution Approach 1:
The patent replaces the static mapping mechanism with a dynamic routing approach where the broker evaluates URI requests at runtime and determines the appropriate provider based on current collection membership. This allows the system to adapt to dynamic changes without requiring complex static configuration, as the routing logic automatically adjusts to the current state of collections and their members.
Solution Approach 2:
The broker acts as an intermediary between URI requests and providers, introducing a new component that handles the routing decision-making process. This intermediary layer absorbs the complexity of dynamic routing logic, allowing providers to remain simple and focused on their specific processing functions while the broker manages the adaptability to dynamic collection changes.
2Ease of operation
If topmost collection providers are configured to handle all sub-collections and dynamic members, then routing is possible, but modularity and robustness are reduced
Solution Approach 1:
The patent segments the routing functionality from the provider logic by introducing the broker as a separate component. This segmentation allows providers to be modular and focused on specific collection types or members, while the broker handles the complex routing decisions. Each provider can be independently configured and maintained, improving modularity and robustness without sacrificing routing capability.
Solution Approach 2:
The broker provides a universal routing mechanism that works across all collections and providers, eliminating the need for each provider to implement complex routing logic for all sub-collections. This multi-functional broker handles diverse routing scenarios uniformly, simplifying provider configuration and improving the overall modularity of the system.
3Adaptability or versatility
If static file mapping is used for URI paths, then the routing structure is simple, but hierarchical collections and dynamic members cannot be adequately handled
Solution Approach 1:
The patent replaces static file mapping with dynamic routing logic in the broker that evaluates URI requests at runtime. This dynamic approach enables proper handling of hierarchical collections by evaluating the URI path structure and matching it against the actual hierarchy of collections and members at the time of the request, rather than relying on predetermined static mappings.
Data Source
AI summary
A resource management system that includes at least one managed computing system including a plurality of hierarchal computer resources and a server computing system that is coupled to the at least one managed computing system through a network. The server computing system includes a broker in communication with a plurality of providers. The broker is configured to receive a Uniform Resource Identifier (URI) request for a first resource of the plurality of hierarchal computer resources included in the at least one managed computing system. The URI request includes a resource path that identifies the first resource by a hierarchy of a plurality of collections. The broker is configured to determine a last collection in the hierarchy of the plurality of collections that matches a first provider of the plurality of providers, and forward the request directly to the first provider such that the first provider processes the URI request.