Advantages of IIS over Apache

[Tread42]

What are some advantages of using the IIS setup over an open source server like Apache and utilizing PHP? Our org. seems content on using Apache/PHP but most vendors seem to get a rise out of the open source platform. So I was wondering if someone could tell me the pros/cons of each?

Thanks
Regards,
Tread42

 

[Junior1544]

well, first... befor i say any thing, i am biosed to microsoft... for personal reasons...

i use microsoft because it's much more user/admin friendly... every thing is done via a gui, and it's easy to start and stop any thing... apachee, every thing is done in code, and ini files, and the dreded conf file... apachee is so confusing to me, it's un real... but now for the pro's of apachee... as the administrator, if your running apachee and are good at it, you got a job for life... learning apachee is very hard for the simple minded(like me) and even better. it's free. and now, they give you even more options because they are running microsoft vertions, so you don't have to run linux or unix to run apachee...

hope my limited knoldge has helped you.

--Junior JHauge@jmjpc.net
Life is change. To deny change is to deny life.

 

[ChrisRAnthony]

As a dedicated MS user (MCSE NT, MCSE 2000) I am strongly in favour of running IIS. However I have become rapidly disillusioned with IIS due to the large number of security patches and upgrades that have to be applied to keep the version secure. We have now started to install Apache on NT as an alternative. I agree with Junior, that Apache is all command line and file driven, and thus is not so intuitive to use, but I will have to start learning to love it!!

 

[Guest_imported]

IIS vs. Apache

I currently run a full 2000/.NET network with IIS5/6. It works for me no problems and I will most likely continue to run like this for a whiel. I am experimenting with FreeBSD (I like the little daemon).

To answer your question:

IIS is alot more user friendly and has greater integration with various snapins, etc... Thanks to Mr. Microsoft everything works together nicely.

Apache is less user friendly but a LOT more stable. I have had more issues with my IIS boxes than I have had with my Apache Box. By Issues I mean: Various services stopping out of the blue, IIS_USR accounts not working properly, etc.


My Advice is that if you want a web server, and you have a little time to play around. Apache on a BSD Box is the way to go. THIS IS ONLY IF YOU WANT A WEB SERVER. If you want a lot more stuff to occure, are under time constraings, or plain and simple just like microsoft. IIS is the solution.

Here is a brief summary of both:

IIS:
-> WINDOWS INTEGRATION. everything fits very nicely.
-> SECURITY ISSUES. You must stay on top of patches!
-> FLEXIBILITY. You can do some cool stuff with IIS
-> COSTS $$. Simply, how much $$ do you want to spend
-> GREATER OVERHEAD. Windows based vs. Text based?
-> EASE OF USE. Very easy to use

APACHE:
-> SECURE. Plain + Simple = Secure
-> HARDER TO USE. Not super easy to setup
-> SMALL MEMORY FOOTPRINT. No Gui loading (assumin *nix install)
-> CACHING: Apache caches a LARGE portion of the website (or maybe all) into memory so when a request is made it can pe spit out right away).
-> COST: FREE!@#$
-> PORTABLE: Comes in Win32 Version as well

This isn't definitive, but it is an idea. It's like asking: "Chicken or the Egg"?.

 

[Junior1544]

my answer to that is the chicken, but that's for another forum;-) JHauge@jmjpc.net
Life is change. To deny change is to deny life.