Harvester Application Dependency Resolution via Preliminary Search

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cloud-based platforms face challenges in efficiently managing dependencies between computing resource objects during the harvesting process, leading to bottlenecks and delays in resource utilization.

Innovation Solution

A harvester application is used to generate a computing resource collection for a client by identifying and resolving dependencies between computing resource objects. The application defers the resolution of unresolved dependencies until the harvest session is complete, improving efficiency by reducing the need for multiple searches of the resource catalog.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the system resolves dependencies immediately during the harvesting process, then dependency accuracy is improved, but processing time increases due to multiple searches of the resource catalog

Engineering Contradiction:
Improvedependency resolution accuracyVSAvoidharvesting process time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs a preliminary search of the resource catalog to build a complete set of computing resource objects before dependency resolution begins. This preliminary action ensures all objects are available in memory for subsequent dependency matching, eliminating the need for repeated searches during the harvesting process while maintaining accurate dependency resolution

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The search operation is extracted and performed once before the harvesting process begins, separating it from the dependency resolution steps. By taking out the search operation and completing it beforehand, the system avoids multiple redundant searches while ensuring all computing resource objects are available for dependency matching

Inventive Principle:
Principle #2Taking out (Extraction)

2Reliability

If the system performs multiple searches of the resource catalog to resolve dependencies, then dependency resolution completeness is improved, but productivity decreases

Engineering Contradiction:
Improvedependency resolution completenessVSAvoidresource harvesting efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system performs a preliminary search of the resource catalog to build a complete set of computing resource objects before dependency resolution begins. This preliminary action ensures all objects are available in memory for subsequent dependency matching, eliminating the need for repeated searches during the harvesting process while maintaining accurate dependency resolution

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system merges the search operation with the initial setup phase rather than performing separate searches during dependency resolution. By combining these operations and performing the search once upfront, the system achieves complete dependency resolution without the productivity loss from multiple searches

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS20250147942A1Techniques for efficient compute resource harvesting
Publication Date: 2025.05.08 ORACLE INT CORP
  • US20250147942A1 patent drawing
  • US20250147942A1 patent drawing
  • US20250147942A1 patent drawing

AI summary

The present disclosure relates to a system and techniques for resolving dangling references resulting from a dependency relationship between computing resource objects uncovered during a harvesting process. The techniques include, adding a computing resource object from a catalog of computing resource objects to a computing resource collection for a client and identifying one or more dependencies for the computing resource object. The techniques further include determining at least one unresolved dependency from the one or more dependencies, the at least one unresolved dependency including a second dependency on a second computing resource object outside of the computing resource collection. The techniques further include resolving the at least one unresolved dependency after the second computing resource object associated with the unresolved dependency has been added to the computing resource collection.