AWS Lambda Silent Crash – A Platform Failure, Not an Application Bug [pdf]

Re:AWS Lambda Silent Crash – A Platform Failure, Not an Appl... by kevin_nisbet on Monday July 14, 2025 @10:56PM (#44567460)

I don’t know about node but a fun abuse of this is background tasks can still sometimes run on a busy lambda as the same process will unsuspend and resuspend the same process. So you can abuse this sometimes for non essential background tasks and to keep things like caches in process. You just cant rely on this since the runtime instead might just cycle out the suspended lambda.

[ Parent | on HN ]

Re:AWS Lambda Silent Crash – A Platform Failure, Not an Appl... by johnduhart on Monday July 14, 2025 @11:01PM (#44567489)

Absolutely, I do this at $dayjob to update feature flags and refresh config. Your code just needs to understand that such execution is not guaranteed to happened, and in-flight requests may get interrupted and should be retried.

[ Parent | on HN ]

Re:AWS Lambda Silent Crash – A Platform Failure, Not an Appl... by lbreakjai on Tuesday July 15, 2025 @04:38AM (#44569182)

I wouldn't really call this an abuse. I remember their documentation mentioning it.

[ Parent | on HN ]

Re:AWS Lambda Silent Crash – A Platform Failure, Not an Appl... by __turbobrew__ on Tuesday July 15, 2025 @11:27PM (#44578407)

TiTiler does exactly that. Geospatial rasters are stored in S3, and the lambda retains a cache in memory of loaded data from S3. So if the same lambda execution is used it can return cached data without hitting S3.

[ Parent | on HN ]