41
AWS Lambda now charges for INIT Phase
(aws.amazon.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 30 Apr 2025
41 points (97.7% liked)
Programming
21000 readers
48 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 !webdev@programming.dev
founded 2 years ago
MODERATORS
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.