3 ms·
Well, I have switched to NGINX for some projects, and am considering the switch back if Apache gets a few things nailed down (this release is a move in the righ
by batista 15y ago
Well, I have switched to NGINX for some projects, and am considering the switch back if Apache gets a few things nailed down (this release is a move in the right direction).
The main reason is: I don't care for that much performance in the raw one standalone server case, and I can always put Varnish on top. But I do care for easy of installation, breadth of documentation, etc, and with Apache you got that in spades. This can be in even very simple things, that I can solve in Nginx in 15 minutes, like, say, Wordpress having specific rewrite rules and support for Apache built-in and not for Nginx. It's trivial to solve, but if I used Apache, I wouldn't even have to.
Given two platforms, one of which is better than the other but less popular, I usually stick to the most popular one (within reason. Like, I won't go for PHP, but I would go with Rails, not Padrino or some even less known thing).
Fewer problems down the road, and if you get into those, people have already encountered them.