Backend uses in Chrome Headless

[uasan]

Hi.
There is also a very promising use case - this is Chrome Headless on the backend.
IBM browser functions

[phoglenix]

@ericwilligers should we add this to the potential use-cases in the explainer?

[ewilligers]

If sockets were part of a test automation API, that would suffice for backend uses.

Thus I suspect this use case is more an example of a happy passenger than a motivating reason to add sockets to the web platform (the purpose of use cases in explainers).

[uasan]

IBM browser functions - this is not for test automation, this is runtime for server side render and serverless solution, there client sockets are needed for connection to databases (Redis, Postgres, etc...)

P.S.
In 2010, Ryan Dahl developed Node.js, because then there was no Chrome Headless with socket support and others I/O in userland, the presence of sockets in Chrome will allow to use the same runtime on the client and on the server.