4 ms·
It’s kind of hard to explain what a big deal NGINX/fastcgi was back in the day coming from httpd/mod_php. All of the sudden, a basic EC2 instance could handle o
by ramesh31 4y ago
It’s kind of hard to explain what a big deal NGINX/fastcgi was back in the day coming from httpd/mod_php. All of the sudden, a basic EC2 instance could handle orders of magnitude more concurrent requests. Before NodeJS was a thing, it opened up whole new possibilities for my company at the time.
Not sure what my point is. But NGNIX has a special place in my developer heart and it’s really encouraging to hear this.
- ggm 4y agoI am probably in the dying cohort who were mod_python, didn't make uplift to fastcgi and are somewhat mentally stuck in expectation of apache hooks and thin paralellism in our code. The fastcgi thing was true: I don't for a minute deny what you are saying. But it also stranded some "less agile" minds like me. I know significant sites using Perl use::CGI; still.
- thriftwy 4y agoBefore nginx there was mod_accel for Apache which was hard to configure but provided same ballpark of performance reverse proxying. Earlier work of the same artist.
- jwmoz 4y agoI came from the same place, you're right, it felt like this super new hacker fast thing.
- xorcist 4y agoThe big deal was FPM, the PHP FastCGI process manager. Apache had mod_fastcgi for half a decade before nginx even existed, and then got mod_fcgi, but it was not much good without any support from PHP (which was an even bigger deal back then).
- BirAdam 4y agoYou can use Apache with FPM. However, Nginx was definitely what I chose to use. I was working in managed webhosting at the time, and it was just amazing how much could be done in Nginx without needing to track down some abandoned module like had to be done with Apache all the time.