Wednesday, February 13, 2013

Application Pool

Posted by Rahul Kharde at 2:15 AM

An Application Pool can contain one or more applications and allows us to configure a level of isolation between different Web applications. For example, if you want to isolate all the Web applications running in the same computer, you can do this by creating a separate application pool for every Web application and placing them in their corresponding application pool. Because each application pool runs in its own worker process, errors in one application pool will not affect the applications running in other application pools. Deploying applications in application pools is a primary advantage of running IIS 6.0 in worker process isolation mode because you can customize the application pools to achieve the degree of application isolation that you need.
  • Application pools are used to separate set of IIS worker processes that share the same configuration.
  • Application pools enable us to isolate our web application for better security, reliability, and availability
  • AppPools can run as different identities, so you can restrict permissions this way.
  • You can recycle/restart one app pool without affecting the sites that are running in different app pools.
  • Application pools allow you to isolate your applications from one another
  • If they are running on the same server. This way, if there is an error in one app, it won't take down other applications.
  • Applications pools allow you to separate different apps which require different levels of security.
  • You can assign a different identity to each app pool so that when you run task manager, you know which w3wp.exe is which.
  • If you have a website that has a memory leak or generally misbehaves, you can place it in an app pool so it doesn't affect the other web sites
  • If you have a website that is very CPU-intensive (like resizing photos, for instance), you can place it in its own app pool and throttle its CPU utilization
  • If you have multiple websites that each has their own SQL database, you can use active directory authentication instead of storing usernames/passwords in web.config.

If you enjoyed this post and wish to be informed whenever a new post is published, then make sure you subscribe to my regular Email Updates. Subscribe Now!

Kindly Bookmark and Share it:



Have any question? Feel Free To Post Below:


Popular Posts

Recent Comments

© 2011. All Rights Reserved | Help to understand .Net | Template by Blogger Widgets

Home | About | Top