Dynamic API Selection for Converged Infrastructure Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional methods for managing multiple APIs in converged infrastructures are inefficient and labor-intensive due to the need for static configuration of each API for heterogeneous computing resources, lacking resiliency and robustness.

Innovation Solution

A system that dynamically selects an API for a computing component within a converged infrastructure based on various selection metrics, such as failure rates, response latency, and API capabilities, using a dynamic API selection component and a communication services component to enable communication between the component and management software.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If static configuration of each API for each computing component is used, then API compatibility is ensured, but configuration time and labor increase significantly

Engineering Contradiction:
ImproveAPI compatibilityVSAvoidconfiguration time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system enables self-service by allowing computing components to automatically select and configure their own APIs through dynamic discovery mechanisms. The component publishes its capabilities and requirements, and the management software autonomously matches them with appropriate APIs from available providers, eliminating manual configuration efforts while ensuring compatibility through systematic matching criteria.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system changes the approach from static to dynamic parameter configuration. Instead of pre-configuring fixed API mappings, the system continuously evaluates component states, performance metrics, and availability conditions to dynamically adjust API selections. This allows the configuration to adapt to changing system conditions while maintaining compatibility through real-time validation.

Inventive Principle:
Principle #35Parameter changes

2Productivity

If multiple heterogeneous computing resources are included in converged infrastructure, then resource utilization efficiency improves, but system complexity increases

Engineering Contradiction:
Improveresource utilization efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system implements universality by creating a common framework that handles diverse computing resources through standardized mechanisms. The dynamic API selection system provides universal interfaces that work across different component types, and the automated discovery and matching processes apply uniformly regardless of resource heterogeneity, allowing efficient utilization without proportionally increasing management complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system introduces intermediary layers including API providers, component capability registries, and automated matching services that mediate between heterogeneous resources and management functions. These intermediaries abstract the complexity of diverse component interfaces, presenting unified access points while handling the intricacies of resource-specific protocols and requirements behind the scenes.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Manufacturing precision

If manual API configuration is performed for each component, then configuration accuracy is maintained, but labor intensity increases

Engineering Contradiction:
Improveconfiguration accuracyVSAvoidlabor intensity
Core Design Contradiction:
Manufacturing precisionVSEase of manufacture

Solution Approach 1:

The system implements feedback mechanisms where component capability information, API performance metrics, and matching results are continuously monitored and used to refine future selections. The automated system learns from configuration outcomes and performance data, adjusting its matching algorithms to improve accuracy over time while reducing the need for manual intervention in configuration decisions.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system replaces manual mechanical configuration processes with automated computational systems. Instead of human operators manually matching components to APIs, the system uses automated discovery, evaluation, and selection algorithms that process component capabilities and API characteristics computationally, maintaining precision through systematic evaluation while eliminating labor-intensive manual configuration tasks.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

4Reliability

If dynamic API selection is implemented, then system resiliency improves, but selection complexity increases

Engineering Contradiction:
Improvesystem resiliencyVSAvoidselection complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system embraces dynamics by implementing flexible, adaptable API selection mechanisms that respond to changing system conditions. The selection process continuously evaluates component states, API availability, and performance metrics to dynamically adjust choices, enabling the system to adapt to failures, load changes, and resource availability variations, thereby improving resiliency through responsive reconfiguration.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system applies segmentation by breaking down the complex selection process into distinct modular components: capability discovery, requirement analysis, matching algorithms, validation, and execution. Each segment handles a specific aspect of the selection process independently, making the overall complex system manageable through clear separation of concerns while maintaining the ability to dynamically select APIs based on integrated evaluation of all segments.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10216548B1Dynamic and adaptive programmatic interface selection (DAPIS)
Publication Date: 2019.02.26 EMC IP HLDG CO LLC
  • US10216548B1 patent drawing
  • US10216548B1 patent drawing
  • US10216548B1 patent drawing

AI summary

Aspects of the present disclosure involve converged infrastructures, and more particularly, systems that automatically select an application programming interface for use in connecting one or more components of the converged infrastructure with management software. Component information is obtained for a particular component within the converged infrastructure. The component information is used in conjunction with various selection metrics to identify an applicable application programming interface.