Are you willing to compare your approach to for example Lambda's approach, where the user gets an actual real Linux VM. with zero differences (Work that, incidentally was in part contributed to Linux by Google!), as opposed to a Linux emulator?
This is based on gVisor (https://github.com/google/gvisor), but it does not use the ptrace sandboxing that is in the mainline open source project. Our First Generation runtimes (aka nacl) were based on ptrace. In our informal testing we have observed the Second Generation runtimes to be about 20% faster than the First Generation. I don't have benchmarks on how it compares to a raw VM.
These new runtimes are capable of multithreading, so long as the language is capable of it. And you will need to use an instance larger than the default (F1 / B1) to have access to more than one thread.
App Engine Flex is a version of App Engine that uses VMs with Linux. You can find a comparison between the standard and flexible environments here:
https://cloud.google.com/appengine/docs/the-appengine-enviro...
AWS> we put your code in a container, like everyone else puts your code in a container. We bikeshedded the Linux distro a bit, so you might need to recompile
Customer> OK. Fine
GCP> our web scale open source userland kernel hypervisor written in Go hosts your code in a Linux-but-not-quite-Linux microservice
Customer> Why does <X> system call return a strange error code?
GCP> You're too dumb to understand. Trust us
Customer> oh, I think I understand well enough. Calls back Azure sales rep
it's still Python 2.7 only :(
Did you mean "disclosure"?
Disclosure would work just as well, and is in fact more accurate!
That's precisely why I objected to its use in the context it was used here (and other places where it is colloquially used incorrectly): by announcing you worked on something, you reinforce the possibility of bias in the post while taking partial responsibility for the work--it does not disclaim or subtract bias or responsibility.
> the word does deny something: possibly objectivity.
i.e. there is a possibility of bias.
That said, I've made my peace about the "proper" use of language, or rather, the lack thereof, and now espouse it.
Like, literally.
The meanings of words and idioms shift over time. As long as we're understood well enough, that's fine by me.
Using gVisor, instead of NaCL, as the sandboxing technology, shipping new runtimes becomes a much more tractable task with less differences from the "plain" runtime. In fact, gVisor allows us to use the runtime unmodified.
This in turn, decreases the "lock-in". There are still decisions we need to make depending on the runtime, e.g. which package manager to use if there isn't a community default.
Hopefully, the narrative for "Serverless" moves beyond lambda and functions. Sometimes (!) we want apps, databases, caches and more to be "Serverless" :-)
Disclaimer: I work at Google, on the App Engine Runtimes team. I helped ship this