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.

Read our blog

5 Common Amazon SQS Issues

As with all services on AWS, issues can crop up while using SQS because it’s not always obvious what every service can and cannot do. But fear not, for this article aims to help you solve the most common ones as quickly as possible. Ready to fix your queues? Then let’s dive in!

5 Common Step Function Issues

Here you will find the most common issues when working with Step Functions, especially when starting with the service.

6 Common DynamoDB Issues

It’s expected that developers face many of the same issues when starting their NoSQL journey with DynamoDB. This article might clear things up a bit.

More articles

Made by developers for developers

Dashbird was born out of our own need for an enhanced serverless debugging and monitoring tool, and we take pride in being developers.

What our customers say

Dashbird gives us a simple and easy to use tool to have peace of mind and know that all of our Serverless functions are running correctly. We are instantly aware now if there’s a problem. We love the fact that we have enough information in the Slack notification itself to take appropriate action immediately and know exactly where the issue occurred.

Thanks to Dashbird the time to discover the occurrence of an issue reduced from 2-4 hours to a matter of seconds or minutes. It also means that hundreds of dollars are saved every month.

Great onboarding: it takes just a couple of minutes to connect an AWS account to an organization in Dashbird. The UI is clean and gives a good overview of what is happening with the Lambdas and API Gateways in the account.

I mean, it is just extremely time-saving. It’s so efficient! I don’t think it’s an exaggeration or dramatic to say that Dashbird has been a lifesaver for us.

Dashbird provides an easier interface to monitor and debug problems with our Lambdas. Relevant logs are simple to find and view. Dashbird’s support has been good, and they take product suggestions with grace.

Great UI. Easy to navigate through CloudWatch logs. Simple setup.

Dashbird helped us refine the size of our Lambdas, resulting in significantly reduced costs. We have Dashbird alert us in seconds via email when any of our functions behaves abnormally. Their app immediately makes the cause and severity of errors obvious.