That’s not really unique to Node. The majority of languages and web app platforms have concurrency mechanisms that will process multiple requests simultaneously. That is certainly a drawback of Lambda if you’re looking at raw CPU cycle efficiency and your application spends a lot of time waiting on synchronous downstream calls, but in most cases that doesn’t really matter. In practice, there are a lot of apps that can either use really fast data stores like Dynamo or use asynchronous processing models that minimize the amount of idle CPU time for a given request. Also, even with some inefficiencies when looking at high concurrency time periods, sometimes the ability for Lambda to immediately scale down during troughs in your load pattern makes up for it when looking at the global efficiency of the system (especially when you consider other operational overhead like patching servers.) Bottom line, people use Node with Lambda because they like the language and are familiar with it. Using the same language for the front end browser code and the backend is nice for teams that build full stack web apps. Answer from VegaWinnfield on reddit.com
Amazon Web Services
docs.aws.amazon.com › aws lambda › developer guide › building lambda functions with node.js
Building Lambda functions with Node.js - AWS Lambda
You can run JavaScript code with Node.js in AWS Lambda. Lambda provides runtimes for Node.js that run your code to process events. Your code runs in an environment that includes the AWS SDK for JavaScript, with credentials from an AWS Identity and Access Management (IAM) role that you manage.
Reddit
reddit.com › r/aws › why would i use node.js in lambda? node main feature is handling concurrent many requests. if each request to lambda will spawn a new node instance, whats the point?
r/aws on Reddit: Why would I use Node.js in Lambda? Node main feature is handling concurrent many requests. If each request to lambda will spawn a new Node instance, whats the point?
February 8, 2020 -
Maybe I'm missing something here, from an architectural point of view, I can't wrap my head on using node inside a lambda. Let's say I receive 3 requests, a single node instance would be able to handle this with ease, but if I use lambda, 3 lambdas with Node inside would be spawned, each would be idle while waiting for the callback.
Edit: Many very good answers. I will for sure discuss this with the team next week. Very happy with this community. Thanks and please keep them coming!
Top answer 1 of 27
29
That’s not really unique to Node. The majority of languages and web app platforms have concurrency mechanisms that will process multiple requests simultaneously. That is certainly a drawback of Lambda if you’re looking at raw CPU cycle efficiency and your application spends a lot of time waiting on synchronous downstream calls, but in most cases that doesn’t really matter. In practice, there are a lot of apps that can either use really fast data stores like Dynamo or use asynchronous processing models that minimize the amount of idle CPU time for a given request. Also, even with some inefficiencies when looking at high concurrency time periods, sometimes the ability for Lambda to immediately scale down during troughs in your load pattern makes up for it when looking at the global efficiency of the system (especially when you consider other operational overhead like patching servers.) Bottom line, people use Node with Lambda because they like the language and are familiar with it. Using the same language for the front end browser code and the backend is nice for teams that build full stack web apps.
2 of 27
12
> if I use lambda, 3 lambdas with Node inside would be spawned, each would be idle while waiting for the callback This is true of any other language, though. You could have three instances of a program written in Assembly waiting for data to return. > I can't wrap my head on using node inside a lambda The reasons to adopt Node over other platforms are varied, and not necessarily technical arguments. Node has fast startup times compared with .Net or Java. AWS themselves recommend Node in use-cases where cold-start latency matters; eg. web handlers. Most business applications are IO-bound. It doesn't matter which language you pick if you're sat waiting for data to return over the network. Javascript is easy to hire for - it's a lingua franca that most engineers have some skill with Modern front-end frameworks often support server-side rendering, which makes a single language attractive across the entire stack. As a result of the above, JS is the default option for Lambda, which means the best tooling and libraries are written for JS, compounding the advantages and mind-share. Architecture isn't really about making the best technical choice, it's about making the right _business_ decision in a technical context so that your choices support one another.
Videos
03:14
How To Deploy a Node JS Lambda Function Using the AWS CDK - YouTube
29:00
Complete Guide to AWS Lambda Function with Node Js, AWS Api Gateway ...
15:36
Build a REST API using AWS Lambda, API Gateway and NodeJS - YouTube
29:36
How to test and develop AWS lambda functions locally with nodejs?
A Node.js Lambda Function
Amazon Web Services
docs.aws.amazon.com › aws lambda › developer guide › building lambda functions with node.js › define lambda function handler in node.js
Define Lambda function handler in Node.js - AWS Lambda
This page describes how to work with Lambda function handlers in Node.js, including options for project setup, naming conventions, and best practices. This page also includes an example of a Node.js Lambda function that takes in information about an order, produces a text file receipt, and ...
GitHub
github.com › aws › aws-lambda-nodejs-runtime-interface-client
GitHub - aws/aws-lambda-nodejs-runtime-interface-client: AWS Lambda Runtime Interface Client for Node.js · GitHub
Starred by 220 users
Forked by 62 users
Languages TypeScript 91.1% | Shell 3.9% | JavaScript 2.5% | C++ 1.8% | Python 0.4% | M4 0.2% | Makefile 0.1%
AWS
docs.aws.amazon.com › cdk › api › v2 › python › aws_cdk.aws_lambda_nodejs › README.html
Amazon Lambda Node.js Library — AWS Cloud Development Kit 2.248.0 documentation
This library provides constructs for Node.js Lambda functions. The NodejsFunction construct creates a Lambda function with automatic transpiling and bundling of TypeScript or Javascript code.
npm
npmjs.com › package › node-lambda
node-lambda - npm
Command line tool for locally running and remotely deploying your node.js applications to Amazon Lambda.. Latest version: 1.3.0, last published: 2 years ago. Start using node-lambda in your project by running `npm i node-lambda`. There are 28 other projects in the npm registry using node-lambda.
» npm install node-lambda
Published Jan 08, 2024
Version 1.3.0
Author motdotla
Repository https://github.com/motdotla/node-lambda
TutorialsPoint
tutorialspoint.com › aws_lambda › aws_lambda_function_in_nodejs.htm
AWS Lambda Function in NODEJS
Nodejs is one of the languages that AWS Lambda function supports. The version supported with nodejs are v6.10 and v8.10. In this chapter, we will learn about various functionalities of AWS Lambda function in NODEJS in detail.
npm
npmjs.com › package › @aws-cdk › aws-lambda-nodejs
@aws-cdk/aws-lambda-nodejs - npm
This library provides constructs for Node.js Lambda functions. The NodejsFunction construct creates a Lambda function with automatic transpiling and bundling of TypeScript or Javascript code.
» npm install @aws-cdk/aws-lambda-nodejs
Published Jun 19, 2023
Version 1.204.0
Author Amazon Web Services
Repository https://github.com/aws/aws-cdk
Homepage https://github.com/aws/aws-cdk
AWS
aws.amazon.com › about-aws › whats-new › 2025 › 11 › aws-lambda-nodejs-24
AWS Lambda adds support for Node.js 24 - AWS
AWS Lambda now supports creating serverless applications using Node.js 24. Developers can use Node.js 24 as both a managed runtime and a container base image, and AWS will automatically apply updates to the managed runtime and base image as they become available.
GeeksforGeeks
geeksforgeeks.org › devops › aws-lambda-function-handler-in-nodejs
AWS Lambda Function Handler in Node.js - GeeksforGeeks
July 23, 2025 - Runtime: nodejs14.x · CodeUri: . Description: A simple Lambda function · Now, run the command. sam local invoke MyLambdaFunction --event event.json · The handler is the entry point for your AWS Lambda function. In simple terms, it's the function that will be invoked when the AWS Lambda service calls a function you've written.
Hevo
hevodata.com › home › learn › data strategy
NodeJS Lambda | The Complete Guide to Get Started 101
January 12, 2026 - If your AWS Lambda function has not changed and only a short time has passed since the last call, Lambda may reuse the container. This cuts down on the time it takes to start up the new container and your code inside it. The NodeJS Lambda function handler is the event-processing mechanism in your function code.
Stackify
stackify.com › aws-lambda-with-node-js-a-complete-getting-started-guide
AWS Lambda with Node.js: A Complete Getting Started Guide - Stackify
May 1, 2023 - # filename: serverless.yml service: ImageUploaderService # The `provider` block defines where your service will be deployed custom: bucket: getting-started-lambda-example provider: name: aws runtime: nodejs8.10 region: eu-west-1 stackName: imageUploader iamRoleStatements: - Effect: "Allow" Action: - "s3:PutObject" Resource: - "arn:aws:s3:::${self:custom.bucket}/*" # The `functions` block defines what code to deploy functions: UploadImage: handler: uploadImage.handler # The `events` block defines how to trigger the uploadImage.handler code events: - http: path: upload method: post cors: true environment: Bucket: ${self:custom.bucket} resources: Resources: StorageBucket: Type: "AWS::S3::Bucket" Properties: BucketName: ${self:custom.bucket}
GitHub
github.com › ZenitechSoftware › lambda-node
GitHub - ZenitechSoftware/lambda-node: Allows you to run your JavaScript code on any Node.js version in AWS Lambda.
Allows you to run your JavaScript code on any Node.js version in AWS Lambda. - ZenitechSoftware/lambda-node
Starred by 14 users
Forked by 2 users
Languages JavaScript 96.8% | Shell 3.2% | JavaScript 96.8% | Shell 3.2%
Docker Hub
hub.docker.com › r › amazon › aws-lambda-nodejs
amazon/aws-lambda-nodejs - Docker Image
AWS Lambda base images for NodeJS · Image · Languages & frameworks · Integration & delivery · 54 · 5M+ OverviewTags · AWS provided base images for Lambda contain all the required components to run your functions packaged as container images on AWS Lambda.