API Call Consolidation for Web Application Latency Reduction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Web application quality of experience (QoE) is often compromised due to the inefficiencies in API call optimizations, as development teams rarely consolidate frequent API calls, leading to increased latency and poor user experience.

Innovation Solution

A device analyzes trace data to identify frequently co-occurring API calls, quantifies the latency savings from consolidating these calls into singular calls, and provides recommendations to users for implementing these consolidations, thereby reducing network-related latency issues.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If multiple small API calls are made separately to fulfill web application requests, then the application can access required data from different services, but the cumulative latency increases and quality of experience deteriorates

Engineering Contradiction:
ImproveAPI call efficiencyVSAvoidcumulative latency
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent combines multiple frequently co-occurring API calls into a single consolidated API call. The system analyzes trace data to identify patterns where multiple API calls are made in sequence, then creates a unified call that retrieves all required data in one request, eliminating the cumulative latency of multiple separate round trips between client and server.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent performs preliminary analysis of API call patterns by examining trace data to identify frequently co-occurring calls. This upfront analysis enables the system to pre-determine which API calls should be consolidated, so that when consolidation is implemented, the most beneficial combinations are already identified and ready for optimization.

Inventive Principle:
Principle #10Preliminary action

2Ease of operation

If development teams focus on their own responsibilities without concerted effort to optimize API calls, then each team can maintain their own code quality, but overall application performance suffers due to unoptimized API call patterns

Engineering Contradiction:
Improvedevelopment team autonomyVSAvoidapplication performance
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The patent implements a feedback mechanism that provides developers with actionable recommendations for API call consolidation. The system analyzes actual runtime trace data, identifies optimization opportunities, and presents specific recommendations to developers. This feedback loop enables teams to maintain autonomy while improving overall application performance through data-driven optimization suggestions.

Inventive Principle:
Principle #23Feedback

3Speed

If API calls are consolidated into fewer calls, then network latency is reduced and throughput improves, but the complexity of analyzing and managing API call patterns increases

Engineering Contradiction:
Improveapplication response speedVSAvoidAPI optimization system complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The patent implements a self-service approach where the system automatically analyzes trace data, identifies consolidation opportunities, and generates optimization recommendations without requiring manual intervention. The automated analysis of call patterns and generation of consolidation suggestions reduces the complexity burden on developers while still achieving performance improvements.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS20240394121A1API consolidation recommendations to improve web application qoe
Publication Date: 2024.11.28 CISCO TECHNOLOGY INC
  • US20240394121A1 patent drawing
  • US20240394121A1 patent drawing
  • US20240394121A1 patent drawing

AI summary

In one embodiment, a device obtains trace data indicative of application programming interface calls made during sessions between clients and an application accessible via a network. The device identifies, based on the trace data, a set of calls among the application programming interface calls that are frequently co-occurring. The device quantifies a latency savings expected to occur were the set of calls to be consolidated into a singular call instead of being made separately. The device provides, to a user interface, a recommendation to consolidate the set of calls into a consolidated call that indicates the latency savings.