Dynamic API Call Conversion for Cloud Scalability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

API management in cloud environments faces challenges such as security, scalability, integration, documentation, monitoring, and governance, with scalability being one of the biggest challenges due to the need to handle large volumes of traffic and sudden spikes in demand without crashing or slowing down.

Innovation Solution

The techniques involve collecting data on variables related to converting synchronous API calls to asynchronous API calls, analyzing these data to determine relationships between the variables, and making a determination on whether to convert the synchronous API calls to asynchronous API calls based on the analysis, thereby optimizing API system scalability in cloud environments.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If synchronous API calls are used, then response accuracy is maintained, but system scalability deteriorates under high traffic volumes

Engineering Contradiction:
Improveresponse accuracyVSAvoidsystem scalability
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system dynamically switches between synchronous and asynchronous API call modes based on real-time traffic conditions and service characteristics. This allows the system to adapt its processing mode to current load levels, maintaining reliability when needed while enabling scalability during high traffic periods.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent changes the operational parameter of API call timing from synchronous (immediate response required) to asynchronous (delayed response acceptable), thereby transforming the system's ability to handle traffic volumes while maintaining acceptable response accuracy through selective use of each mode.

Inventive Principle:
Principle #35Parameter changes

2Productivity

If asynchronous API calls are implemented, then system scalability is improved, but response time increases

Engineering Contradiction:
Improvesystem scalabilityVSAvoidresponse time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system applies asynchronous processing partially - only to API calls where delayed response is acceptable based on service type and traffic conditions. Critical time-sensitive calls remain synchronous, while non-critical calls use asynchronous processing, achieving scalability improvement without excessive response time delays across all operations.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The patent introduces an intermediary decision-making layer that evaluates each API call and determines whether synchronous or asynchronous processing is appropriate. This intermediary mechanism balances scalability needs with response time requirements by routing calls appropriately based on service characteristics and current system state.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If more infrastructure resources are allocated, then API scalability is improved, but system cost increases

Engineering Contradiction:
ImproveAPI scalabilityVSAvoidinfrastructure resources
Core Design Contradiction:
ProductivityVSQuantity of substance

Solution Approach 1:

The system performs self-service by automatically analyzing its own traffic patterns and service characteristics to determine optimal API call timing modes. This self-analysis capability enables the system to achieve scalability improvements through intelligent processing mode selection rather than requiring proportional increases in infrastructure resources.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent changes the operational parameter of API call timing to optimize resource utilization. By transforming certain calls from synchronous to asynchronous mode, the system achieves better scalability with existing infrastructure resources rather than requiring additional hardware or computing capacity.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS20250130870A1Optimizing application programming interface system scalability in a cloud environment
Publication Date: 2025.04.24 CISCO TECHNOLOGY INC
  • US20250130870A1 patent drawing
  • US20250130870A1 patent drawing
  • US20250130870A1 patent drawing

AI summary

In one embodiment, a method herein comprises: collecting, by a process, data corresponding to one or more variables used to measure convertibility of a particular synchronous application programming interface call into an asynchronous application programming interface call; performing, by the process, an analysis on the data to determine relationships between the one or more variables; making a determination, by the process and based on the analysis, as to whether to convert the particular synchronous application programming interface call to the asynchronous application programming interface call; and converting, by the process and based on the determination, the particular synchronous application programming interface call to the asynchronous application programming interface call.