Solve The Cold Start Issue with Lambda Provisioned Concurrency

Cold Starts have been a massive issue with FaaS. In summary, it makes functions slower to startup in some cases. That’s in the opposite way of every effort to improve web applications performance.

Many efforts have been made in the recent years to solve AWS Lambda cold starts or educate on handling them. Many have mitigated the issue, but none really solved it.

AWS has just made a great progress on the area with the Provisioned Capacity feature announcement. As the function scales up, instead of waiting new requests to come in before provisioning resources to serve them, AWS will proactively provision new instances of the function in advance.

This behavior guarantees the performance of every request will stay within double digit milliseconds, up to the Provisioned Concurrency threshold set to the function. There are some caveats that developers should be aware though. For example: it makes your functions inelligible to the Lambda Free Tier.

Learn everything about this feature and follow a step-by-step guide in our Knowledge Base.

Lambda Provisioned Concurrency is generally available in several regions and already integrated with AWS SAM, CodeDeploy and other serverless frameworks.

_Image credits to Denys Nevozhai on Unsplash_.

A collection of lessons learned at Dashbird after working with 4,000+ customers and 300,000+ Lambda functions

Write for us!

We're looking for developers to share their experience with serverless.

Emails and pull requests welcome!

Start using Dashbird for free!

Failure detection, analytics and visibility for serverless applications in under 5 minutes.

Request Demo