CODEWITHSUNDEEP
amazon-web-servicesaws-lambda
hatellla
hatellla

Reputation: 5132

AWS Lambda Provisioning Business Logic

In AWS Lambda, there is no need of provisioning done by us. But I was wondering how AWS Lambda might be provisioning machines to run for the requests. Is it creating a EC2 server for each request and execute the request and then kill the server? Or it keeps some EC2 servers always on to serve the request by executing the lambda function? If its doing the former point, then I am wondering it would also affect performance of AWS Lambda to serve the request. Can anyone guide me on this?

Upvotes: 4

Views: 109

Answers (2)

Ryan Shillington
Ryan Shillington

Reputation: 25097

Lambdas run inside of a docker-like container, on EC2 servers (using Firecracker) that are highly, highly optimized. AWS has thousands of servers running full time to serve all of the Lambda functions that are running.

A cold start Lambda (one that's never been run before) starts up in a few seconds, depending on how big it is. An EC2 server takes 30+ seconds to startup. If it had to startup an EC2 server, you'd never be able to use a Lambda through API gateway (because API Gateway has a 30 second timeout). But obviously you can.

If you want your Lambdas to startup super duper fast (100ms), use Provisioned Concurrency.

Upvotes: 2

qkhanhpro
qkhanhpro

Reputation: 5220

AWS Lambda is known to reuse the resources. It will not create an EC2 server for each request so that will not be a performance concern

But you should note that the disk space provided for your function sometimes not cleanup properly. As some users reported

You can read more on the execution life cycle of Lambda here: https://docs.aws.amazon.com/lambda/latest/dg/running-lambda-code.html

Upvotes: 0

Related Questions