CDN API Request Routing for Uniform Cloud Service Signatures
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing DNS-based routing methods for API requests to cloud service instances face limitations due to variability in API call signatures, leading to reduced availability of documented reusable API calls, especially when multiple concurrent instances are involved.
Innovation Solution
A combination of content delivery network (CDN) routing and DNS routing is employed to standardize API call signatures, using a global routing table to dynamically route API requests to appropriate cloud service instances, allowing transparent migration of workloads without altering client-provided API requests.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If DNS-based routing is used to route API requests to cloud service instances, then routing capability is provided, but API call signature uniformity deteriorates and availability of documented reusable API calls reduces
Solution Approach 1:
A CDN routing engine is introduced as an intermediary between clients and cloud service instances. The routing engine receives API requests, determines the appropriate service instance based on geographic region and service type, and forwards requests through standardized endpoints. This intermediary layer enforces signature uniformity while maintaining routing flexibility, resolving the contradiction between adaptability and precision.
2Productivity
If multiple concurrent cloud service instances are deployed, then service capacity and geographic coverage are improved, but API call signature variability increases
Solution Approach 1:
The system segments API requests by geographic region and service type, routing them to appropriate regional service instances. Each region maintains standardized API endpoints and signatures, while the CDN routing engine manages the segmentation and routing logic. This allows multiple concurrent instances to operate with uniform signatures within their respective segments.
Solution Approach 2:
The CDN routing engine serves multiple functions: it acts as a DNS resolver, a geographic routing decision-maker, and an API signature standardizer. By consolidating these functions in a single universal component, the system maintains signature uniformity across multiple service instances while providing geographic distribution and load balancing.
3Adaptability or versatility
If workload migration between cloud service instances is enabled, then system flexibility and maintenance capability are improved, but client API request consistency becomes more difficult to maintain
Solution Approach 1:
The CDN routing engine creates and manages copies of API requests, forwarding them to appropriate service instances based on current workload distribution. When workload migration occurs, the routing engine updates its internal routing tables and redirects subsequent requests to the new instance. Clients continue using the same API endpoints and signatures, while the routing engine handles the migration transparently in the background.
Data Source
AI summary
A process includes receiving, by a server associated with a content delivery network, a first request that specifies an application programming interface (API) call to a cloud service. The first request includes data that represents an authorization bearer token, a geographical service region identifier and an API call group. The process includes routing, by the server, the API call to an instance of the cloud service. The routing includes determining, by the server, a client identifier based on the authorization bearer token; and identifying, by the server, a location of the instance based on the client identifier, the geographical region identifier and the API call group identifier. The routing includes, responsive to the identification, sending, by the receiver, a second request corresponding to the API call to the location.