Saturday, April 26, 2003

Source: On The Mark; 4/26/2003; 4:16:46 PM Web Apps and Web Gardens in IIS 6.0 One area of our company is already pursuing server consolidation. Their approach has been to take four ASP.NET applications and house them together on a single W2K machine. All were built on a common framework and all belong to the same business group. However, the design showed a flaw when one application "misbehaved" (waiting on a long-running DB2 transaction) resulting in no ASP.NET activity for three minutes after which the ASP.NET worker process was recycled - effectively taking down all four applications. Windows 2000 and IIS 5.0 just don't provide the kind of application isolation necessary for this approach to work. Windows Server 2003, on the other hand, sports a completely rearchitected IIS 6.0. A key feature of the new architecture is that a web application can be placed in an application pool. Each application pool receives its own worker process. Similarly, multiple processes can be dedicated to a Web Garden - a single machine version of a web farm. Misbehaving applications are a fact of life. We need to address those problems as they are uncovered, but we must also avoid putting one app at risk because of another that misbehaves. IIS 6.0 seems to provide a solid solution. [On The Mark] 4:25:46 PM    trackback []     Articulate []