Ask HN: Why does AWS Lambda have a time limit?
Is the time limit something that we could potentially see removed in the future?
4 comments
Managing infrastructure that runs millions of programs in Turing-complete languages is a lot easier when execution time is known to be X, rather than potentially being infinite.
It also transfers a lot of complexity and responsibility for Lambda from AWS engineers onto the users of Lambda.
This setup makes sense to me, and I don’t see a need for it to change.
If you have really long-running processes, a different AWS service like Elastic Beanstalk (or your own self-hosted Lambda-like service) is a better fit.
It also transfers a lot of complexity and responsibility for Lambda from AWS engineers onto the users of Lambda.
This setup makes sense to me, and I don’t see a need for it to change.
If you have really long-running processes, a different AWS service like Elastic Beanstalk (or your own self-hosted Lambda-like service) is a better fit.
Thanks for the response!