#Serverless is a somewhat unhelpfully misleading term for "highly scalable stateless code"
-
-
it’s trivial to restrict access to file system and other OS functions, which makes it safer to run other people’s code in your environment
-
it’s been a feature of the language from day 0, as opposed to Ruby/Python/etc which aren’t designed for running untrusted code
-
Heroku has used Linux sandboxing facilities to implement this concept for ages: https://12factor.net/processes (Heroku apps are 12 factor)
-
"Serverless" postdates LXC and Docker so "easy to sandbox" can't be the distinction, right?
-
i think it’s that you can avoid process startup overhead and may even not need to fully sandbox at the OS level
-
You still need to sandbox because JS isn't useful without some exposed OS guts and security is hard ;)
-
My hypothesis is: 1. Serverless is, more or less, definitionally about JS 2. It's popular because JS is popular and empowering
-
I think the extremely fast startup time of a container running node was crucial to the order of magnitude change I mentioned.
- 6 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.