119 engineers on Hacker News describe using AWS Lambda first-hand: 42 endorse it, 15 regret it, 15 are mixed.
“there are times I regret my lambda decision and would prefer just a EC2 host even if it cost more. Deployment would be easier/simpler.”
mixed · production · joshstrange · 2026-10-13 · source ↗ · wrong label?“we use lambda/sfn/other services to process hundreds of millions of pages of data annually and it scales beautifully”
endorse · production · holler · 2026-10-13 · source ↗ · wrong label?“We run a screenshot API (ApiFlash) with Chromium packaged in an AWS Lambda container image instead of Firecracker on EC2.”
endorse · production · timojeajea · 2026-06-17 · source ↗ · wrong label?“We have natively image Lambda functions in production. Work well.”
endorse · production · bsan3 · 2025-12-31 · source ↗ · wrong label?“I have a ton of Node-based lambdas in prod, and while they're no speed demons, I'm quite surprised how bad it is compared to even interpreted things like Python.”
mixed · production · torginus · 2025-12-02 · source ↗ · wrong label?“before we switched to serverless cloud step function lambda craziness”
regret · production · junon · 2025-07-06 · source ↗ · wrong label?“a bunch of lambdas that handles all the backend. Overall it's been pretty great... The real issue with lambdas is limiting concurrency”
mixed · production · mannyv · 2025-03-15 · source ↗ · wrong label?“our costs went from $6K/month (on savings plans, evemn) of ec2 to ~$400/month in lambda, sqs, and elasticache/redis costs”
endorse · production · hylaride · 2025-01-09 · source ↗ · wrong label?“Much easier to let the lambdas run than have large running servers waiting. Autoscaling is possible, of course, but laggy autoscaling won't work”
endorse · production · sudhirj · 2024-06-23 · source ↗ · wrong label?“this is why we love AWS Lambda over ECS+Fargate”
endorse · production · irjustin · 2024-01-26 · source ↗ · wrong label?“the setup for sending something to a lambda feels like JCL boiler plate masturbation”
regret · production · LispSporks22 · 2023-12-29 · source ↗ · wrong label?“we used as the crux of our message scheduling and processing system”
endorse · production · sam0x17 · 2023-12-07 · source ↗ · wrong label?“I couldn't even stand having a dozen lambdas. ... Eventually, we moved to a "fat lambda" monolith”
regret · production · icedchai · 2023-12-06 · source ↗ · wrong label?“We've been using Lambda for ML serving low-volume CV models... for a couple of years at Roboflow and it is really good for low-volume and bursty use-cases... It gets really expensive relative to GPUs for high load”
mixed · production · 2 yr · yeldarb · 2023-11-16 · source ↗ · wrong label?“We use lambda at my work and we serve several million users a month. Lambda bill comes out to around 200$ a month”
endorse · production · willio58 · 2023-11-12 · source ↗ · wrong label?“Cost-wise we're pretty bursty, so it's saved us quite a bit. Lambda runtime is money”
endorse · production · ceejayoz · 2023-11-01 · source ↗ · wrong label?“we used AWS-specific managed services like Lambda, Dynamo, and SNS/SQS, which required MUCH less effort from DevOps.”
endorse · production · pwinnski · 2022-09-29 · source ↗ · wrong label?“Lambda. I've build multi-region endpoint compute services before. Never again.”
regret · production · nl · 2022-08-15 · source ↗ · wrong label?“I do currently enjoy not having to manage anything myself and I like that there's no internal abstractions”
endorse · production · politelemon · 2022-08-01 · source ↗ · wrong label?“We moved to Lambda for our async processing, there's been a few surprises, but it's been a very good experience overall.”
endorse · production · cube2222 · 2022-06-14 · source ↗ · wrong label?“we've seen good performance at low cost”
endorse · production · thesketh · 2022-04-25 · source ↗ · wrong label?“has taken lambda from being obtuse and glitchy to work with to quite a joy if you just lean on your framework.”
endorse · production · sam0x17 · 2021-12-16 · source ↗ · wrong label?“the scaling works quite well, there is no up-front infrastructure cost”
endorse · production · m_mueller · 2021-12-16 · source ↗ · wrong label?“after a couple of years of running a couple of serverless apps that rely heavily on a few AWS Lambdas”
endorse · production · 2 yr · fivea · 2021-11-20 · source ↗ · wrong label?“Yeah the caveats, gotchas, and workarounds you have to do to get something reasonable running on Lambda are just goofy.”
regret · production · VWWHFSfQ · 2021-10-12 · source ↗ · wrong label?“Each request is handled by a lambda, and even though these are memory intensive operations we never need to worry about servers or running out or RAM”
endorse · production · sudhirj · 2021-10-12 · source ↗ · wrong label?“I'm extremely happy with how it turned out... I pay something like $1 for 40-50k transcode operations.”
endorse · production · eldavido · 2021-10-12 · source ↗ · wrong label?“Checking in on those dozens of functions handling millions of invocations every month, and seeing them just chug along with no maintenance, has convinced me”
endorse · production · 6 yr · 015a · 2021-09-26 · source ↗ · wrong label?“Even "simple" things like Lambda underdeliver, just this week we run into problems using it with VPC, for example.”
regret · production · ratww · 2021-09-11 · source ↗ · wrong label?“We switched from deployment ... To runtime startup: lambda warmup time. And cost: RAM consumption is proportional to binary size”
mixed · production · fddhjjj · 2021-07-29 · source ↗ · wrong label?“AWS Lambda free minutes are well enough to run a B2B SaaS until like 300 paying customers.”
endorse · production · 4 yr · giorgioz · 2021-03-24 · source ↗ · wrong label?“we've been using Lambda / Step for a few years now and it's been highly robust, easy to understand”
endorse · production · 3 yr · abcxjeb284 · 2020-12-21 · source ↗ · wrong label?“We use more lambdas and for more things than are generally considered kosher... one more couldn't hurt.”
endorse · production · sten · 2020-12-15 · source ↗ · wrong label?“We use event-based analytics. A super easy way to do it is to create an AWS Lambda function that you can hit using a Rest API.”
endorse · production · catchmeifyoucan · 2020-12-10 · source ↗ · wrong label?“Zip file size limit has always been a big problem since we need to package a lot of dependencies.”
mixed · production · nuclid · 2020-12-01 · source ↗ · wrong label?“our lambda functions were routinely too large because the pandas branch of the dependency tree”
regret · production · throwaway894345 · 2020-08-13 · source ↗ · wrong label?“We discovered this the hard way once when an automatically generated function name or something was over the limit in prod”
regret · production · mandarg · 2020-05-10 · source ↗ · wrong label?“Not only price, but performance was horrible. Lambdas take forever to warm up (unacceptable for latency sensitive use cases).”
regret · personal · cj · 2019-09-23 · source ↗ · wrong label?“We switched to AWS serverless about a year ago (API gateway and Lambda) and there have been no real surprises.”
endorse · production · 1 yr · matchagaucho · 2019-09-23 · source ↗ · wrong label?“We switched to AWS Lambda functions for those cron jobs and they've never failed once.”
endorse · production · ordinaryperson · 2019-09-23 · source ↗ · wrong label?“for certain specific situations it's brilliant and I wouldn't want to give it up.”
endorse · production · kstrauser · 2019-09-23 · source ↗ · wrong label?“It was a nightmare getting certain Python libraries (eg. Pillow, psycopg) to work in the AWS Lambda environment”
regret · personal · The_Amp_Walrus · 2019-07-28 · source ↗ · wrong label?“Converted whole ad network to Serverless. Used Rust Lambda runtime for CPU intensive tasks.”
endorse · production · InGodsName · 2018-12-26 · source ↗ · wrong label?“You debug systems in prod with lambda just like you do with anything else - via a good logging infrastructure.”
endorse · production · scarface74 · 2018-12-19 · source ↗ · wrong label?“The big catch is that you don't control the containers, so there's no session stickiness.”
mixed · production · 2 yr · adzicg · 2018-12-19 · source ↗ · wrong label?“Creating a lambda is adding one function to your code.”
endorse · production · scarface74 · 2018-12-19 · source ↗ · wrong label?“none of the application we moved to AWS Lambda affected by these. ... Simple price calculations usually makes it clear what Lambda is not for.”
mixed · production · StreamBright · 2018-12-16 · source ↗ · wrong label?“We use both pre-process and on-the-fly depending on if we need hashes ahead of time.”
endorse · production · opwieurposiu · 2018-12-11 · source ↗ · wrong label?“Lambda Layers fixes so many problems! We had to hack around Lambda zip size limits.”
endorse · production · teej · 2018-11-29 · source ↗ · wrong label?“the poller between Kinesis -> Lambda just couldn't cope. This was discovered after lots of support calls with AWS.”
regret · production · djhworld · 2018-07-13 · source ↗ · wrong label?“We run binaries on our lambda instance with a go-based function, since Lambda allows for up to 250mb of binaries, 3gb ram and 30s max”
endorse · production · skunkworker · 2018-07-03 · source ↗ · wrong label?“we run all our Lambdas with the max 3GB memory both for peace-of-mind and because the underlying EC2 instances have significantly faster CPU”
mixed · production · 1.5 yr · not_kurt_godel · 2018-06-23 · source ↗ · wrong label?“I'm quite happy with the results.”
endorse · production · adzicg · 2018-02-27 · source ↗ · wrong label?“Just like any tool, Lambda is extremely effective when used for the things it excels at.”
endorse · production · RhodesianHunter · 2017-12-31 · source ↗ · wrong label?“We are using AWS Lambda in production heavily. It is basically an unhealthy hate and love abusive relationship.”
mixed · production · CSDude · 2017-12-31 · source ↗ · wrong label?“keeping my code as close to the business logic as possible - which is fairly easy with Lambda.”
endorse · production · laurentl · 2017-12-21 · source ↗ · wrong label?“Drawbacks I experience: Vendor lock-in... Cold/warm start: this is somewhat annoying.”
mixed · personal · Vinnl · 2017-12-21 · source ↗ · wrong label?“We use Lambda + API GW to manage the glue between our different data/service providers.”
endorse · production · laurentl · 2017-12-21 · source ↗ · wrong label?“we have switched to python for our FaaS but only because of lack of Ruby support from AWS lambda.”
regret · production · flowardnut · 2017-12-19 · source ↗ · wrong label?“Cold starts can be very problematic for latency sensitive scenarios when using languages/frameworks that startup slow.”
mixed · production · Rapzid · 2017-09-25 · source ↗ · wrong label?“We run many microservices on Lambda and it has been a pleasant experience for us.”
endorse · production · aeikenberry · 2017-06-21 · source ↗ · wrong label?“We run a beta / prod system to do testing and then for blue / green, we deploy a second function and switch the API Gateway over when we are good to go. Pretty straight forward”
endorse · production · Prefinem · 2017-06-21 · source ↗ · wrong label?“For everything else, Lambda and API Gateway have been fantastic... But we couldn't get along on a 100% Lambda backend”
mixed · production · gamache · 2016-12-05 · source ↗ · wrong label?“waiting for months for re:invent in the hope that it would be announced today, only to be disappointed... Python 3 support as an additional runtime?”
regret · production · scrollaway · 2016-12-01 · source ↗ · wrong label?“I use Lambda in production as a replacement for a cron server. So far, all it does is keep my cache warm. So far, no complaints.”
endorse · production · LePetitDev · 2016-11-21 · source ↗ · wrong label?“We gave it a run in prod and abandoned it quickly.”
regret · production · zbjornson · 2016-11-20 · source ↗ · wrong label?“It's really awesome to work with, you just deploy a function and quit worrying about it.”
endorse · production · avitzurel · 2016-11-20 · source ↗ · wrong label?“I've used Lambda in production under pretty high throughput conditions before. It's fairly stable”
endorse · production · Nimsical · 2016-11-20 · source ↗ · wrong label?“We run on top of AWS Lambda - if you choose. Lambda is great but there's still a TON of scaffolding and boilerplate to get your APIs up and running”
mixed · production · altsang · 2016-10-13 · source ↗ · wrong label?“We reduced our service server costs to 1/6th by moving from Heroku to Lambda.”
endorse · production · pksunkara · 2016-10-11 · source ↗ · wrong label?“Once you move beyond a single region on a single account, things get a lot harder.”
mixed · production · falcolas · 2016-10-11 · source ↗ · wrong label?“Lambda does not support versioning... the minute I change it for my staging/test/qa environment, I have changed it for production as well. So, I can't roll back easily.”
regret · production · cargomaster · 2015-07-16 · source ↗ · wrong label?“At $DAYJOB, we used to have a few internal use Azure Functions (which we've migrated to AWS Lambda).”
neutral · production · Kwpolska · 2025-12-14 · source ↗ · wrong label?“mostly I deploy Docker containers to various managed services on AWS - Lambda, ECS, etc.”
neutral · production · raw_anon_1111 · 2025-12-04 · source ↗ · wrong label?“We've migrated to a serverless architecture using Lambda and Step Functions to handle scaling.”
neutral · production · buzzbyjool · 2025-05-09 · source ↗ · wrong label?“It's not much different from how we as programmers use things like Cloudflare or AWS Lambda.”
neutral · production · weitendorf · 2024-12-02 · source ↗ · wrong label?“some AWS Lambda functions, some CLI tools, our Terraform repo”
neutral · production · pxc · 2024-11-27 · source ↗ · wrong label?“Yes, we use something similar for debugging lambdas locally.”
neutral · production · SamuelAdams · 2024-07-12 · source ↗ · wrong label?“we have built a simple event system in top of lambda functions, sqs, s3, eventbridge etc”
neutral · production · fennecbutt · 2024-06-22 · source ↗ · wrong label?“We started actually on AWS Lambda. We are on a mix of AWS EC2 and EKS now, all autoscaled per region”
neutral · production · tnolet · 2024-06-07 · source ↗ · wrong label?“AWS had dropped support for $runtime in Lambda, and it became impossible to upgrade the CloudFormation template.”
neutral · production · bvanderveen · 2023-04-27 · source ↗ · wrong label?“we switched to using a little URL shortening service that we wrote on aws lambda+dynamodb”
neutral · production · tonto · 2023-01-09 · source ↗ · wrong label?“which auths through a random lambda who knows where on what server”
neutral · production · _gabe_ · 2022-12-10 · source ↗ · wrong label?“we replaced our data orchestration with a stateless lambda”
neutral · production · geertj · 2022-08-02 · source ↗ · wrong label?“to send your docker to Lambda for inference and Batch/Colab for training”
neutral · production · lysecret · 2022-03-04 · source ↗ · wrong label?“We used Dynamo, ElasticSearch, Lambda and could make it running in 60 days”
neutral · production · artembugara · 2022-01-20 · source ↗ · wrong label?“the lambda itself is an express app with a single route defined”
neutral · production · retrocryptid · 2021-12-31 · source ↗ · wrong label?“We also have a series of Lambda functions that handle uploaded audio/video file prep”
neutral · production · rememberlenny · 2021-12-06 · source ↗ · wrong label?“there are plugins for running the lambdas locally as well as for dynamodb, sqs, ses and eventbridge.”
neutral · production · wdfx · 2021-12-03 · source ↗ · wrong label?“We run mostly on AWS - essentially Lambda/API Gateway/SageMaker etc”
neutral · production · jedwhite · 2021-06-11 · source ↗ · wrong label?“In prod I map a custom domain to the lambda, routing is done internally to the function.”
neutral · production · mozey · 2021-04-19 · source ↗ · wrong label?“If we talk about lambdas because that's where the business logic lies in a "serverless" architecture”
neutral · production · andreineculau · 2021-04-18 · source ↗ · wrong label?“But I have to deploy stub functions and have a different deployment model for prod.”
neutral · production · jedberg · 2021-03-02 · source ↗ · wrong label?“we rarely have upstream changes to the lambdas configuration / parent environments themselves”
neutral · production · leetrout · 2020-12-31 · source ↗ · wrong label?“Lambda (for processes where we needed to scale from 0 to $alot”
neutral · production · scarface74 · 2020-12-20 · source ↗ · wrong label?“Thanks, I have not heard of AWS Lambda before.”
neutral · personal · trinovantes · 2020-11-21 · source ↗ · wrong label?“We use terraform and terragrunt by themselves to deploy lambdas.”
neutral · production · lovehashbrowns · 2020-10-12 · source ↗ · wrong label?“Now that we are using Lambda a lot, the SpringBoot is long in the tooth when it comes to cold boot times”
neutral · production · blntechie · 2020-09-25 · source ↗ · wrong label?“ses is still useful for processing incoming email via Lambda”
neutral · production · statictype · 2020-01-04 · source ↗ · wrong label?“deployment to AWS Lambdas via CloudFormation commands (also invoked by Make) really simple.”
neutral · production · finaliteration · 2019-12-08 · source ↗ · wrong label?“it's the main database we use along with Lambdas”
neutral · production · topicseed · 2019-12-04 · source ↗ · wrong label?“Our entire environment is AWS CodeBuild, CodePipeline, and Lambda-based”
neutral · production · cddotdotslash · 2019-11-03 · source ↗ · wrong label?“the Lambda front end validates and routes, the backend replies”
neutral · production · KaiserPro · 2019-07-31 · source ↗ · wrong label?“our newer code is .NET Core, and we run it on AWS Lambda.”
neutral · production · lancefisher · 2019-06-23 · source ↗ · wrong label?“We've been using amazon cognito with lambda authorizers.”
neutral · production · InGodsName · 2018-12-27 · source ↗ · wrong label?“I learned and brought in production the followings: AWS Cloudflare and Lambda (with Go)”
neutral · production · apeacox · 2018-12-23 · source ↗ · wrong label?“Serverless (AWS Lambda, zeit.co)... I'm finding it easier to stick with older methods”
neutral · personal · maliker · 2018-12-23 · source ↗ · wrong label?“We use pools in lambdas to Amazon Aurora and it works out fine.”
neutral · production · dlhavema · 2018-12-15 · source ↗ · wrong label?“@matterapp/lambdas: Our background jobs system.”
neutral · production · keremkazan · 2018-12-05 · source ↗ · wrong label?“It could easily be made "serverless" by uploading the same service with minor changes to AWS Lambda.”
neutral · personal · Diggsey · 2018-12-04 · source ↗ · wrong label?“Honestly, for everything we are currently running on Lambda.”
neutral · production · Tehnix · 2018-11-29 · source ↗ · wrong label?“I haven't even been using a shim to run my Rust binaries. Just statically link them”
neutral · production · staticassertion · 2018-11-29 · source ↗ · wrong label?“We run ETL pipelines and have lambda as a component of that, maybe 250k-500k invocations a day.”
neutral · production · djhworld · 2018-10-31 · source ↗ · wrong label?“I've been using Zappa for a few side projects and even at work”
neutral · production · smoll · 2017-12-14 · source ↗ · wrong label?“We use Lambda for our event processing pipeline and also for our GraphQL API consumed by our clients”
neutral · production · leetbulb · 2017-12-05 · source ↗ · wrong label?“For large scale tests we run https://goad.io on lambdas.”
neutral · production · social_quotient · 2017-11-19 · source ↗ · wrong label?“are now experimenting with running Chrome Headless in Lambda, for economic and concurrency reasons.”
neutral · personal · donaltroddyn · 2017-11-17 · source ↗ · wrong label?“I wrote Gimel[0] - an A/B testing backend using Labmda and Redis... It's used in production for a few months now”
neutral · production · gingerlime · 2016-11-20 · source ↗ · wrong label?“a dynamic image thumbnail generator that runs on Lambda”
neutral · production · rmccue · 2016-11-01 · source ↗ · wrong label?