Tag feed

#aws

27,264 posts143,408 followers

Trending tags this week

Leading a 5-Week AWS Cloud Club Workshop Series

As the Technical Lead at the AWS Cloud Club (FAST NUCES Peshawar), I believe students shouldn't just learn theory they should build. I’ve spent the last few weeks planning and executing a 5 week hands

Join discussion

CDChloe DumontFeb 25

0

Lambda@Edge vs CloudFront functions. Edge won.

We were doing request validation and header manipulation on Lambda@Edge for a year. cold starts killed us during traffic spikes, even with provisioned concurrency. switched to CloudFront functions las

Join discussion

PSPriya SharmaFeb 25

0

AWS Lambda isn't a silver bullet and y'all keep shipping garbage because of it

been cleaning up after lambda migrations for two years now. everyone wants "serverless" until they realize cold starts at 3am cost them $50k in lost transactions. or they hit the 15-minute timeout on

Join discussion

MCMarcus ChenFeb 25

8

We got woken up at 3am because our Lambda timeouts spiked 400% after a deploy

We'd switched to Node 18 runtime and figured cold starts would be fine. They weren't. A function that usually runs in 200ms was taking 8-12 seconds on cold starts. Our traffic spikes at night (asia ti

SJPSSophia and 7 more commented

PSPriya SharmaFeb 25

7

Serverless cold starts are way worse than anyone tells you until production hits

Been running a gRPC service on Lambda for 18 months. Cold starts were killing us - median 3.2s, p99 hitting 8s. Customers noticed. We tried the obvious stuff first (provisioned concurrency, bigger mem

CATDChloe and 6 more commented

RMRavi MenonFeb 25

0

Are you really losing sleep over lambda cold starts

So I keep seeing people optimize their serverless stacks to death around cold starts. Provisioned concurrency, container images instead of zips, custom runtimes, warmer functions every minute. The mat

Join discussion

SRSofia RodriguezFeb 25

0

Spent two weeks optimizing cold starts on our Lambda functions, cut them from 1.8s to 340ms

We ship a React component library as Lambda@Edge for dynamic header/footer injection. Cold starts were killing us in prod, especially during traffic spikes. Started with the obvious stuff: smaller bun

Join discussion

TLTom LindgrenFeb 25

0

Built a DynamoDB single-table thing, it's worse than I thought

Recently shipped a feature that required denormalizing a whole domain into one table. GSIs everywhere, composite keys, the whole mess. We were coming from postgres so the mindset shift was brutal. her

Join discussion

PSPriya SharmaFeb 25

0

Everyone pretending Lambda cold starts don't matter

The amount of cargo cult "best practices" around Lambda is exhausting. Keep your functions under 50MB, use provisioned concurrency, minimize dependencies, blah blah. Yeah, and sometimes a cold start j

Join discussion

JPJenna PedersonOct 19, 2020

35

Ask an AWS Developer Advocate!

Hey folks! Ever wondered how to determine the right resources for your Lambda function? Or why one might use AWS Amplify over hosting your static site directly on S3? Maybe you’re trying to get started with AWS or you’re wondering where to find the A...

CNSAIcharless and 34 more commented

#aws

Search Hashnode

#aws

Trending tags this week

Leading a 5-Week AWS Cloud Club Workshop Series

Lambda@Edge vs CloudFront functions. Edge won.

AWS Lambda isn't a silver bullet and y'all keep shipping garbage because of it

We got woken up at 3am because our Lambda timeouts spiked 400% after a deploy

Serverless cold starts are way worse than anyone tells you until production hits

Are you really losing sleep over lambda cold starts

Spent two weeks optimizing cold starts on our Lambda functions, cut them from 1.8s to 340ms

Built a DynamoDB single-table thing, it's worse than I thought

Everyone pretending Lambda cold starts don't matter

Ask an AWS Developer Advocate!