AWS Lambda
Amazon's serverless compute service that runs code in response to events without managing servers.
Liked for running whole web apps as single functions behind adapters,123 instant scaling for bursty or large workloads,45 and very low cost at modest traffic.67 The main caveats are added complexity when an app is split into many functions,89 plus surprise charges and higher costs than dedicated servers for steady loads.101112
Why people recommend it
Monolith web apps · 3
Commenters run whole web apps in one function via Axum, Fastify, Hono or Express adapters.
“I treat Lambda purely as compute and ignore everything else related to "serverless".”
“at almost 15 million requests per month the cost is under $10/mo”
Show 1 more
“shove Hono/Express/Fastify into a lambda with some shim/adapter”
Container deploys · 3
Docker images deploy smoothly and can be tested locally first.
“I’ve always deployed node.js docker images for aws lambda and had pleasant experience”
“I treat Lambda purely as compute and ignore everything else related to "serverless".”
Show 1 more
I know just enough about Kubernetes to not sound like an idiot when I’m in the room and mostly I deploy Docker containers to various managed services on AWS - Lambda, ECS, etc. But, as a lead for implementations, I just couldn’t in good conscience permit something that is not an industry standard and not supported by my cloud provider. First from a self interested standpoint, it looks a lot better on their resume to
Instant scaling · 2
It handles sudden traffic spikes and very large processing volumes well.
“you cannot beat the instant scale of Lambdas.”
“we use lambda/sfn/other services to process hundreds of millions of pages of data annually and it scales beautifully”
Low cost · 2
Users report near-zero bills, including under $10/mo at about 15M requests.
“at almost 15 million requests per month the cost is under $10/mo”
“I've built 2 applications using Lambdas as a backend and I love how simple and it is.”
Low maintenance · 2
No servers to manage, and it is easy for a small team to maintain.
“I've built 2 applications using Lambdas as a backend and I love how simple and it is.”
“we use lambda/sfn/other services to process hundreds of millions of pages of data annually and it scales beautifully”
Event automation · 1
Webhooks can trigger functions for tasks like rebuilding a static site.
“trigger an AWS Lambda which, on merge to main, automatically pulled in the repo”
Caveats and dissent
Architecture complexity · 2
One function per route and microservice sprawl make packaging and management harder.
“shove Hono/Express/Fastify into a lambda with some shim/adapter”
“I used both for years. Nothing beats VPS/bare metal.”
Surprise charges · 1
One user was billed for an automatically added add-on while on the free tier with almost no traffic.
“almost no traffic (few requests per day), on free trier and YET I had to pay for the add-on they automatically added”
Steady-load cost · 2
For consistent loads, dedicated EC2 instances or a VPS can be cheaper or simpler.
“you cannot beat the instant scale of Lambdas.”
“I used both for years. Nothing beats VPS/bare metal.”
Often compared with
Who recommends it in their own words
Threads where it came up
- AWS Lambda Web Functions 6 mentions
- We charge $10k a week to delete AI-generated code 1 mention
- I returned to AWS, and was reminded why I left 1 mention
- Ask HN: Should I learn Docker to deploy my app in VPS? 1 mention
- Jeffgeerling.com has been Migrated to Hugo 1 mention
- Python Workers redux: fast cold starts, packages, and a uv-first workflow 1 mention
Data: aws-lambda.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 12
“I treat Lambda purely as compute and ignore everything else related to "serverless".”
“at almost 15 million requests per month the cost is under $10/mo”
“I've built 2 applications using Lambdas as a backend and I love how simple and it is.”
“we use lambda/sfn/other services to process hundreds of millions of pages of data annually and it scales beautifully”
“you cannot beat the instant scale of Lambdas.”
“shove Hono/Express/Fastify into a lambda with some shim/adapter”
“almost no traffic (few requests per day), on free trier and YET I had to pay for the add-on they automatically added”
“there definitely is a sweet spot where it can work well”
“I’ve always deployed node.js docker images for aws lambda and had pleasant experience”
“trigger an AWS Lambda which, on merge to main, automatically pulled in the repo”
“I used both for years. Nothing beats VPS/bare metal.”
I know just enough about Kubernetes to not sound like an idiot when I’m in the room and mostly I deploy Docker containers to various managed services on AWS - Lambda, ECS, etc. But, as a lead for implementations, I just couldn’t in good conscience permit something that is not an industry standard and not supported by my cloud provider. First from a self interested standpoint, it looks a lot better on their resume to