6 ms·
It may just be such a basic tenant of the platform that no one thought to. You stop getting billed after lambda returns a response so why would you expect compu
by somethingAlex 1y ago
It may just be such a basic tenant of the platform that no one thought to. You stop getting billed after lambda returns a response so why would you expect computation to continue? This guy expected free lunch.
- charcircuit 1y agoI don't see that on the main AWS Lambda pages. It just says that you pay for what you use. It would make sense that the time billed would be until there is no more code to execute.
- meepmorp 1y agoYeah, but if you actually read the developer documentation, they explain the execution model pretty extensively.
- everfrustrated 1y agoDevelopers will do anything except read the documentation.
- meepmorp 1y agoSo many times I've caught myself thinking "I don't want to understand this shit, I just wanna fix it," as I've grudgingly opened up whatever docs I've avoided reading; almost as many times as I've wondered "what fucking moron wrote this code" before immediately `git blame`ing myself.
- somethingAlex 1y agoFair enough, I guess this just seems like a bold assumption to make since an explicit handler function is a cornerstone of lambda, rather than being able to run module level code and having the end self detected.
- nemothekid 1y ago>until there is no more code to execute What does "no more code to execute" mean to you? How would you define that?
- Hikikomori 1y agoIn the context of lambda, when you return.
- charcircuit 1y agoEssentially !uv_loop_alive, when the event loop will exit.