Adaptive API Call Balancing for Cloud Tenants
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional cloud computing systems impose uniform API call rate limits, which can negatively impact the quality of service for cloud tenants by treating all API calls equally, regardless of their type or revenue generation potential, leading to reduced functionality and revenue for cloud service providers.
Innovation Solution
Implementing an adaptive API call balancing system that allows API calls based on their revenue and cost difference, using a management server to determine whether executing an API call would generate additional revenue for the cloud provider, and rejecting calls that do not meet a threshold average difference.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of energy
If uniform API call rate limits are imposed on all cloud tenants, then system resource consumption is controlled, but quality of service deteriorates due to treating all API calls equally regardless of revenue generation potential
Solution Approach 1:
The patent implements differential rate limiting where different API calls are subject to different rate limits based on their characteristics. Revenue-generating API calls receive higher rate limits while non-revenue-generating calls receive lower limits. This local differentiation resolves the contradiction by optimizing resource allocation for each API call type rather than applying uniform restrictions.
Solution Approach 2:
The system dynamically adjusts the rate limit parameter based on API call characteristics such as revenue potential, call type, and tenant history. By changing the rate limit parameter adaptively rather than maintaining a fixed uniform limit, the system controls resource consumption while preserving quality of service for valuable API calls.
2Productivity
If API call rate limits are increased to improve quality of service, then revenue generation improves, but system resource consumption increases
Solution Approach 1:
The patent applies higher rate limits specifically to revenue-generating API calls while maintaining lower limits for non-revenue calls. This selective approach increases productivity and revenue generation without proportionally increasing overall resource consumption, as only valuable API calls receive elevated rate limits.
Solution Approach 2:
The system adjusts the rate limit parameter dynamically based on the revenue potential of each API call. High-value calls receive increased rate limits to maximize revenue generation, while low-value calls receive restricted limits to control resource consumption, optimizing the productivity-resource consumption tradeoff.
3Device complexity
If all API calls are treated equally with uniform rate limits, then system simplicity is maintained, but functionality is reduced due to inability to prioritize revenue-generating calls
Solution Approach 1:
The patent introduces differentiated rate limiting based on API call characteristics, creating local variations in policy application. This adds functionality by enabling prioritization of revenue-generating calls while maintaining relative system simplicity through rule-based differentiation rather than complex adaptive algorithms.
Data Source
AI summary
A management server may receive a first application programming interface (API) call from a client device, and determine a first API difference value between a revenue resulting from an execution of the first API call and an amount of resources to be involved in the execution of the first API call. The management server may also calculate an average difference value of API calls received from the client device in view of the first API difference value and previous API difference values determined for previous API calls received from the client device. The management server may further determine whether the average difference value satisfies a threshold. In response to determining that the average difference value satisfies the threshold, the management server may allow the API call. In response to determining that the average difference value does not satisfy the threshold, the management server may reject the first API call.