Apache drops below 50 percent web server market share, nginx claims over 33 percent

[Rohit Kumar]

The latest data from w3techs shows Apache market share is declining. Nginx sees enormous gains and now is the web server of choice for the top 100k sites

The post Apache drops below 50 percent web server market share, nginx claims over 33 percent appeared first on ServeTheHome.

Continue reading...

 

[T_Minus]

Wow interesting!

I need to give nginx another look, apache is just there and easy... lol

 

[Jaket]

I've been using Nginx for the past two years on our companies sites and it's been much better than when we had apache running. Interesting to see this

 

[cheezehead]

Not surprised, it works for almost all use cases Apache does while scaling better and needing less resources. Apache's biggest strength is it's module architecture which does provide some application-specific needed functionality.

 

[eva2000]

Been using Nginx via my Centmin Mod Project for past 6+ yrs with 3,000+ new installs per month by users. Doing my part to get Nginx usage up

 

[mstone]

In my mind apache suffered from the same kind of stumbled transition as python. Back in the pre-2.0 days it seemed like apache had a mindshare that it never really recovered. Moving to 2.0 caused all sorts of headaches, so a lot of people stayed on 1.3 for a long time, others looked at alternatives, and the project just seemed to become less focused. HTTP/2 is the latest example: once upon a time apache would have been pushing the envelope for that sort of feature, now it's just been playing catch up. Put another way, it's a project that's reached the point of valuing stability more than innovation, so people looking for innovation have just gone elsewhere.

 

[eva2000]

It's also about server resource usage and scalability. If Nginx can replace a 6x apache web server cluster with 2-3x Nginx web servers and still handle 2x times more traffic, then folks' eyes are forced wide open to the benefits of Nginx

 

[BackupProphet]

I use Nginx and Apache a lot. The biggest difference between those two are the configuration format, performance wise they are both pretty much equal, in almost every case you will run out of network bandwidth before one of them gets cpu bound.

 

[fractal]

Do most people run nginx with php or do they run nginx as a proxy to instances of apache/php?

I am seriously considering putting nginx as a front end for all my piffly little web sites and run them on as many VMs as makes sense on as many hosts as makes sense behind nginx as a proxy.

I guess I don't know enough about nginx to know whether it makes sense to run something like wordpress directly under nginx or whether it is better to use nginx as the proxy so you can change the underling configuration without anyone knowing, which is how I was thinking of using it.

 

[Jaket]

We have a few blogs and everything running wordpress using nginx on different VPS's.

 

[cheezehead]

Do most people run nginx with php or do they run nginx as a proxy to instances of apache/php?

I am seriously considering putting nginx as a front end for all my piffly little web sites and run them on as many VMs as makes sense on as many hosts as makes sense behind nginx as a proxy.

I guess I don't know enough about nginx to know whether it makes sense to run something like wordpress directly under nginx or whether it is better to use nginx as the proxy so you can change the underling configuration without anyone knowing, which is how I was thinking of using it.

It can do both. Depending on scaling, you could run nginx with carp/haproxy in front and then direct certain "static" content to nginx boxes in the backend and then the rest to the apache/tomcat installs.