Chrome seems to handle memory quite well in headless mode at any rate. The memory footprint isn't tiny, but it seems a fair bit smaller than the container based approaches used by other serverless systems.
Isn't this still wrapped in a container. I would assume a commercial deployment would need this isolation - after all chrome allows toggling feature flags, which could bleed across instances if not containerized.
The big benefit to this approach is the availability of WebApis in a Faas environment.
I don't think you need the extra layer of isolation. Browser tabs are isolated pretty well if they are running different sites. Chrome's spectre mitigations will also help to isolate functions from one another https://security.googleblog.com/2018/07/mitigating-spectre-w...
throwGuardian|6 years ago
The big benefit to this approach is the availability of WebApis in a Faas environment.
richardyoung00|6 years ago