Ask HN: Why does AWS Lambda have a time limit?

Re:Ask HN: Why does AWS Lambda have a time limit? by smt88 on Wednesday November 07, 2018 @12:59PM (#18400852)

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.

[ Parent | on HN ]

Re:Ask HN: Why does AWS Lambda have a time limit? by QuinnyPig on Wednesday November 07, 2018 @03:21PM (#18402048)

It’s certainly a creative answer to the Halting Problem!

[ Parent | on HN ]

Re:Ask HN: Why does AWS Lambda have a time limit? by smt88 on Wednesday November 07, 2018 @04:19PM (#18402505)

Parse.com did the same thing, as did all of those old-school PHP hosts, so it's been a common solution for at least the 22 years I've been using hosting services -- maybe longer.

[ Parent | on HN ]

Re:Ask HN: Why does AWS Lambda have a time limit? by johnnyodonnell on Wednesday November 07, 2018 @02:05PM (#18401349)

Thanks for the response!

[ Parent | on HN ]