Wednesday, July 24, 2013

Host-named site collections in SharePoint 2013


One of the recommendations in SharePoint 2013 is the usage of Host Named Site Collections (HNSCs) over using multiple web applications when you want to use vanity urls for specific SharePoint sites. Host-named site collections each have a unique DNS host name and therefore its own top-level URL.  SharePoint 2013 allows you to add multiple URLs by using the Set-SPSiteURL Powershell command. An interesting quote around this is found in a new article Host-named site collection architecture and deployment (SharePoint 2013) :

Because the Office 365 environment uses host-named site collections, new features are optimized for these site collections and they are expected to be more reliable. Learn how to plan for and implement host-named site collections, design URLs, and manage URLs.

The same information is found in SharePoint 2013 design samples – corporate portals and extranet sites :

The recommended configuration for deploying sites is using host-named site collections with all sites located within a single web application. This configuration is recommended to deploy sites because it is the same architecture that the Office 365 environment uses. Consequently this is the most heavily tested configuration. New features, including the App model and Request Management, are optimized for this configuration, and it is the most reliable configuration going forward.

Some of the reasons why host-named site collections are also considered to be the better solution because:

  • Create less overhead on web servers, because no additional IIS web site is required
  • Provide more flexibility because you provide alternative access to individual site collections instead of entire web applications. There is a limit of 20 web applications per farm (with 5 predefined zones), but you can create thousands of site collections (each with their own vanity url)
  • Reduced resource consumption since there are less web applications required (ant thus also less application pools)
  • Mitigates cross-site scripting risks

    Other references:

  • 1 comment:

    Abhishek Srivastava said...

    Microsoft made the Host Name Site collections a "recommendation"

    OK. How do large sharepoint deployments move from Site path to Host Name.

    Microsoft recommends that we export the sites out and then import them back as Host Named SCs. then remove the old site collections.

    Obviously if anyone has done site export import then they will know that it is extremely slow process.

    Microsoft has given no tools through which customers can migrate the entire content database to Host Named SC.

    the import export process is almost impossible for large multi-TB farms with many SCs more than 200GB+