Skip to content

Why HNSCs in a Single Web Application? and Best Practices in SharePoint 2013..

February 1, 2015

The new recommendations and path suggested by the MS is to go with single web application and multiple Host Named Site Collections (HNSCs) instead of multiple web applications as we use to do in the previous version of SharePoint.

For Software Boundaries and Limits click here.

You can still go with the additional web application if functionality is needed that can not be achieved in the web app shared by all the HNSCs e.g. different authentication requirement SAML or FBA.

I have spent lot of time building this new site architecture and during my research I put together some notes (with links) from different articles written by MVPs and other famous authors/TechNet.

I used this during the implementation and share and show the importance of this new architecture and how to implement e.g. no manual IIS bindings and other best practices.  I thought I will share this online as well for quick reference for others too.

If you have been playing with this new model and want to show your client the importance of this new structure you can use these points mentioned below and feel free to add any additional in the comment section.

  1. From TechNet “The recommended configuration for deploying sites is using host-named site collections with all sites located within a single web application, as illustrated in the following diagram.”
    http://technet.microsoft.com/en-us/library/cc424952.aspx#section1a

    • From the same TechNet link mentioned above “We recommend host-named site collections  unless requirements dictate that path-based sites with alternate access mapping are necessary”
    • From the link mentioned above “You can use host-named and path based site collections in the same web application. To ensure that both types of site collections are accessible to users, do not put host header bindings on the IIS website of your web application”
  2. Corporate Portal with Host named site collection http://www.microsoft.com/en-us/download/details.aspx?id=30362
  3. Why only One Web App is recommended : “ The problem is that even the base binaries needed to load a Site into memory (e.g. using separate web apps) has a high performance impact — and given that people generally want vanity URLs, which meant separate Web Apps in the past, HNSC is a great alternative.” http://social.technet.microsoft.com/Forums/sharepoint/en-US/231859ae-2656-4328-971e-ebf37639a827/host-named-site-collection-hnsc?forum=sharepointadminprevious
  4. As per MVP , Paul Stork “Yes you can add a host header in the IIS binding after the fact, but it’s not a supported design from Microsoft’s point of view and I really wouldn’t recommend it.”” link : http://social.technet.microsoft.com/Forums/en-US/eb95884c-0ebc-4743-9643-22387d164406/single-web-app-w-host-named-site-collections-or-multiple-web-apps-w-host-headings?forum=sharepointadmin
  5. Brenda (MSFT) talks about a Single Web Application “New features and existing features are optimized to work with host-named site collections like never before. However, it’s not just the feature that is important. It’s how it is configured — all host-named site collections are deployed to a single web application. The App model and Request Management, for example, are optimized for this configuration.” http://blogs.technet.com/b/tothesharepoint/archive/2013/05/17/your-friendly-guide-to-host-named-site-collections-with-timo-heidschuster-sharepoint-solution-architect.aspx
  6. Maximum number of web application is 20 but as per the same TechNet article “We recommended limiting the number of web applications as much as possible. Create additional host named site collections where possible instead of adding web applications.” http://technet.microsoft.com/en-us/library/cc262787(v=office.15).aspx#WebApplication
  7. As per Trevor, MVP “You should try to limit the number of Web Applications (preferably 1). You can mix HNSC and Path-Based site collections within the same Web Application.” http://social.technet.microsoft.com/Forums/sharepoint/en-US/53dc9179-9eb9-4bad-bbaf-57babca28b82/confusion-around-host-named-site-collections-host-header-web-application-and-mysite-host?forum=sharepointadmin
  8. Logical Architecture Guidance for SharePoint by Steve Peschka. Benefits of one Web Application http://blogs.technet.com/b/speschka/archive/2013/06/26/logical-architecture-guidance-for-sharepoint-2013-part-1.aspx
  9. MVP, Trevor says regarding single Web App and single AppPool “The Microsoft model provides far better scalability than individual Web Applications would. Each Web Application (or Application Pool) has a significant amount of overhead, just in the base binaries alone. This is why Microsoft is encouraging towards a single Web Application + single Application Pool + host-based site collection model” http://social.technet.microsoft.com/Forums/sharepoint/en-US/c2de887a-25dd-4554-9181-f4ab1093d8d1/best-practices-for-web-applications-and-app-pools-in-2013?forum=sharepointgeneral
  10. Removing IIS binding manually by Russ Maxwell “When you create a web application and specify a host header URL, you stamp the host header URL on the spwebapplication object which is stored in the objects table in the configuration database. When you try to change the host header URL by updating the Alternate Access Mapping and manually update the bindings in IIS, the SPWebApplication object is never updated so it continues to maintain knowledge of the original host header URL and not the new one. When you start the Microsoft SharePoint Foundation Web Application service in Central Admin, the information from the associated SPWebApplication object in the configuration database is used when instantiating IIS Sites. This is why the original host header URL shows up.” http://blogs.msdn.com/b/russmax/archive/2013/02/27/how-to-properly-change-the-host-header-url-of-a-web-application-in-sharepoint-2010.aspx
    Also see this where MS recommend to remove IIS binding manually.
  11. Last but my favorite ,One of the best article written by Trevor Seward to show comparison of resources usage when use multiple web applications vs single web application with multiple HNSCs. http://thesharepointfarm.com/2014/08/expense-application-pools/

Feel free to add any comments or share your thoughts …

Advertisements
Leave a Comment

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: