Earlier quoted context omitted.
So, literally, Netcraft confirms Apache is dying.
For "dying" being defined as "increases installs but slower than the whole market balloons".
Nginx reaches 33.3% web server market share while Apache falls below 50%
101–110 of 190 posts
Re: Nginx reaches 33.3% web server market share while Apache falls below 50%
#102I (and I know no one) who has reached for Apache over NGINX in a decade.
Re: Nginx reaches 33.3% web server market share while Apache falls below 50%
#103Re: Nginx reaches 33.3% web server market share while Apache falls below 50%
#104This is like (or worst) than comparing orange and apples. Nginx and Apache are completely different.
Re: Nginx reaches 33.3% web server market share while Apache falls below 50%
#105This is your periodical friendly reminder that Igor Sysoev, principal author of nginx, is strongly pro-Putin and anti-Ukraine. You might get a taste of his views at his personal website, http://sysoev.ru (in Russian; use Google translate). So, if such things matter to you, you might consider choosing some other web frontend.
Re: Nginx reaches 33.3% web server market share while Apache falls below 50%
#106This is your periodical friendly reminder that Igor Sysoev, principal author of nginx, is strongly pro-Putin and anti-Ukraine. You might get a taste of his views at his personal website, http://sysoev.ru (in Russian; use Google translate). So, if such things matter to you, you might consider choosing some other web frontend.
Re: Nginx reaches 33.3% web server market share while Apache falls below 50%
#107Earlier quoted context omitted.
nginx is much more simple than full-service servers like Apache. Which is good if you want to do something easy fast (like terminate TLS, proxy, load-balance, simple redirect, simple header munging, etc.). And not good if you want to do something more complex and get into learning how nginx rewrite rules really work (totally not obvious), how if and other predicates really work (multiple articles in docs suggest it's…
A good reason to use nginx (or better HAProxy), is to stop people from writing endless mess of redirect and rewrite rules.
Re: Nginx reaches 33.3% web server market share while Apache falls below 50%
#108nginx is creating a name and market for itself as a reverse proxy, even though there are better solutions for reverse-proxies out there, everything from HAProxy to Apache Traffic Server to even Apache httpd. But this is an important market to have. Why? Because it allows for the perception that the "web runs on nginx" simply because all you see are the nginx web proxies and nothing behind that. So what are the server…
I feel the "marketing" concept is less actual marketing and more feature appeal, but I guess that's similar? Maybe not, though. Features provide actual value, whereas marketing is ... tricksy.
Re: Nginx reaches 33.3% web server market share while Apache falls below 50%
#109Apache has historically been a giant swiss army knife that will do just about everything you could want, from redirect databases to cgi to php interpreters to crazy auth setups. It did all that while still being a reasonably good workhorse for static file serving (when properly turned and using the right worker model, event rather than threaded or process). Nginx seems to have a different model. It does support a num…
nginx is turning into much more than just a load balancer. Projects such as OpenResty (a full CMS built into nginx) and Kong (an API management service), are built right into nginx using Lua. We've done some minor nginx Lua extensions and are looking to offload activities such as JSON validation into the front-end nginx. http://openresty.org/ https://getkong.org
The latter seems tricky. It's validation inside the application a bottleneck?
Re: Nginx reaches 33.3% web server market share while Apache falls below 50%
#110A lot of Apache work load is now behind Nginx or Haproxy, I wouldn't say those numbers are entirely truthful. Consider how Plesk panels nowadays go with Nginx proxy by default, but Apache in the backend; CPanel will probably follow soon and people have already been doing this manually for a while too. Apache is still there, just not in as much plain sight as it used to.
People like to think they are special, and that they've need more speed, so they turn to Nginx, but most of us can easily be served by Apache.