Comment Re:probably on Microsoft's list of next important (Score 4, Interesting) 282
Where I've worked in the past, it seems that the Web Server of choice follows the Application Server of choice.
If management find a great application that cheaper to run, and maybe has a great support contract at a low price, they buy into the idea, and don't really bother about the fact that they have to move the front end web server technology from say IIS to Apache.
I've been in a situation when a brilliant Apache / Java / Broadvision combination, was replaced by an IIS / .Net solution, just because of what seemed "a good deal" at the time.
However in my particular situation, us "Sys Admins" loved apache so much, we decided to leave it in at the front end, to serve media, protect the front end and internal-proxy the IIS data, and then have IIS as the middle layer just doing the .Net integration part and processing data.
So at the end of the day, Netcraft reports apache, but the real grunt of the work is being done by IIS.
Mike
If management find a great application that cheaper to run, and maybe has a great support contract at a low price, they buy into the idea, and don't really bother about the fact that they have to move the front end web server technology from say IIS to Apache.
I've been in a situation when a brilliant Apache / Java / Broadvision combination, was replaced by an IIS /
However in my particular situation, us "Sys Admins" loved apache so much, we decided to leave it in at the front end, to serve media, protect the front end and internal-proxy the IIS data, and then have IIS as the middle layer just doing the
So at the end of the day, Netcraft reports apache, but the real grunt of the work is being done by IIS.
Mike
