#Npm serverless appsync plugin code

Plus, it can have real impacts on customer retention and conversion.īack-end developers have been able to get away with ignoring their code size for a long time because of the way it was packaged and executed. The amount of time taken for it to download affects the time to first paint and time to first interaction. They spent hours optimizing the JavaScript, images, CSS, and HTML delivered to a web application. The packaged code size has long been a metric of importance to web developers. Where back-end developers need to catch up The result is a slow response time for your customer. Since this code is in your application package, it still needs to be copied and extracted onto the file system every time a container is provisioned. This can create very bloated Lambda functions. If you’re using the serverless framework with JavaScript, it packages your code with all the npm dependencies by default. This extra startup time will impact the perceived responsiveness of user-facing functions, such as APIs or Slack applications. Why bundle size still mattersĭespite the improvements that AWS has made, your Lambda can still cold start. These changes have reduced the number of things that a developer needs to do to improve their Lambda start-up performance.īut there is still one variable under the control of the developer that has a significant effect on cold starts – the packaged bundle size. AWS has been doing some great work lately to reduce Lambda cold start times for all its Lambda runtimes, such as their VPC networking improvements and adding native support for automatically keeping your Lambda containers warm.

Npm serverless-appsync-plugin