Re:Migrating from Netlify to Cloudflare Workers Sites for 2x...
by afiori on Friday February 11, 2022 @11:42AM
(#30303532)
I believe I made a mistake, my previous comments are about CGI not FastCGI.
Also I am not an expert so I will not be able to prove anything, but I can try my best to express my opinions.
I do not think that node has any problems with FastCGI
So basically Node's start latency are too slow for CGI and FastCGI is bad for a worker platforms (or for any multitenant offering).
The reason is that cloudflare doesn't want to keep track which workers are for which customers and want to offer a clean slate environment for each request.
This either means spinning up new processes or using some other in-process isolation techniques. All javascript workers platforms I know use V8 isolates, which (I believe) node does not offer.
PS: I made also another mistake, it looks like deno offers a worker platform on V8 isolates. https://deno.com/deploy
Also I am not an expert so I will not be able to prove anything, but I can try my best to express my opinions.
I do not think that node has any problems with FastCGI
So basically Node's start latency are too slow for CGI and FastCGI is bad for a worker platforms (or for any multitenant offering).
The reason is that cloudflare doesn't want to keep track which workers are for which customers and want to offer a clean slate environment for each request.
This either means spinning up new processes or using some other in-process isolation techniques. All javascript workers platforms I know use V8 isolates, which (I believe) node does not offer.
PS: I made also another mistake, it looks like deno offers a worker platform on V8 isolates. https://deno.com/deploy