Application programming interface as a service

• US 10,303,532 B1
• Filed: 10/31/2017
• Issued: 05/28/2019
• Est. Priority Date: 09/24/2014
• Status: Active Grant

• Current Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Original Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Inventors: Engers, Ross Bevan, Le Roux, Jaco Hermanus Gabriel
• Primary Examiner(s): Ho, Andy
• Assistant Examiner(s): Seye, Abdou K
• Application Number:
  US15/799,169
• Time in Patent Office: 574 Days
• CPC Class Codes: G06F 8/36 Software reuse
• CPC Class Codes: G06F 9/4484 Executing subprograms
• CPC Class Codes: G06F 9/45533 Hypervisors; Virtual machine monitors
• CPC Class Codes: G06F 9/54 Interprogram communication
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services

Abstract

An application programming interface (API) may be provided by a service. A client of the service may provide computer instructions to the service. Configuration information may also be provided by the client. An API may be generated for the client based on the computing instructions. A number of virtual machines may be associated with the API based on the configuration information. The API may be used to process requests.

Claims

1. A method for providing an application programming interface (API) as a service, comprising:

determining that a request to set up the service is authorized;

receiving a set of computer instructions and configuration information for the set of computer instructions, the set of computer instructions for processing invocations of the API when executed;

creating the API from the received set of computer instructions and configuration information;

determining, based on the configuration information, whether to change a number of one or more virtual machine (VM) instances associated with the API; and

processing an API call made to the service by executing at least a part of the set of computer instructions on the one or more VM instances.

2. The method of claim 1, further comprising receiving the API call made to the service, wherein determining whether to change the number of VM instances associated with the API is based on receiving the API call.

3. The method of claim 1, wherein the configuration information comprises a processing threshold, and wherein determining whether to change the number of VM instances associated with the API is based on a comparison of load information to the processing threshold.

4. The method of claim 1, further comprising determining one or more metrics associated with the API, and wherein determining whether to change the number of VM instances associated with the API is based on the one or more metrics.

5. The method of claim 1, wherein the configuration information comprises one or more of a scale up rule for determining whether to associate an additional VM instance with the API or a scale down rule for determining whether to terminate an association of a VM instance with the API.

6. The method of claim 1, further comprising instantiating an additional VM instance as one of the one or more VM instances based on the determining whether to change the number of one or more VM instances associated with the API.

7. The method of claim 1, further comprising configuring a load balancer to distribute a processing load among the one or more VM instances based on the determining whether to change the number of one or more VM instances associated with the API.

8. A system, comprising:

one or more processors; and

a memory communicatively coupled to the processor when the system is operational, the memory bearing processor-executable instructions that, upon execution by the one or more processors, cause the system to at least;

determine that a request to set up an application programming interface (API) as a service is authorized;

receive a set of computer instructions and configuration information for the set of computer instructions, the set of computer instructions for processing invocations of the API when executed;

create the API from the received set of computer instructions and configuration information;

determine, based on the configuration information, whether to change a number of one or more virtual machine (VM) instances associated with the API; and

process an API call made to the service by executing at least a part of the set of computer instructions on the one or more VM instances.

9. The system of claim 8, wherein the memory further bears processor-executable instructions that, upon execution by the one or more processors, cause the system to at least:

receive the API call made to the service, wherein the determine whether to change the number of VM instances associated with the API is based on receiving the API call.

10. The system of claim 8, wherein the configuration information comprises a processing threshold, and wherein the determine whether to change the number of VM instances associated with the API is based on a comparison of load information to the processing threshold.

11. The system of claim 8, wherein the memory further bears processor-executable instructions that, upon execution by the one or more processors, cause the system to at least:

determine one or more metrics associated with the API, and wherein the determine whether to change the number of VM instances associated with the API is based on the one or more metrics.

12. The system of claim 8, wherein the configuration information comprises one or more of a scale up rule for determining whether to associate an additional VM instance with the API or a scale down rule for determining whether to terminate an association of a VM instance with the API.

13. The system of claim 8, wherein the memory further bears processor-executable instructions that, upon execution by the one or more processors, cause the system to at least:

instantiate an additional VM instance as one of the one or more VM instances based on the determine whether to change the number of one or more VM instances associated with the API.

14. The system of claim 8, wherein the memory further bears processor-executable instructions that, upon execution by the one or more processors, cause the system to at least:

configure a load balancer to distribute a processing load among the one or more VM instances based on the determine whether to change the number of one or more VM instances associated with the API.

15. A non-transitory computer-readable storage medium bearing computer-executable instructions that, upon execution by one or more computing nodes, cause the one or more computing nodes to perform operations comprising:

determining that a request to set up an application programming interface (API) as a service is authorized;

receiving a set of computer instructions and configuration information for the set of computer instructions, the set of computer instructions for processing invocations of the API when executed;

creating the API from the received set of computer instructions and configuration information;

determining, based on the configuration information, whether to change a number of one or more virtual machine (VM) instances associated with the API; and

processing an API call made to the service by executing at least a part of the set of computer instructions on the one or more VM instances.

16. The non-transitory computer-readable storage medium of claim 15, further bearing computer-executable instructions that, upon execution by the one or more computing nodes, cause the one or more computing nodes to perform operations comprising:

receiving the API call made to the service, wherein determining whether to change the number of VM instances associated with the API is based on receiving the API call.

17. The non-transitory computer-readable storage medium of claim 15, wherein the configuration information comprises a processing threshold, and wherein determining whether to change the number of VM instances associated with the API is based on a comparison of load information to the processing threshold.

18. The non-transitory computer-readable storage medium of claim 15, further bearing computer-executable instructions that, upon execution by the one or more computing nodes, cause the one or more computing nodes to perform operations comprising:

determining one or more metrics associated with the API, and wherein determining whether to change the number of VM instances associated with the API is based on the one or more metrics.

19. The non-transitory computer-readable storage medium of claim 15, wherein the configuration information comprises one or more of a scale up rule for determining whether to associate an additional VM instance with the API or a scale down rule for determining whether to terminate an association of a VM instance with the API.

20. The non-transitory computer-readable storage medium of claim 15, further bearing computer-executable instructions that, upon execution by the one or more computing nodes, cause the one or more computing nodes to perform operations comprising:

instantiating an additional VM instance as one of the one or more VM instances based on the determining whether to change the number of one or more VM instances associated with the API.