Amazon Technologies, Inc.

Naveen Dasa Subramanyam

David Craig Yanacek

Amit Raghunath Kulkarni

Sean Tyler Myers

Aritra Bandyopadhyay

Yogesh Aggarwal

Jianwei Cui

Shashanka Krishnaswamy

Systems and methods are described for reducing cold starts code within a serverless code execution system by providing a set of environments reserved for the code. A frontend distribute calls for execution among a set of manager devices that manage environments in the system, distributed in a manner that groups calls together and attempts to distribute calls of the same group to a stable subset of the manager devices. In the case that a user reduces or eliminates the number of environments reserved for the code, a frontend continues to distribute calls for execution of the code to those environments while they continue to be used. This reduces cold starts that might otherwise occur during reduction or elimination of reserved environments.

Serverless call distribution to implement spillover while avoiding cold starts

Systems and methods are described for reducing cold starts code within a serverless code execution system by providing a set of environments reserved for the code. A frontend utilizes a consistent hash ring to distribute calls for execution among a set of manager devices that manage environments in the system, distributed in a manner that groups calls together and attempts to distribute calls of the same group to a stable subset of the manager devices. Each group is assigned an arc, representing a subset of manager devices. When a call is received to execute a set of code that has environments reserved, the frontend distributes the call to a manager device of a reserved arc. When a call is received to execute a set of code that does not have environment reserved, the frontend distributes the call to an arc associated with an arc for unreserved executions.

Serverless call distribution to utilize reserved capacity without inhibiting scaling

A computing resource service provider may provide customers with access to software functions executing within compute instances. In addition, customer may desire that the software functions executing within the compute instances have access to virtual network operated by the customer. To accomplish this, a network interface belonging to the customer may be created and attached to a particular compute instance. In addition, this network interface may be moved from global network namespace of the compute instance into a new network namespace within the compute instance. In this manner, software functions executed by the compute instance may communicate to other computing device attached to the virtual network through the network interface.

Virtual networking for compute instances

Growing community of inventors

Seattle, WA, United States of America

Naveen Dasa Subramanyam