API Server Service Tier Validation via Intermediary
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing techniques face challenges in efficiently determining the appropriate service tier for API requests, leading to increased complexity and resource usage, particularly in managing different service levels and coordinating subscription information across multiple servers.
Innovation Solution
The proposed solution involves a method where an API server receives a request, validates the API authorization identifier, determines the service tier based on the request, and transmits a response including the validation result and the service tier indicator to the API server, thereby improving resource management and response efficiency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If the API server determines service tier information locally for each request, then the service tier can be accurately identified, but the computing resources and time required increase significantly
Solution Approach 1:
The validation server performs preliminary action by determining service tier information in advance during the validation process, before the API server needs to process the request. This preliminary determination of service tier allows the API server to receive pre-processed information and reduce its processing requirements, thereby maintaining accuracy while improving overall system efficiency.
Solution Approach 2:
The validation server acts as an intermediary between the client device and the API server. It receives the API request, determines the service tier information, and transmits this pre-determined information back to the API server. This intermediary role eliminates the need for the API server to perform resource-intensive service tier determination locally, resolving the contradiction between accuracy and processing efficiency.
2Ease of operation
If the client device is involved in selecting service tier, then service tier information can be determined, but the complexity of coordinating subscription information across multiple servers increases
Solution Approach 1:
The validation server serves as an intermediary that handles the complex coordination of subscription information. Instead of requiring the client device to manage service tier selection and subscription coordination, the validation server receives the API request, determines the service tier based on subscription information, and provides this information to the API server. This intermediary approach simplifies the client device's role while maintaining ease of operation.
Solution Approach 2:
The complex service tier determination function is extracted from the API server and relocated to the validation server. By taking out the service tier determination logic from the API server's request processing flow, the system reduces the complexity burden on the API server while maintaining the ability to accurately determine service tiers based on subscription information.
3Adaptability or versatility
If the API server processes each request individually to determine service tier, then service-specific responses can be provided, but the scalability to handle higher volume requests decreases
Solution Approach 1:
The validation server performs preliminary service tier determination for each request, enabling the API server to receive pre-processed information that allows for service-specific responses. This preliminary action separates the service tier determination from the main request processing, allowing the API server to handle higher volumes of requests while still providing adapted service-specific responses based on the pre-determined service tier.
Data Source
AI summary
In various embodiments, one or more non-transitory computer-readable media storing program instructions that, when executed by one or more processors of an application programming interface (API) server, cause the one or more processors to perform a method comprising receiving, from a client device, a request to access a service; transmitting, to a validation server, an authorization request including an API authorization identifier; receiving, from the validation server, a validation response to the authorization request, the validation response including a validation result based on the API authorization identifier and an indicator of a level of resources to be used when performing the request; and performing the service based on the request and the validation response.