Simple execution model for server-side apps: each request is practically a separate process, sharing nothing with the others... so basically you can even have an infinite loop in the code specific for one request, some code calling an extension that leaks memory in the code for another etc. The bugs keep piling, but your app keeps mostly workin' ;)
It's in a way like lambda/serverless but on any random server.
I'm kind of sad this model of "shared nothing" + "something just runs your code" has never carried on to other more enjoyable languages...
> Simple execution model for server-side apps: each request is practically a separate process, sharing nothing with the others
It occurs to me that this isn’t a technical impossibility with JavaScript. It wouldn’t be difficult to write a library that spins up a new node process for each request. It’s just less efficient and goes against the grain of the language. (Having asynchronous IO)
