Although these guys have been around since WSS 3.0, host-named site collections haven’t received a great deal of attention up until the last year or so. Continue reading
|05/11/2012 update: since writing this, the official SP2013 software boundaries article has been updated to include a supported limit of up to 20 Web Applications per SharePoint 2013 farm. This is in line with what I have heard from various SharePoint MCMs.|
Designing a URL structure for a SharePoint farm sounds like a straightforward task. Surely it’s just a case of creating a few Web apps and corresponding DNS entries, right? Continue reading
Today I published a post on SP365 which attempts to explain host-named site collections to the uninitiated in the form of a bitesize video overview.
Host-named site collections are a key part of SharePoint 2010’s multi tenant support and offer a huge amount of scalability. They provide support for multiple root named URLs (vanity URLs) and in many cases are a valid alternative to creating additional Web applications.
If you have any feedback or suggestions, feel free to add a comment.
|11/07/2011 Update:I have had some feedback around this article that made me realise that I inadvertently gave RBS a bit of a bashing. It’s a useful technology that – used in the right scenarios – can significantly improve maintainability and scalability. The main point of the RBS section was to debunk the myth that RBS provides a means of bypassing the [current] data sizing boundaries that Microsoft provide.|
I have seen a number of queries over the past couple of months around Web app and application pool limitations in the context of SharePoint 2010. Whilst most SharePoint administrators are aware of the Microsoft recommended application pool limit documented on Technet (10 per farm), Microsoft don’t appear to publish any “magic numbers” around the suggested Web app limit. Continue reading