3 ms·

Apache might very well be under pressure from NGINX, but getting out a new major release (and after so many years), is DEFINITELY NOT a sing of this. Much less

by batista 15y ago

Apache might very well be under pressure from NGINX, but getting out a new major release (and after so many years), is DEFINITELY NOT a sing of this. Much less is a new release indicator that Zdnet will be "eating their words in a year or two" regarding Ngix/Apache market share. On the contrary, if this release DOES improve performance a lot and reduces memory usage, on top of all the other savings, it would make it even LESS possible for NGINX to win over Apache. Besides raw performance, there are lots of reasons to use Apache still, from the fact that it's a battle tested server with tons of documentation, know best practices, tools and modules support, knowledgable admins etc available for it. So, if performance is improved, many people won't bother switched that otherwise might have.

lbotos 15y ago
A counter to this is all the people that have switched to NGINX are not going to "jump ship" back to Apache. I'm one of those converts and while this may be great for people who NEED Apache, most people don't need it and may have already made the switch to NGINX.
- absconditus 15y ago
  Except that most people did not make the switch. Apache continues to hover around 65% of the market while its next nearest competitor, Microsoft, hovers around 15%. nginx is below 10% and climbing very slowly. http://news.netcraft.com/archives/2012/02/07/february-2012-web-server-survey.html http://news.netcraft.com/archives/2012/02/07/february-2012-w...
- 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.

by batista 15y ago

lbotos 15y ago

A counter to this is all the people that have switched to NGINX are not going to "jump ship" back to Apache. I'm one of those converts and while this may be great for people who NEED Apache, most people don't need it and may have already made the switch to NGINX.

absconditus 15y ago
Except that most people did not make the switch. Apache continues to hover around 65% of the market while its next nearest competitor, Microsoft, hovers around 15%. nginx is below 10% and climbing very slowly. http://news.netcraft.com/archives/2012/02/07/february-2012-web-server-survey.html http://news.netcraft.com/archives/2012/02/07/february-2012-w...
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.