News for hackers. Stuff that matters.

A comment on Browser Functions: A serverless platform using Web Browser execution engines.

Re:Browser Functions: A serverless platform using Web Browse... by ksec on Thursday January 16, 2020 @11:02AM (#22065744)
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.

[ Parent | on HN ]
Re:Browser Functions: A serverless platform using Web Browse... by richardyoung00 on Thursday January 16, 2020 @11:28AM (#22066036)
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.
[ Parent | on HN ]
Re:Browser Functions: A serverless platform using Web Browse... by throwGuardian on Thursday January 16, 2020 @11:38AM (#22066135)
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.

[ Parent | on HN ]
Re:Browser Functions: A serverless platform using Web Browse... by richardyoung00 on Friday January 17, 2020 @01:56AM (#22072479)
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...
[ Parent | on HN ]