Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

FCGI is still quite useful. You can use FCGI, Apache, and Go to get quite good performance. FGCI will spin up more Go servers as needed, and the Go servers can process multiple transactions without reloading the program. Probably outperforms node.js.

Basic CGI reloads the worker program for each request, which is secure but slow. FCGI is an orchestration system. Like Kubernetes, but with lower labor costs. If one of the workers crashes, a new one will be started.

You can run stuff like this on US$10/month shared hosting accounts. To scale up, put a load balancer in front and a replicated database on the back.



> FCGI is an orchestration system. Like Kubernetes, but with lower labor costs

It does about 0.00001% of what Kubernetes can do.

Launching processes to handle web requests is pretty basic for any web server.


Why would you do this instead of just proxy directly to a Go server with sufficient GOMAXPROCS?




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: