Since AWS controls when the function is expired from warm start to cold start, it’s a guarantee they’re going to become extra aggressive about terminating idle functions.
Why leave customer code loaded for free when you can charge for startup again?
this post was submitted on 30 Apr 2025
36 points (95.0% liked)
Programming
19912 readers
125 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 2 years ago
MODERATORS
That's an inherent problem with serverless/functions as a service. There's no guarantee at all on it staying warm for a given amount of time and any system that depended on it without paying for provisioned concurrency was just depending on hopes and dreams.
This just means more people will set up Eventbridge rules to call lambdas regularly and keep them running. You avoid having to pay the time penalty and now, actual financial cost of a cold start.
Ah yes, keeping your Lambda functions running, rendering the main benefit of them pointless 🙃
People really should just set up a Fargate task instead...
Yeah I often see devs come up with complex architectures to just work around Lambda's limitations. Things to keep them warm (but then fail because they don't account for concurrent requests still hitting cold starts), multiple levels of Lambda functions to work around 15 minute time outs, and more. Just use the right tool for the job and look at Fargate or Batch.