3 ms·
Regarding the WebAssembly part, it seems to me that native Linux code sandboxed by seccomp would work just as well if not better, and has been available since 2
by devit 8y ago
Regarding the WebAssembly part, it seems to me that native Linux code sandboxed by seccomp would work just as well if not better, and has been available since 2005 (and there's also NaCL if you want in-process, as well as a bunch of VMs).
So I think the reason for "CloudFlare workers" not being available ten years ago has to be found somewhere else.
- steveklabnik 8y agoThere's pros and cons, like anything else. For some more details about why specifically Workers uses V8 and Isolates, I recommend this talk: https://www.infoq.com/presentations/cloudflare-v8 https://www.infoq.com/presentations/cloudflare-v8 Specifically, > But the kind of scalability I'm talking about here is scalability to the number of tenants, the number of applications that we can be hosting at one time. The challenge with this is that, again, we don't want people to choose one or two or five locations where their software runs; we want it to run everywhere. We want everyone's code running in every one of our locations. And some of our locations are not that big. Though some have lots and lots of computers, but others have maybe a dozen machines. How do you fit- we have 10 million customers- on a dozen machines? Turns out that the existing technologies for this, the existing server-side technologies, don't live up to the task. What we really need is basically 100X efficiency gain in number of people we can host and 100X decrease in how many resources each one is using.