Software container activation and throttling

US10389697B1 · US · B1

Patent metadata
FieldValue
Publication numberUS-10389697-B1
Application numberUS-201414498862-A
CountryUS
Kind codeB1
Filing dateSep 26, 2014
Priority dateAug 27, 2014
Publication dateAug 20, 2019
Grant dateAug 20, 2019

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

Technologies are described herein for managing the activation of software containers, for throttling of requests directed to tenants executing in a software container, and for priming the execution of software containers. The activation of software containers and tenants may be managed by maintaining an activation queue for storing requests to activate software containers or tenants on a host computer. Requests may be retrieved from the queue and utilized to determine whether a software container or a tenant is to be activated on a host. “Bounce” or hot swap tenant activations may be performed. Tenant activation requests might also be throttled by denying the requests or by postponing the requests until a later time. A software container might also be configured to throttle incoming requests to tenants executing therein. The execution of a software container might also be primed by replaying previously recorded network traffic to the software container.

First claim

Opening claim text (preview).

What is claimed is: 1. A non-transitory computer-readable storage medium having computer-executable instructions stored thereupon which, when executed by a computer, cause the computer to: receive a first request from a tenant to activate the tenant in a software container, the tenant comprising an application executable in the software container; determine that the first request indicates that, prior to activating the tenant in the first software container, execution of the software container is to be terminated, and then the execution of the software container is to be restarted; transmit a second request to an authorization system to inquire whether the tenant is authorized to request an activation that includes a restart of the software container; receive, from the authorization system, a response indicating that the tenant is so authorized to request the activation; and based at least in part on determining that the tenant is authorized to request the activation: terminate the execution of the software container; restart the execution of the software container; activate the tenant in the software container; and prime the execution of the software container by replaying previously recorded network traffic to the software container following restarting the execution of the software container. 2. The non-transitory computer-readable storage medium of claim 1 , having further computer-executable instructions stored thereupon to, after the tenant has been activated in the software container: determine that the tenant is experiencing an operational issue; terminate the execution of the software container; restart the execution of the software container; and activate the tenant in the software container. 3. The non-transitory computer-readable storage medium of claim 1 , having further computer-executable instructions stored thereupon to: expose an application programming interface (API) for receiving a third request to activate the tenant in the software container by restarting the execution of the software container and activating the tenant therein; receive the third request by way of the API; and in response to receiving the third request by the API, terminate the execution of the first software container, restart the execution of the first software container, and activate the tenant in the first software container. 4. The non-transitory computer-readable storage medium of claim 1 , having further computer-executable instructions stored thereupon to: determine to throttle incoming requests for at least one tenant of a plurality of tenants of the software container; and throttle the incoming requests by rejecting at least a portion of the incoming requests for the at least one tenant. 5. The non-transitory computer-readable storage medium of claim 1 , having further computer-executable instructions stored thereupon to: determine to throttle incoming requests for at least one tenant of a plurality of tenants of the software container; and throttle the incoming requests by queueing at least a portion of the incoming requests for the at least one tenant for processing at a future time. 6. The non-transitory computer-readable storage medium of claim 1 , having further computer-executable instructions stored thereupon to: receive a request to throttle incoming requests for one or more tenants of a plurality of tenants of the software container; and throttle the incoming requests for the one or more tenants by denying or queueing at least a portion of the incoming requests for the one or more tenants. 7. A computer for activation of tenant in a software container on the computer, the computer comprising: a processor; and a non-transitory computer-readable storage medium having computer-executable instructions stored thereupon which, when executed by the processor, cause the computer to: receive a first request from a tenant to activate the tenant in a software container, the tenant being executable in the software container; determine whether the tenant is authorized to request an activation that includes a restart of the software container; based at least in part on a first determination that the tenant is authorized to request the activation: terminate the execution of the software container; restart the execution of the software container; activate the tenant in the software container; and prime the execution of the software container by replaying previously recorded network traffic to the software container following restarting the execution of the software container; or based at least in part on a second determination that the tenant is not se authorized to request the activation: activate the tenant in the software container without terminating and restarting the execution of the software container. 8. The computer of claim 7 , wherein the non-transitory computer-readable storage medium has further computer-executable instructions stored thereupon to cause the computer to determine whether the tenant is authorized to request the activation that includes the restart of the software container by: transmitting a second request to an authorization system to inquire whether the tenant is authorized to request the activation; and receiving, from the authorization system, a response either indicating that the tenant is authorized to request the activation or indicating that the tenant is not authorized to request the activation. 9. The computer of claim 7 , wherein terminating the execution of the software container comprises: completing one or more processes associated with one or more other tenants executing on the software container; and terminating the execution of the software container after completion of the one or more processes. 10. The computer of claim 7 , wherein the non-transitory computer-readable storage medium has further computer-executable instructions stored thereupon to cause the computer to: execute the software container in a process on the computer, the software container configured to execute one or more tenants in the process, the tenant being one of the one or more tenants in the process; obtain operational health information by way of the software container; determine at the software container to throttle incoming requests for at least one of the one or more tenants based, at least in part, on the operational health information; and throttle at least a portion the incoming requests for at least one of the one or more tenants by way of the software container. 11. The computer of claim 10 , wherein the operational health information comprises operational health information for the at least one tenant. 12. The computer of claim 10 , wherein the operational health information comprises operational health information for the software container. 13. The computer of claim 10 , wherein the operational health information comprises operational health information for the computer. 14. The computer of claim 7 , wherein the non-transitory computer-readable storage medium has further computer-executable instructions stored thereupon to cause the computer to: determine at the software container to throttle incoming requests for at least one tenant of a plurality of tenants, the tenant being one of the plurality of tenants; throttle at least a portion of the incoming requests for the at least one tenant by way of the software container by routing at least a portion of the incoming requests to another tenant. 15. The computer of claim 7 , wherein the non-transitory computer-readable storage medium has further computer-executable instruct

Assignees

Inventors

Classifications

  • H04W12/08Primary

    Access security · CPC title

  • based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title

  • Profiles · CPC title

  • H04L63/08Primary

    for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32) · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US10389697B1 cover?
Technologies are described herein for managing the activation of software containers, for throttling of requests directed to tenants executing in a software container, and for priming the execution of software containers. The activation of software containers and tenants may be managed by maintaining an activation queue for storing requests to activate software containers or tenants on a host c…
Who is the assignee on this patent?
Amazon Tech Inc
What technology area does this patent fall under?
Primary CPC classification H04W12/08. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Aug 20 2019 00:00:00 GMT+0000 (Coordinated Universal Time) (B1). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 6 related publications on this page (citations in our corpus or others sharing the same primary CPC).