Right now the only language/runtime supported is js/node, but they intend to include others.
(figured people would want to know this, and you have to scroll a ways to find out, so)
(figured people would want to know this, and you have to scroll a ways to find out, so)
The jokes ppl make are starting to get a bit more real: https://www.destroyallsoftware.com/talks/the-birth-and-death...
I published some explorations of that environment here: http://alestic.com/2014/11/aws-lambda-environment
Let me know in the comments on that article what other commands you'd like to see output for.
A quick back-of-the-envelope test on my machine for both node and python suggest similar (around 100 ms) start up times for the bare environments.
Do you just mean that you'd prefer to use node for smaller jobs anyway?
so maybe lambda its not suitable for things that are less than a few seconds.
I could write python with no django and try to structure things so they don't need database. but then I would have to take input from and put output data back to a queue of some sort.
>> A quick back-of-the-envelope test
and actually python on mine was even faster than node when both are doing nothing. so my assumption was wrong (but its based on mostly using django and all my node stuff is small servers and tools)
» time node noop.js node noop.js 0.04s user 0.01s system 98% cpu 0.045 total
» time python noop.py python noop.py 0.01s user 0.01s system 90% cpu 0.026 total
but importing significant numbers of libraries would be the real test.
the main benefits to lambda would still be:
- scaling for high demand - no cost for idle time
and let's not worry about the micro pennies in startup times