Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

The Internet Apache

Apache Web Server Share Falls Below 50 Percent For First Time Since 2009 303

Posted by Unknown Lamer
from the netcraft-confirms-netcraft-meme-is-dying dept.
darthcamaro writes "Apache has always dominated the web server landscape. But in August, its share has slipped below 50 percent for the first time in years. The winner isn't nginx either — it's Microsoft IIS that has picked up share. But don't worry, this isn't likely a repeat of the Netscape/IE battle of the late 90's, Apache is here to stay (right?)" The dip is mostly the result of GoDaddy switching to IIS from Apache. Which is to say GoDaddy hosts a whole lot of sites.
This discussion has been archived. No new comments can be posted.

Apache Web Server Share Falls Below 50 Percent For First Time Since 2009

Comments Filter:
  • Hmm (Score:4, Interesting)

    by Tailhook (98486) on Monday August 12, 2013 @06:53PM (#44547617)

    The statistical effect of millions of empty, neglected GoDaddy hosted sites will not ultimately mean a great deal. It does raise a question for me, however; what benefit does GoDaddy hope to realize with IIS? My last contact with IIS was about 9 years ago. At that time it was fragile, insecure and plagued with mysterious "metabase" corruption problems. The thought of using such a thing for large scale hosting seems absurd and I've ignored it ever since.

    Has it since improved enough to entice really large operations?

  • Re:GoDaddy IIS (Score:2, Interesting)

    by LoRdTAW (99712) on Monday August 12, 2013 @07:16PM (#44547811)

    Simple: asp.net. Plenty of half assed coders out there can, with little effort, build a website using Visual Basic or C#.

  • Re:Hmm (Score:5, Interesting)

    by DuckDodgers (541817) <keeper_of_the_wolf.yahoo@com> on Monday August 12, 2013 @07:57PM (#44548125)
    Linux isn't harder to administer because of any inherent problems, it's harder for the average person to administer because we probably had Windows in the home computer and at the office, and at the school. Making the jump from Windows 95 to Windows NT or from Windows Vista to Server 2008 is a lot easier than jumping from Windows to Linux.

    If you're a serious power-user administrator, Linux and Unixes in general has been easier to administer than Windows Server for a very long time. You have more interoperable shell tools at your disposal. The Server GUI is better for an admin novice, but terminal tools are quicker for a power user than toggling through programs and hunting through menus. Microsoft is catching up with PowerShell, but even if the technology is extremely flexible and mature (and it may well be), they took the odd step of inventing a new syntax different enough to be confusing to people comfortable with bash or cmd.exe - me among them. Now I'm asking myself whether making the investment in Powershell is worthwhile. It probably is, but I don't look forward to it.
  • by raymorris (2726007) on Monday August 12, 2013 @08:44PM (#44548463)
    A while back Microsoft was paying hosts and registrars with large numbers of domains parked, or $30 / year type, to switch over.
    I don't know if that program is still active.
  • by the_B0fh (208483) on Monday August 12, 2013 @08:46PM (#44548471) Homepage

    why is it that everytime I read about a dip in apache stats, it's because of godaddy switching over? Bloody hell, they've been switching over for years, just how many effing sites do they have?

  • Re:Hmm (Score:4, Interesting)

    by smash (1351) on Monday August 12, 2013 @09:00PM (#44548549) Homepage Journal
    +1. Powershell is quirky. It is prettty excruciatingly slow. There are bugs. But it really is pretty neat, and nothing similar exists in the Unix world as yet. If you need to admin Windows boxes, you'd definitely be well advised to learn powershell.
  • Re:Hmm (Score:5, Interesting)

    by DaveAtFraud (460127) on Monday August 12, 2013 @09:26PM (#44548695) Homepage Journal

    You basically just admitted that Linux boxes are harder to administer than Windows servers. This makes Linux servers much less appealing for companies when you can find Windows server admins for a dime a dozen, but Linux admins are harder to find and generally cost a lot more.

    Er, no. Windows makes the easy things easy (pick what you want from the list rather than, horror of horrors, type something) but still hasn't succeeded in making the difficult easy. This lulls people who think they know what they're doing into jumping into the deep end and finding out they can't swim. Lots of things when setting up a server (web or otherwise) that require an understanding of the underlying networking. The Windows admins who don't know this are the ones who are "a dime a dozen." The ones that do can create a secure, functional site with Windows but wish they had Linux since it's easier and more secure and faster and more flexible and....


  • Re:Hmm (Score:4, Interesting)

    by MightyMartian (840721) on Monday August 12, 2013 @09:28PM (#44548709) Journal

    My experience with Powershell is sufficient to state that Windows users can keep it. Bash is a far far more mature shell with a helluva more lineage and experience behind it.

  • Re:1st post. (Score:3, Interesting)

    by micheas (231635) on Monday August 12, 2013 @10:19PM (#44548949) Homepage Journal

    It was mostly due to microsoft cutting a check to godaddy to not show apache traffic server in the headers.

    Godaddy runs IIS on linux. Well, they run IIS behind apache traffic server so which webserver to count as the webserver is a bit of an academic question. The moral here is that godaddy hosts a lot (hundreds of thousands, if not millions) of inactive sites that they collect 9.95 or so a year for hosting.

  • Re:1st post. (Score:5, Interesting)

    by Zenin (266666) on Tuesday August 13, 2013 @03:14AM (#44550299) Homepage

    You can backup IIS's config just the same. It's just an XML file (and a surprisingly easy to read/understand one at that).

    You can also do your config by editing it as well, although typically you'll use something like AppCmd or more modernly PowerShell.

    It's frankly easier to reliably automate/script IIS configuration changes than Apache. Apache's configuration system is incredibly powerful and at times that's needed, but that power also means it's effectively impossible for a random admin script to make sense of it enough to modify. Such a tool must intrinsically know not just Apache's config system...but your specific implementation with it. AppCmd and PowerShell can pretty reliably walk into nearly any IIS setup, no matter how convoluted, and safely make additions, tweaks, etc.

    Frankly I'm first and foremost an Apache fan, have been since it was literally A Patchy Server. And I still deploy it more often than not, often in front of IIS to get some clever hack done that just isn't practical in IIS.

    But that said...I'm warming up to IIS, especially as C#/.Net gains major traction in the wake of Oracle's kiss of death to Java.

  • by gbjbaanb (229885) on Tuesday August 13, 2013 @04:01AM (#44550455)

    IIRC, GoDaddy switched to IIS for these parked domains and a dip in Apache usage appeared, then reversed itself a year or so later... now its repeating.

    Seems more like a money-making initiative fromGoDaddy, or a money-losing initiative from MS yet again. What's the chances history will repeat itself once the contract runs out...

  • by kervin (64171) on Tuesday August 13, 2013 @07:54AM (#44551493) Homepage

    Prefork plus increased file descriptors? You're kidding right? While you can get Apache to match NGinx, it's definitely nowhere that simple. As optimized as Unix fork() is, processes are going to use more resources than threads in this scenario every time. Prefork is the worse MPM you can use when you need performance. Even the Apache manual spells this out.

    You'd have *begin* with worker or event MPM, use Apache 2.4 at least, and finely tune for your Application and specific load.

    The benefit of NGinx is that you get a highly optimized web server right out of the box. You don't have to mess with the configs and you're almost there.

    Technically the Apache team can do the same if they get rid of Prefork and a whole bunch of decades old legacy configuration options. Remove code processing modules from the webserver application space, i.e. get rid of mod_php for php_fpm, etc. All this can be configured now and you'll get that speed and stability, but it's just not done out of the box.

    With NGinx it is. The only way to do things is the 'fast' or optimized way.

  • by IwantToKeepAnon (411424) on Tuesday August 13, 2013 @08:29AM (#44551801) Homepage

    The Netcraft graphs show "Google" as a platform, last I read (a couple years ago granted) that google ran a customized version of apache. Does google now offer a honest-to-goodness webserver of its own? Or can googles #'s be added into the apache category? And what about Tomcat sites? Are they already included in the apache #'s?

    Thanks for the link.

In case of injury notify your superior immediately. He'll kiss it and make it better.