Implementation of a service that coordinates the placement and execution of containers

• US 10,218,633 B2
• Filed: 03/28/2014
• Issued: 02/26/2019
• Est. Priority Date: 03/28/2014
• Status: Active Grant

• Current Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Original Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Inventors: Carl, Craig Keith
• Primary Examiner(s): Bates, Kevin T
• Assistant Examiner(s): Scott, Mark A
• Application Number:
  US14/229,702
• Publication Number:
  US 20150281111A1
• Time in Patent Office: 1,796 Days
• Field of Search: 709226
• CPC Class Codes: H04L 47/70 Admission control; Resource allocation
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 67/1023 based on a hash applied to IP addresses or costs
• CPC Class Codes: H04L 67/1036 Load balancing of requests to servers for services different from user content provisioning, e.g. load balancing across domain name servers

Abstract

Organizations are constantly looking for faster and less expensive computer systems to manage businesses; however, the current standard in virtualization techniques includes using virtual machines, which require a long period of time to be instantiated before handling requests and are resource intensive. Using Domain Name System (DNS) queries to a DNS server as an indicator to initiate a virtual resource, such as containers, enables the system to instantiate the container prior to an end user transmitting their first request for a resource stored in that container. Containers can be initialized upon indication of a request, terminated at the end of the request process and initialized again for a next request as they can be activated at very fast speeds as needed. Additionally, using DNS queries as indicators to warm a cache of a network component enables the system components to be imminently used, to be pre-loaded with requested resources.

Claims

1. A computer-implemented method comprising:

receiving, from a Domain Name System (DNS) service, a message indicating a DNS request, made by a client device, to resolve a uniform resource locator (URL) to an Internet Protocol (IP) address;

as a result of receiving the message, instantiating the container thereby enabling the instantiated container to process a request transmitted to the IP address, the container being an operating system-level virtualization of an environment of a computing resource;

receiving, from the client device, the request directed to the IP address; and

sending the received request to the instantiated container.

2. The computer-implemented method of claim 1, wherein instantiating the container comprises utilizing information in the DNS request to instantiate the container prior to a request for a resource being transmitted to the container.

3. The computer-implemented method of claim 2, wherein the request is routed to the container via a load balancer and wherein the DNS service is configured to send an IP address of the load balancer to the client device.

4. The computer-implemented method of claim 2, wherein the resource is virtual machine, a web resource, an image, a web form, a static webpage, a website, or an application programming interface.

5. A system, comprising:

at least one computing device implementing one or more services, wherein the one or more services;

receive a request, from a requestor, to resolve a first identifier of a resource stored in a container to a second identifier of the resource stored in the container, the container being a virtualization of an environment of the resource; and

transmit, to a system different from the requestor that is operable to instantiate the container, a notification of the request involving the first identifier for the resource stored in the container.

6. The system of claim 5, wherein the request is received by a Domain Name System (DNS) service, the DNS service is operably interconnected with a load-balancing layer configured to provide an Internet Protocol (IP) address to the container.

7. The system of claim 6, wherein the load-balancing layer is operably interconnected with a timer and configured to monitor a time between an instantiation of the container and a next request for the resource in the container.

8. The system of claim 6, wherein the load-balancing layer is configured to control a time-out value, when the time-out value equals a maximum value, the load-balancing layer is configured to transmit a message to the container to terminate operational status, wherein the maximum value can be a predetermined value or a dynamically set value.

9. The system of claim 6, wherein the one or more services are further configured to transmit a message to the load-balancing layer to instantiate at least two containers, wherein the at least two containers include a first resource and a second resource accessibly by the first resource.

10. The system of claim 6, wherein the load-balancing layer is configured to keep the container instantiated to process future requests for a length of time determined based at least in part on a time value associated with the request.

11. The system of claim 10, wherein determining the length of time to keep the container instantiated includes determining the length of time based at least in part on a location in which the container is running, a number of compute cycles, a maximum or minimum financial cost, or a media acknowledgment related to at least one resource store in the container.

12. The system of claim 10, further comprising dynamically setting a run time for the container during a lifecycle of the container, wherein the run time is based at least in part on a function of geographic rotation, a function of geographic location of a user requesting access to the container or a function of a type of resource the container is hosting.

13. A non-transitory computer-readable storage medium having stored thereon executable instructions that, if executed by one or more processors of a computer system, cause the computer system to at least:

detect a request made, by a client device, to resolve a first identifier associated with a container to a second identifier of a resource stored in a network component, the container comprising code to be executed to process the request;

load the code to process the request; and

as a result of the detecting, initiate the network component to pre-warm a cache associated with the network component before the client device transmits a request referencing the second identifier.

14. The non-transitory computer-readable storage medium of claim 13, wherein the instructions further comprise instructions that, when executed by the one or more processors, cause the computer system to maintain a cache operably interconnected to a domain name system (DNS) server.

15. The non-transitory computer-readable storage medium of claim 13, wherein the instructions further comprise instructions that, when executed by the one or more processors, cause the computer system to maintain resource records in the cache of the network component, wherein the resource records include information related to the client device, a customer of a client device and/or information related to services requested by the client device.

16. The non-transitory computer-readable storage medium of claim 15, wherein the instructions that cause the computer system to maintain resource records in the cache of the network component further include instructions that cause the computer system to:

search the cache for resource records corresponding to the request; and

utilize the resource records to resolve the request.

17. The non-transitory computer-readable storage medium of claim 13, wherein the instructions further comprise instructions that, when executed by the one or more processors, cause the computer system to instantiate a virtual machine or a container in response to a network component pre-loading data related to a resource into the cache of the network component.

18. The non-transitory computer-readable storage medium of claim 17, wherein the instructions that cause the computer system to instantiate the virtual machine or the container further include instructions that cause the computer system to selectively transmit a message that includes a type of the resource, wherein the type of the resource includes a virtual machine, a web resource, an image, a web form, a static webpage, or an application programming interface.

19. The non-transitory computer-readable storage medium of claim 13, wherein the instructions further comprise instructions that, when executed by the one or more processors, cause the computer system to determine a point of presence (PoP) location to send a user request.

20. The non-transitory computer-readable storage medium of claim 19, wherein the instructions that cause the computer system to determine the PoP location to send the user request further include instructions that cause the computer system to transmit a message to the PoP location, the message including a notification of incoming activity.