Why and how to optimize your Lambda

1. node-mysql2

   1 11 4,247 9.7 JavaScript

   :zap: fast mysqljs/mysql compatible mysql driver for node.js

   

   Unfortunately, ESM is not a silver bullet, and I ran into some issues. For example, running the mysql2 in ESM was not possible. Make sure to test everything properly. I wrote a more extensive blog post about ESM vs CJS.

2. SurveyJS

   surveyjs.io featured

   JavaScript Form Builder with No-Code UI & Built-In JSON Schema Editor. Keep full control over the data you collect and tailor the form builder’s entire look and feel to your users’ needs. SurveyJS works with React, Angular, Vue 3, and is compatible with any backend or auth system. Learn more.

   

3. hono

   2 99 24,917 9.5 TypeScript

   Web framework built on Web Standards

   

   Especially in the Node.js ecosystem, there are numerous alternatives to choose from. When selecting an Express alternative, check out HonoJS. Not because the syntax is similar to ExpressJS, but the bundle is only 19 KB 🤯 When using Zod 4, consider Zod mini.

4. aws-lambda-power-tuning

   3 45 5,784 6.3 JavaScript

   AWS Lambda Power Tuning is an open-source tool that can help you visualize and fine-tune the memory/power configuration of Lambda functions. It runs in your own AWS account - powered by AWS Step Functions - and it supports three optimization strategies: cost, speed, and balanced.

   

   Lambda Power Tuning is a fascinating project that operates your Lambda with varying memory sizes and presents a chart. It displays the execution time and costs based on the memory size (see below). How to interpret the chart above: execution time goes from 35s with 128MB to less than 3s with 1.5GB, while being 14% cheaper to run4.

5. esbuild

   4 359 39,085 9.1 Go

   An extremely fast bundler for the web

   

   I recommend using NodeJS, not because it fits the event-driven, non-blocking model, but because it is very well-suited for reducing file size by bundling the code. Esbuild is a great tool to bundle your Lambda. It is already included in the CDK construct NodeJSFunction when using AWS CDK, and you don't need source maps, at least not in production.

Suggest a related project