Apache Webserver Surpasses 50 Million Website Mark
chris81 writes "For the first time ever, the Apache Web Server is powering more than 50 million websites, according to Netcraft's Web Server Survey for October. Although relative share fell by 0.67 percent, the total number of sites powered by Apache grew to over 52 million. Microsoft's IIS finished second with more than 15 million sites served."
Not just that so many people and companies host websites on Apache, I'm more impressed that there are so many websites?
Such an enormous collection of data, it boggles my mind.
This is the sig that says NI (again)
I'm not entirely sure I understand what it means, but July 2001 and June 2004 show an almost mirror image in terms of the blue and red lines (Apache and MS.) When one goes up, the other goes down and vice-versa. Strange. I wonder what exactly was happening during that time period to cause that.
.NET and you didn't really have a choice.
Several big hosting providers were trying to switch their hosting between Apache and IIS. Providers that are big enough to actually make those kinds of dents in the graph. As you can see from the final result, most of them figured out Apache was the better solution. I wouldn't use IIS to serve HTML either, only if the content required
Kjella
Live today, because you never know what tomorrow brings
It is most likely because of PHP and a fair collection of PHP Blogging scripts which are available. I mean just look at the sheer number of blogs at the moment and it isn't hard to understand just how many new sites there are now. Must be a dot blog boom (I doubt it will be too long before we see the .blog TLD)
I really can't see this as anything that'll come as a surprise to anyone, nor the fact that apache came first. I also have a feeling that the apache guys see this the same way, as it is nowhere to be found at http://apache.org/foundation/news.html/. but i guess any round number is worth celebrating, after all free as in drunk, is as important as any other freedom ;)
Blah blah sig blah blah blah irony blah blah
I wouldn't use IIS to serve HTML either,
I've dealt with both Apache and IIS professionally and by far--by far!--I have encountered the most issues with IIS, from little annoyances to full-blown meltdowns. I'm not sure how IIS survives in the market place when its competitor is more robust, functions better and is free. Chalk one up to the marketing people at MS, I guess.
--Rick "If it isn't broken, take it apart and find out why."
The big movers are the domain registrars; they'll host several hundred parked domains on a single server. While they're all using the same content (probably the same files, even), they'll show up as hundreds of sites. If they move from Apache to IIS (or vice versa), several hundred (or thousand?) websites appear to switch.
What would be really interesting would be a figure of total pages served (over the entire internet), grouped by server type. Or the average return opn investement, per server type. Number of hostnames really says nothing, I can add a few thousand myself with no trouble at all.
Don't want to be a troll, but what are the latest innovations Apache introduced lately to stay on top? I think we don't talk often enough about this software here on Slashdot. No, I'm not new here...
Qualitywise, MS SQL Server is the IIS of the database world. Only if you somehow got locked into .NET or some other proprietary hook into MS would you need MS SQL over an industry standard like Postgresql or MySQL which are in approximately the same niche. Those two are even starting to nibble at the heels of Oracle in some contexts, unlike MS SQL.
MS has tried give aways before with IIS. People learn their lesson and move on, unless they get locked in. The same goes with SQL databases.
So a purchase price of zero is an advantage, but the main reason people use Apache and the other parts of LAMP is the quality. The price is just gravy.
Beta is broken and the link to classic doesn't work. Stop wasting our time or there won't be anybody left here.
They just say they "received responses from 74,409,971 sites" while not defining what a site actually is.
Netcraft is very clear about this.
One server running 10,000 virtual hosts is 10,000 "sites".
This is why historically thttpd did very well in Netcraft surveys -- it was good at hosting thousands of sites from one server (and allowed throttling of over-used sites).
One word: ASP.
Many corporate sites start of as a set of static pages with a "Contact us" web form. ASP is typically used for that as it requires only minimal programming effort.
Later on, when more dynamic content is added, they will often stick with IIS since they already know it.
WWTTD?
If your IT department is afraid of editing text files (I assume that was supposed to mean "edit", right?), then you have a bigger problem than being dependant on Microsoft, anyway.
quidquid latine dictum sit altum videtur.