On Monday, 9 May 2022 at 20:37:50 UTC, Andrea Fontana wrote:
The same goes for cgi/fastcgi/scgi and so on.
Well, cgi does one process per request, so there is no worker pool (it is the original "serverless" lol).
fastcgi is interesting because the Apache module for it will actually start and stop worker processes as-needed. I don't think the the nginx impl does that though.
But the nicest thing about all these application models is if you write it in the right way, you can swap out the approach, either transparently adding the i/o event waits or just adding additional servers without touching the application code. That's a lot harder to do when you expect shared state etc. like other things encourage.
