DYNAMIC PERSONALIZED API ASSEMBLY
Methods, computer readable media, and devices for dynamic personalized API assembly are provided. One method may include receiving a data query from a client by a CDN, parsing the data query to generate a modified data query, transmitting the modified data query to an origin server, receiving a content from the origin server, generating a modified content based on the content, and sending the modified content to the client. Another method may include receiving an API call by an origin server, generating an API response by creating a payload file and adding markup directives indicating whether content is cacheable, and transmitting the API response.
1 . A computer-implemented method for providing an application programming interface (API), the method comprising:
providing an application programming interface (API) for processing a request from a client device;
in response to receiving the request, generating multiple API calls directed to a predefined subset of a plurality of services available via a cloud computing environment, wherein one or more of the multiple API calls are redirected to a cache;
receiving responses for the multiple API calls from the subset of services, wherein one or more of the responses includes response content marked as cacheable;
caching the response content marked as cacheable;
aggregating the responses into a single response payload file for the request; and
sending the single response payload file to the client device.
2 . The computer-implemented method of claim 1 , wherein the predefined subset of services is selected to personalize the single response payload file for the client device.
3 . The computer-implemented method of claim 1 , wherein the single response payload file comprises content previously marked as cacheable and content retrieved from an origin server.
4 . The computer-implemented method of claim 3 , wherein the content marked as cacheable is cached in a content delivery network (CDN).
5 . The computer-implemented method of claim 3 , wherein the content marked cacheable is associated with a duration of time for which the content is cached.
6 . The computer-implemented method of claim 5 , wherein the content is invalidated after the duration of time expires.
7 . The computer-implemented method of claim 1 , wherein the response content is marked as cacheable based on a predefined caching policy.
8 . The computer-implemented method of claim 1 further comprising:
providing the application programming interface (API) for processing a second request from a second client device;
in response to receiving the second request, generating a second set of multiple API calls directed to a second predefined subset of a plurality of services available via the cloud computing environment, wherein one or more of the second set of multiple API calls are redirected to a second cache;
receiving a second set of responses for the second set of multiple API calls from the second predefined subset of services, wherein one or more of the second set of responses includes a second response content marked as cacheable;
caching the second response content marked as cacheable;
aggregating the second set of responses into a second single response payload file for the second request; and
sending the second single response payload file to the second client device,
wherein the second predefined subset of services is selected to personalize the second single response payload file for the second client device.
9 . A non-transitory machine-readable storage medium that provides instructions that, if executed by a processor, are configured to cause said processor to perform operations comprising:
providing an application programming interface (API) for processing a request from a client device;
in response to receiving the request, generating multiple API calls directed to a predefined subset of a plurality of services available via a cloud computing environment, wherein one or more of the multiple API calls are redirected to a cache;
receiving responses for the multiple API calls from the subset of services, wherein one or more of the responses includes response content marked as cacheable;
caching the response content marked as cacheable;
aggregating the responses into a single response payload file for the request; and
sending the single response payload file to the client device.
10 . The non-transitory machine-readable storage medium of claim 9 , wherein the predefined subset of services is selected to personalize the single response payload file for the client device.
11 . The non-transitory machine-readable storage medium of claim 9 , wherein the single response payload file comprises content previously marked as cacheable and content retrieved from an origin server.
12 . The non-transitory machine-readable storage medium of claim 11 , wherein the content marked as cacheable is cached in a content delivery network (CDN).
13 . The non-transitory machine-readable storage medium of claim 11 , wherein the content marked cacheable is associated with a duration of time for which the content is cached.
14 . The non-transitory machine-readable storage medium of claim 13 , wherein the content is invalidated after the duration of time expires.
15 . The non-transitory machine-readable storage medium of claim 9 , wherein the response content is marked as cacheable based on a predefined caching policy.
16 . The non-transitory machine-readable storage medium of claim 9 further comprising:
providing the application programming interface (API) for processing a second request from a second client device;
in response to receiving the second request, generating a second set of multiple API calls directed to a second predefined subset of a plurality of services available via the cloud computing environment, wherein one or more of the second set of multiple API calls are redirected to a second cache;
receiving a second set of responses for the second set of multiple API calls from the second predefined subset of services, wherein one or more of the second set of responses includes a second response content marked as cacheable;
caching the second response content marked as cacheable;
aggregating the second set of responses into a second single response payload file for the second request; and
sending the second single response payload file to the second client device,
wherein the second predefined subset of services is selected to personalize the second single response payload file for the second client device.