SharePoint Server Topology Patterns

using(NaT) has a great writeup on different SharePoint server topology patterns.

Instead of the typical MS documentation saying vague things like “think about your indexing needs” without clear indications of what we should be considering about indexing, NaT has identified common server configurations patterns. Many of us have stumbled into the same basic topologies, or read best-practices guides on “separate your WFEs from your database”, but by presenting them as patterns with the strengths and weaknesses of each pattern identified it becomes a simple guide to picking the right topology for a given need.

App-X6 Pattern

The Web-X6 pattern can perhaps fit for a farm where WFEs do a lot of user authentication for collaboration reasons (authentication could be expensive, so therefore an additional WFE would definitely help). On the other hand, The Application-X6 pattern targets the query role. If you are expecting a lot of search queries, then it might be a better idea to have a dedicated query server than having a 3rd WFE, for that reason you add a 2nd application server and that can primarily be used for query but you can also use it to host a second CA or separate the CA from the index server (btw if you are having the CA with Query server you can perhaps stop IIS, and start it back whenever you need it, that way you don’t have to worry about having using up the memory), and you can also use the same box to load balance the Excel Role if Excel services availability is very important.


While he does point out that it’s focused on MOSS 2007, the basic principles of the patterns carry over to 2010 fairly well. I’d love to hear about differences between 2007 and 2010 for these though.

I was happy to see that my current production farm does not fall into an anti-pattern model.



About this entry