←back to thread

Remember FastCGI? (2021)

(brokenco.de)
53 points heavensteeth | 1 comments | 08 Apr 25 12:00 UTC | HN request time: 0s | source
Show context
ryao ◴[11 Apr 25 09:33 UTC] No.43652062[source]▶

  If you find yourself with a scripted language where processing HTTP requests might be too slow or unsafe, I can still see some utility for FastCGI. For most of the rest of us, HTTP won, just write little HTTP webservers.
Without serious development effort, I would expect using an existing web server with FastCGI is faster than writing your own web server. It is also more secure as the FastCGI application can be run as a different user in a chroot, or a namespace based sandbox like a docker container.
replies(4): >>43652278 #>>43652341 #>>43654110 #>>43671603 #
assimpleaspossi ◴[11 Apr 25 14:21 UTC] No.43654110[source]▶
This is exactly why my web dev company used FastCGI for all our development and would still today if I didn't retire it just two years ago.

Wherever we needed faster interaction, FastCGI did the job and allowed us to interface with anything in the backend including our C programs.

replies(1): >>43656823 #
ryao ◴[11 Apr 25 18:25 UTC] No.43656823[source]▶
Why did you retire it?
replies(1): >>43659851 #
1. assimpleaspossi ◴[11 Apr 25 23:33 UTC] No.43659851[source]▶
My biggest customer was a national restaurant chain that thought they should have it all in house. So far, a big mistake.

My second biggest customer went out of business. Which left us with a bunch of itty-bitty businesses that I'm just too tired to be chasing after.