There are many blog posts about cold starts in AWS Lambda out there. I was doing some research and wanted to list the good ones here as well as some bullet points for quick insights into the topic.
A latency experienced when you trigger a function.
A cold start only happens if there is no idle container available waiting to run the code. This is all invisible to the user and AWS has full control over when to kill containers.
If you are using a statically typed language like Java and C# (no shame in there! :D)
First, accept that you can’t guarantee that you won’t experience cold-starts. The ultimate solution must come from the cloud provider. We can only try to improve.
How does language, memory and package size affect cold starts of AWS Lambda?_Comparing the cold start times of AWS Lambda using different languages, memory allocation, and sizes of deployment…_read.acloud.guru
Dealing with cold starts in AWS Lambda_Suppose you want to buy a ticket to a concert of your favorite band and you know that the tickets are running out. You…_medium.com
Resolving Cold Start️ in AWS Lambda_Yes, I know cold starts are frustrating in lambda. Lets start the post with a formal introduction. AWS Lambda is…_medium.com
How to Warmup_This part is not mandatory but if you want to warmup your lambda functions follow along._docs.thundra.io