Migrating from Apache to IIS 1

[jeanpierre]

Is it a steep learning curve to migrate from Apache to IIS?

 

[RhythmAce]

Yes, it looks like this:

apache----
|
|
|
|
IIS <--------

You are going from one that makes up more then the rest of the servers in the world combined, to one that has more bugs and security leaks than any other in existance.

 

[ifincham]

Hi,

As RhythmAce says, its definitely steep - A steep drop. If you really want to do that while everyone else is doing the reverse then, assuming you understand apache, you wouldn't have any problem at all understanding IIS - its all M$ certified button pusher stuff.

Read this and repent -->

http://www.idg.net/go.cgi?id=560416

Regards

 

[rycamor]

hehe... c'mon people, give the guy a break. He probably has to do this to save his job. I have spent time on both servers, since I develop freelance PHP applications, and I often have to work with the client's webserver. I always prefer Apache, but I gotta eat ;-).

I will say the migration path does have some difficulties. Even though IIS is a &quot;button-pusher&quot; setup, there are many assumptions you make after getting comfortable with Apache, which you can't make with Windows.

Many of these problems have to do with the Windows architecture, and network approach. I have spent days, sometimes, tracking down problems with authentication from the webserver, through the proxy to another application server, or troubleshooting ODBC connections to SQL server on another machine, etc... You would think these things are easy to solve, since they just involve button pushing, but the truth is, you still have to know what you are doing, and it will involve reading manuals.

Also, IIS just doesn't have the wealth of configuration options that Apache has. If you enjoy such Apache niceties as mod_rewrite, or the fine-grained control you get with .htaccess files, or the ability to work directly with HTTP headers, etc... you will be very frustrated with IIS.

In the end, my conclusion is that I can get things done much faster on a Unix/Apache system, because its much quicker to edit text and restart daemons that it is to navigate through menu after menu of graphical choices,m and waiting for the system to reboot.

But if you have to use IIS, take some time to read about things before you try to make configuration changes, or you will find yourself spending a few long weekends. -------------------

Current reading --

http://www.wnd.com/news/article.asp?ARTICLE_ID=25456