Amazon Web Services has introduced Lambda Web Functions, a new serverless option that runs standard Node.js HTTP applications without requiring developers to convert them into event handlers or add a framework-specific adapter.
Applications built with frameworks such as Express, Hono, Fastify and Next.js can listen on a port and be deployed through the AWS command line. AWS says the service handles scaling, HTTPS endpoints and optional multi-region distribution.
A third Lambda execution model
AWS now separates Lambda into three forms. Event Functions retain the familiar single-concurrent, event-driven handler model. Web Functions use an HTTP-native model with multiple concurrent requests in one environment. Lambda MicroVMs provide customer-managed, stateful sandboxes for isolated code execution.
Web Functions are intended for API backends, server-side rendering and other interactive HTTP workloads. AWS says each execution environment can process as many as 128 requests concurrently, allowing bursts of traffic to share warm capacity.
The billing model also differs from traditional Lambda execution. CPU time is metered while application code is actively using the processor, while memory remains metered for the lifetime of the environment. AWS argues that this can reduce compute costs for I/O-heavy applications that spend significant time waiting for databases, external APIs or streamed responses.
Deployment and traffic controls
The AWS CLI can package an application, create the Web Function, publish an immutable revision and attach an HTTPS endpoint through a single deployment command. The runtime provides an environment variable containing the host and port on which the application must listen.
Developers can deploy revisions to several AWS regions and use one global URL. Requests are routed to a nearby region on a best-effort basis. Endpoints can point to one revision or divide traffic among revisions, giving teams a mechanism for staged rollouts.
AWS says Web Functions use the same Firecracker isolation technology as its other Lambda execution models. The product removes several pieces of infrastructure work, but developers still need to assess cold-start behavior, database connection limits, regional dependencies and the combined cost of memory, CPU and data transfer.
What changes for serverless development
The main shift is compatibility with the way many web applications already run. Instead of reshaping an HTTP server into an event contract, teams can use a familiar port-listening process and standard framework behavior.
That may lower the migration barrier for smaller APIs and full-stack applications, although it does not make every long-running server workload a natural serverless candidate. Applications that depend on persistent local state, specialized networking or predictable reserved capacity may still fit containers or virtual machines better.
Source: AWS: Announcing AWS Lambda Web Functions.
Featured image: AI-generated editorial illustration by Bex News.
