ENDPOINT MANAGEMENT SYSTEM PROVIDING AN APPLICATION PROGRAMMING INTERFACE PROXY SERVICE

• US 20160301739A1
• Filed: 04/08/2015
• Published: 10/13/2016
• Est. Priority Date: 04/08/2015
• Status: Active Grant

• Current Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Original Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Inventors: Thompson, Jonathan Paul
• Granted Patent: US 9,930,103 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/561 Adding application-functional data or data for application control, e.g. adding metadata

Abstract

An endpoint management and proxy system is described, by which users can manage and enable exposure of application programming interfaces (“APIs”) usable to cause execution of program code on a remote or third party system. Systems and methods are disclosed which facilitate the handling of user requests to perform certain tasks on remote systems. The endpoint management system allows the application developer to define and specify a first proxy API which maps to a second API associated with the remote system. The endpoint proxy system receives requests to execute the proxy API, determines the API mapping, and sends one or more backend API requests to execute program codes by the associated remote systems. Responses from the remote systems are received by the endpoint proxy system which parses and/or transforms the results associated with the response and generates an output result for response back to the user computing systems.

Claims

1. A system for providing endpoint management of application programming interfaces, the system comprising:

an electronic data store configured to store application programming interface (“

API”

) mapping definitions; and

an endpoint system comprising one or more hardware computing devices executing specific computer-executable instructions, wherein the endpoint system is in communication with the electronic data store, and configured to at least;

receive a plurality of API mapping definitions, wherein each respective API mapping definition associates a proxy API with at least one endpoint API;

receive a request from a calling system to execute a program code by a particular proxy API;

determine, based at least in part on the received request and the particular proxy API, an API mapping definition associated with the particular proxy API;

transform the request into an endpoint request for processing by an endpoint API system, wherein the request is transformed based at least in part on the API mapping definition and wherein the endpoint request includes an instruction to execute the program code on the endpoint API system;

transmit the endpoint request to the endpoint API system to cause execution of the program code on the endpoint API system;

receive an endpoint result from the endpoint API system, wherein the endpoint result is generated from the execution of the program code on the endpoint API system;

transform the endpoint result into a proxy result, wherein the endpoint result is transformed based at least in part on the API mapping definition; and

provide a return response to the calling system, wherein the return response comprises at least the proxy result.

2. The system of claim 1, wherein the endpoint system is further configured to store a copy of the endpoint result in a second electronic data store configured to store cached results received from respective endpoint API systems.

3. The system of claim 1, wherein the endpoint system is further configured to access a cached copy of the endpoint result a second electronic data store configured to store cached results received from respective endpoint API systems.

4. A system, comprising:

an endpoint proxy system comprising one or more hardware computing devices adapted to execute specific computer-executable instructions and in communication with an electronic data store configured to store application programming interface (“

API”

) mapping definitions, wherein the endpoint proxy system is configured to at least;

receive a request from a user computing device to execute a proxy API;

determine, based at least in part on the received request and the proxy API, an API mapping definition associated with the proxy API;

transform the request into a backend request for processing by a backend API system, wherein the request is transformed based at least in part on the API mapping definition and wherein the backend request includes an instruction to execute a backend API the endpoint API system;

transmit the backend request to the endpoint API system, wherein the backend request is adapted to cause execution of the backend API on the endpoint API system;

receive a backend result from the backend API system, wherein the endpoint result is generated by execution of the backend API on the backend API system;

transform the backend result into an output result, wherein the backend result is transformed based at least in part on the API mapping definition; and

provide the output result to the user computing device.

5. The system of claim 4, wherein the endpoint proxy system is further configured to store a copy of the backend result in a second electronic data store configured to store cached results received from respective backend API systems.

6. The system of claim 5, wherein the endpoint proxy system is further configured to store the copy of the backend result in the second electronic data store according to a cache duration setting associated with the API mapping definition.

7. The system of claim 4, wherein the endpoint proxy system is further configured to access a cached copy of the backend result from a second electronic data store configured to store cached results received from respective backend API systems.

8. The system of claim 4, wherein the API mapping definition comprises at least associated configuration settings for the proxy API and associated configuration settings for the backend API.

9. The system of claim 8, wherein the associated configuration settings for the proxy API comprises a proxy API name, a proxy API input parameter, and a proxy API output result type.

10. The system of claim 8, wherein the associated configuration settings for the backend API comprises a backend API name, a backend API input parameter, and a backend API output result type.

11. The system of claim 4, wherein the request to execute a proxy API is received from the user computing device over a first network and the backend result is received from the backend API system over a second network, wherein the second network is separate and distinct from the first network.

12. The system of claim 11, wherein the endpoint proxy system and the backend system are co-located on the second network.

13. A computer-implemented method comprising:

as implemented by one or more computing devices configured with specific executable instructions,

receiving a request from a calling system to execute a proxy API;

determining, based at least in part on the received request and the proxy API, an API mapping definition associated with the proxy API;

transforming the request into a backend request for processing by a backend API system, wherein the request is transformed based at least in part on the API mapping definition and wherein the backend request includes an instruction to execute a backend API the endpoint API system;

sending the backend request to the endpoint API system, wherein the backend request is adapted to cause execution of the backend API on the endpoint API system;

receiving a backend result from the backend API system, wherein the endpoint result is generated by execution of the backend API on the backend API system;

transforming the backend result into an output result, wherein the backend result is transformed based at least in part on the API mapping definition; and

providing the output result to the calling system.

14. The computer-implemented method of claim 13, further comprising storing a copy of the backend result in a second electronic data store configured to store cached results received from respective backend API systems.

15. The computer-implemented method of claim 13, further comprising:

receiving a second request to execute a second proxy API; and

determining, based at least in part on the received second request and the second proxy API, a second API mapping definition associated with the second proxy API.

16. The computer-implemented method of claim 15, further comprising:

determining, based on the API mapping definition, that the second proxy API is mapped to the backend API; and

accessing a cached copy of the backend result from a second electronic data store configured to store cached results received from respective backend API systems.

17. The computer-implemented method of claim 15, further comprising:

determining, based on the API mapping definition, that the second proxy API is mapped to a second backend API, wherein the second backend API is configured to return a second backend result that is a subset of the backend result generated by execution of the backend API;

accessing a cached copy of the backend result from a second electronic data store configured to store cached results received from respective backend API systems; and

providing a transformed output result of the cached copy to the calling system.

18. A computer-readable, non-transitory storage medium storing computer executable instructions that, when executed by one or more computing devices, configure the one or more computing devices to perform operations comprising:

receiving a request from a calling system to execute a proxy API;

determining, based at least in part on the received request and the proxy API, an API mapping definition associated with the proxy API;

transforming the request into a backend request for processing by a backend API system, wherein the request is transformed based at least in part on the API mapping definition and wherein the backend request includes an instruction to execute a backend API the endpoint API system;

sending the backend request to the endpoint API system, wherein the backend request is adapted to cause execution of the backend API on the endpoint API system;

receiving a backend result from the backend API system, wherein the endpoint result is generated by execution of the backend API on the backend API system;

transforming the backend result into an output result, wherein the backend result is transformed based at least in part on the API mapping definition; and

providing the output result to the calling system.

19. The computer-readable, non-transitory storage medium of claim 18, wherein the operations further comprise storing a copy of the backend result in a second electronic data store configured to store cached results received from respective backend API systems.

20. The computer-readable, non-transitory storage medium of claim 18, wherein the operations further comprise determining, based at least in part on an authorization setting associated with the API mapping definition, that a user identifier associated with the request to execute the proxy API is included in the API mapping definition as an authorized user or group.

21. The computer-readable, non-transitory storage medium of claim 18, wherein the operations further comprise determining that the request to execute the proxy API is allowed to proceed based at least in part on comparison of a performance throttling setting associated with the API mapping definition to a current API request workload associated with the backend API system.

22. The computer-readable, non-transitory storage medium of claim 18, wherein the API mapping definition comprises at least associated configuration settings for the proxy API and associated configuration settings for the backend API.

23. The computer-readable, non-transitory storage medium of claim 18, wherein the proxy API is associated with a first protocol and the backend API is associated with a second protocol.