API Throttling Control for Virtual Servers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional web services lack an automated mechanism to determine the API-execution-count limiting value for virtual servers, leading to manual and potentially inefficient management of API throttling, which can result in performance issues and penalties when the execution count exceeds predetermined limits.
Innovation Solution
A service system that automatically determines the API-execution-count limiting value per virtual server based on the number of virtual servers and implements a controller to process API calls as errors when the execution count exceeds the set limit, thereby managing API throttling dynamically.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Extent of automation
If manual determination of API-execution-count limiting value is used, then simplicity of implementation is maintained, but automation level and management efficiency deteriorate
Solution Approach 1:
The system automatically determines the API-execution-count limiting value for each virtual server by having the determining unit calculate it based on the number of virtual servers and a reference limiting value. This self-service mechanism eliminates manual configuration while maintaining system simplicity, as the determination is performed autonomously based on readily available system parameters.
Solution Approach 2:
The API-execution-count limiting value is dynamically determined by changing parameters such as the number of virtual servers and the reference limiting value. This allows the system to adapt to different deployment scenarios and load conditions without requiring complex manual configuration, resolving the contradiction between automation and simplicity.
2Adaptability or versatility
If fixed API-execution-count limiting value is used, then system stability is maintained, but adaptability to different virtual server configurations deteriorates
Solution Approach 1:
The API-execution-count limiting value transitions from a fixed parameter to a dynamic one that automatically adjusts based on the number of virtual servers and reference limiting value. This dynamic determination ensures the system adapts to different virtual server configurations while maintaining stability through consistent calculation rules, resolving the contradiction between adaptability and reliability.
Solution Approach 2:
The system segments the overall API-execution-count limiting value into individual allocations per virtual server based on the number of virtual servers. This segmentation approach allows each virtual server to receive an appropriate limiting value while the total system capacity remains stable and controlled, balancing adaptability with reliability.
3Ease of operation
If API-execution-count limiting value is not automatically determined, then system complexity is reduced, but manual management overhead increases
Solution Approach 1:
The determining unit automatically calculates and assigns the API-execution-count limiting value for each virtual server based on the number of virtual servers and reference limiting value. This self-service mechanism eliminates manual determination entirely, reducing both system complexity and management time, as the system performs the determination autonomously without human intervention.
Solution Approach 2:
The system uses parameter changes (number of virtual servers, reference limiting value) to automatically determine the API-execution-count limiting value. This approach simplifies operation by replacing manual configuration with automatic parameter-based calculation, significantly reducing the time and effort required for API throttling management while maintaining system simplicity.
Data Source
AI summary
A service system includes a determining unit configured to determine an API-execution-count limiting value per virtual server on a basis of the number of the virtual servers on which a web service is implemented and an API-execution-count limiting value, and a controller configured to provide the web service or to process the call of the API as an error whether the number of times the API has been executed exceeds the API-execution-count limiting value.