Re:Node v9.4.0
by appdrag on Wednesday January 10, 2018 @11:58AM
(#16116571)
AWS Lambda is still only supporting Node.js 6.10, they need to move faster...
[ Parent
| on HN ]
And Google Cloud Functions are running v6.11.5 [1]. Not much better. Ancient LTS release, and three months behind on patch release.
You can run any Linux binary you'd like if you bundle it yourself. Just use the built-in node runtime as a shim to run your process. It doesn't have to be newer node version Node either ... you can use it to run any standalone executable.
So this mean having a multi megabytes zip for the function instead of 1kb with a native runtime, this also affect cold start loading time of the lambda function ...
Does this really affect the cold start? Even if you use the native runtime it still is running in a separate container and you need to start the node process anyway. (Honest question, didn't measure it).
The size would definitely be affected.
True.
I read that someone builds a Reason/OCaml library with Node.js like API that compiles to native binaries, but uses OCaml standard libary functions in the background, which could probably get much smaller than Node.js.
Azure App Services / Functions support up to 8.9.3. They move pretty quick to add new node releases.
Bluemix's OpenWhisk has been much better about keeping up with Node.js releases FWIW. (I used to work for IBM.)