AWS Lambda Web Functions let developers deploy Node.js web apps without adapters

New model supports concurrent requests and response streaming, billed for active CPU time

By LineZotpaper

Published23 October 2026

Read Time3 min

AWS has introduced Lambda Web Functions, a new service that lets developers run standard Node.js web applications built with frameworks such as Express and Hono directly on Lambda, with concurrent request handling, response streaming and billing based on active CPU time rather than time spent waiting on downstream services.

AWS has introduced Lambda Web Functions, allowing developers to run Node.js web applications using frameworks such as Express and Hono directly on Lambda. According to AWS's documentation, the new functions support concurrent HTTP requests and response streaming. Multi-Region routing directs requests to the closest Region, while a single warm execution environment can handle multiple concurrent requests, significantly reducing cold starts. Existing Lambda functions are now called Lambda Event Functions, with no changes required.

Micah Walter, senior solutions architect at AWS, summarized the benefits: "You can take a standard port-listening server built with Express, Hono, Fastify, Next.js, or any Node.js framework, deploy it with a single command, and Lambda automatically handles scaling, multi-region distribution, and active CPU billing. No adapters, no infrastructure to manage, and no framework lock-in."

Endpoints use a Lambda-provided domain by default. To use a custom domain, edge caching, or AWS WAF, developers can put Amazon CloudFront in front, relying on Lambda Web Functions as the origin. The service targets HTTP workloads including full-stack web applications, REST and GraphQL APIs, and independently scaling microservices. It also supports server-side rendering and streaming responses, such as incremental output from large language models, without a separate hosting layer.

Lambda Web Functions currently support only Node.js; Python, Java, and .NET remain available through traditional Lambda functions. Earlier this year, AWS also launched Lambda MicroVMs, which provide isolated, stateful sandbox environments for running untrusted or user-generated code.

In an article exploring the new service, Julian Wood, Kim Wendt, and Samrat Karak wrote: "Lambda Web Functions bring the serverless operating model to web applications without adapter layers. You write a standard Node.js HTTP server, deploy it with one command or CloudFormation, and get a scalable, pay-per-use HTTPS endpoint with global routing built in."

Community reactions on Reddit and Hacker News have been largely positive, highlighting the simpler programming model and support for concurrent requests. Discussions also raised questions about Python support and how the service differs from existing alternatives. One commenter, magnetik79, noted the shift in the programming model: "now you're no longer working with one invoke/one request - now you might need to be sync/mutex aware."

Pricing for Lambda Web Functions is based on active CPU time and memory usage, with memory billed for the lifetime of the execution environment. Google Cloud Run and Azure Container Apps offer similar models with scale-to-zero and configurable concurrency. The service is currently available in five regions: Northern Virginia, Ohio, Oregon, Tokyo, and Ireland.

Analysis

Why This Matters

Lambda Web Functions change the serverless programming model: a single execution environment handles many concurrent requests, which changes how developers must think about concurrency and state.
The service removes the need for API Gateway and adapter layers for many web workloads, simplifying deployment of standard Node.js frameworks.
Billing for active CPU time rather than waiting time could reduce costs for I/O-heavy workloads, including API backends and streaming AI inference.

Background

Serverless computing has traditionally been built around one event, one invocation and one request, with web frameworks like Express requiring adapter layers to run on Lambda. The new offering extends the serverless operating model to standard Node.js HTTP servers. Similar models already exist elsewhere: Google Cloud Run and Azure Container Apps support web applications without adapter layers, scale-to-zero, and configurable concurrency, making them suitable for intermittent or bursty traffic.

Key Perspectives

Developers: Welcome the simpler programming model, reduced cold starts, and the ability to skip API Gateway for many workloads, but face a new concurrency model that requires sync and mutex awareness, and are asking for support beyond Node.js.

AWS: Positions Lambda Web Functions as removing complexity and framework lock-in, with managed scaling, multi-region distribution, and pay-per-use billing, and points to earlier launches such as Lambda MicroVMs as part of a broader serverless push.

Critics and skeptics: Question the lack of Python support and how the service differs from existing alternatives such as Google Cloud Run and Azure Container Apps, which already offer comparable capabilities.

What to Watch

Whether AWS extends Lambda Web Functions beyond Node.js to Python, Java, and .NET.
Adoption and real-world cost comparisons, particularly for streaming AI inference and I/O-heavy workloads.
How Lambda Web Functions compete with Cloud Run and Azure Container Apps as the serverless web hosting model matures.

Sources

AWS Introduces Lambda Web Functions for Node.js Applications · InfoQ

Checked

12 claims in this story checked against 1 source: 11 supported.

Show each claim

SupportedLambda Web Functions let developers deploy Node.js web apps without adapters.InfoQ: “Lambda Web Functions bring the serverless operating model to web applications without adapter layers. You write a standard Node.js HTTP server, deploy it with one command or CloudFormation”
Partly supportedThe service supports concurrent requests and response streaming, and is billed for active CPU time rather than time spent waiting on downstream services.InfoQ: “They charge for active CPU time and memory, rather than CPU time spent waiting on downstream services.”
SupportedAWS introduced Lambda Web Functions for running Node.js web apps, including apps built with Express and Hono, directly on Lambda.InfoQ: “AWS recently introduced Lambda Web Functions, allowing developers to run Node.js web applications using frameworks such as Express and Hono directly on Lambda”
SupportedMicah Walter said developers can deploy a standard Node.js server with one command and Lambda handles scaling, multi-region distribution and active CPU billing, with no adapters or framework lock-in.InfoQ: “You can take a standard port-listening server built with Express, Hono, Fastify, Next.js, or any Node.js framework, deploy it with a single command, and Lambda automatically handles scaling, multi-region distribution, and active CPU billing. No adapters, no infrastructure to manage, and no framework lock-in.”
SupportedMicah Walter is a senior solutions architect at AWS.InfoQ: “Micah Walter, senior solutions architect at AWS, summarizes the benefits”
SupportedMulti-Region routing directs requests to the closest Region, and one warm execution environment can handle multiple concurrent requests, significantly reducing cold starts.InfoQ: “Multi-Region routing directs requests to the closest Region, while a single warm execution environment can handle multiple concurrent requests, significantly reducing cold starts.”
SupportedExisting Lambda functions are now called Lambda Event Functions, with no changes required.InfoQ: “Existing Lambda functions are now called Lambda Event Functions, with no changes required.”
SupportedWood, Wendt and Karak wrote that Lambda Web Functions bring the serverless operating model to web applications without adapter layers, and provide a scalable, pay-per-use HTTPS endpoint with global routing.InfoQ: “Lambda Web Functions bring the serverless operating model to web applications without adapter layers. You write a standard Node.js HTTP server, deploy it with one command or CloudFormation, and get a scalable, pay-per-use HTTPS endpoint with global routing built in.”
SupportedMagnetik79 wrote that users may need to be sync/mutex aware because the model is no longer one invoke per request.InfoQ: “now you're no longer working with one invoke/one request - now you might need to be sync/mutex aware.”
SupportedLambda Web Functions currently support only Node.js; Python, Java and .NET remain available through traditional Lambda functions.InfoQ: “Lambda Web Functions currently support only Node.js; other languages, including Python, Java, and .NET, remain available through traditional Lambda functions.”
SupportedAWS launched Lambda MicroVMs earlier this year for isolated, stateful sandboxes that run untrusted or user-generated code.InfoQ: “Earlier this year, AWS also launched Lambda MicroVMs, which provide isolated, stateful sandbox environments for running untrusted or user-generated code”
SupportedLambda Web Functions are currently available in Northern Virginia, Ohio, Oregon, Tokyo and Ireland.InfoQ: “The service is currently available in five regions: Northern Virginia, Ohio, Oregon, Tokyo, and Ireland.”