Wouldn't it be very memory inefficient? A browser "tab" isn't exactly a small amount of resource. And I remember there were quite a few problems with headless browser not being perfect ( Although I think that was quite a while ago so things might have improved )
However I do love the idea of Browser Function! It has been a long time since I have been excited with any Web Development tech. So I just need some time to sink in my excitement.
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.
This sounds similar to how Cloudflare Workers work - using the V8 isolate technology built for Chrome to provide secure isolation of backend processes without the overhead of VMs or even containers.
ksec|6 years ago
However I do love the idea of Browser Function! It has been a long time since I have been excited with any Web Development tech. So I just need some time to sink in my excitement.
richardyoung00|6 years ago
Sonata|6 years ago
jgrahamc|6 years ago
https://workers.cloudflare.com/
Plus we have a distributed KV store to go with the code execution environment.
reticulation|6 years ago