It112 SharePoint 2010 Mythbusters
Download as PPTX, PDF1 like1,629 views
This document summarizes a presentation on debunking common myths about SharePoint farm topologies, service applications, authentication, and scalability. Some key points addressed include: - The term "Web Front End" is a hangover from previous versions but the functionality has been decomposed across different services. - Topology models remain appropriate but there are no enforced restrictions. Placement of services like search query servers depends on usage patterns. - Service applications are not hosted on IIS or deployed to application servers but provide scalability through load balancing. - Claims-based authentication does not mean Kerberos is dead and helps address identity delegation issues. - SharePoint can support large deployments with millions of documents and
It112 SharePoint 2010 Mythbusters
- 1. SharePoint 2010MythbustersIT112Spencer HarbarEnterprise Architect harbar.net
- 2. About Spencerwww.harbar.net | spence@harbar.net | @harbarsGeneral SharePoint DogsbodyMicrosoft Certified Master | SharePoint 2007Microsoft Certified Master | SharePoint Instructor & AuthorMost Valuable Professional | SharePoint ServerSharePoint Patterns & Practices Advisory Board Member16 years in Enterprise ITISPA Vice PresidentEnterprise Architect working with Microsoft’s largestcustomers deploying SharePoint Server.Works with SharePoint Product Group on 2010 ReadinessAuthor for MSDN & TechNet
- 3. AgendaDebunking Common SharePoint Farm MisconceptionsTopologyService ApplicationsAuthenticationGlobal DeploymentsAgile FarmsScalabilitySoftware Boundaries
- 5. Farm Topologies (Roles)“Web Front End” (WFE)Terminology hangover from previous version(s)!!SPF Web Application ServiceHere to stay (unfortunately!)Functional Decomposition of:Managed Metadata
- 8. etc
- 10. Search Crawl & Search Query
- 11. Excel Services
- 12. Visio Services
- 13. etcFarm Topologies“No Topology Restrictions”No enforced restrictionsPlenty of real world restrictions, for exampleNumber of “WFE”sNumber of Web ApplicationsTopology Models remain appropriate“Load balancing” of:Search Query ServersExcel Calculation Servicesetc
- 14. Farm Topologies (Search)“Make the Crawl Server a ‘Crawl Front End’”Not always a smart idea!Dedicated Crawl Front Ends are a good ideaIndexer resources can easily become saturated“Always host Search Query on the WFEs”Each WFE == propagated indexesDepends on usage patterns
- 16. Service Applications“...are hosted by the SharePoint Web Services IIS Web Site”“...are deployed on an Application Server”“...are WCF Services”“...provide scalability and load balancing”“...avoid Authentication Delegation configuration”“...make Inter-Farm Services a snap”
- 18. Authentication
- 19. Claims Based Identity“...means Kerberos is dead”“..solves identity delegation problems”“…provides single sign on”
- 20. Authentication“One DC for every four WFEs”Old wives tale, from Exchange!It depends upon your authentication scenarioPlacement of DCs is far more important
- 21. Global Deployments &High Availability
- 22. Global Deployments“SharePoint can’t do geo-distribution”Plenty of optionsConsider carefully why you may need themSharePoint Online“SharePoint doesn’t work over the WAN”A slow WAN link problem is a slow WAN link problem!Not a SharePoint problem
- 23. High Availability“Web Gardens give you better performance”Don’t use them (ever!)BLOB Cache & other managed resources“A single Farm can host 100s of Web Apps”~20 Web Applications per Farm is reasonableSharePoint loves RAMRequest Routing or DNS increases operational service burden considerably
- 24. High Availability“Web Apps can be deployed to specific servers in a Farm”Request Routing or DNS increases operational service burden considerablyThere is nothing wrong with multiple farmsServer Groups is a logical concept not a feature
- 25. Agile Farms
- 26. Your Farm Topology is NOT done!SharePoint Deployments need to be agileYour day one topology...May not be suitable in the futureAdoption patternsFeature implementationUsage patternsPlan for an agile farmAssume your topology will change over lifespanSeriously consider virtualisation
- 27. Agile FarmsConsider future versionsWe aren't done yetOperations ManagementPatching, Reporting etcDon’t get stuck with a single FarmThe “hidden cost” of SharePointAnti-Virus, Backup & Restore, Systems Management, Usage Anaylsis
- 28. Scalability
- 29. “SharePoint can’t scale”average daily load throughput of:~5 million TIFF images~1.9 million Microsoft Office documents.40+ million content items were loaded into SharePoint in only 13 daysAverage content database size of:200.65 GB for Divisional Site Collections137.60 GB for departmental site collections539 GB for the search databaseOver 5TB content storage with capacity for double
- 33. SharePoint “Magic Numbers”“How many XXXX can I have in my SharePoint?”Plan for Software Boundaries (TechNet)technet.microsoft.com/en-us/library/cc262787.aspx (2007)www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=66438e41-5733-448a-bd76-a8052b394fe2 (2010)
- 34. SharePoint “Magic Numbers”There are only guidelines for acceptable performanceSuch guidelines are based upon test scenarios1 thru 1 Database Server1 thru 8 Web ServersTeam Sites (55%), Doc Workspace (20%), Meeting Workspace (10%), Blog (10%), Wiki (5%)Other scenarios coming soonOften refined based on customer deployments
- 35. Logical Architecture "Magic Numbers"
- 36. There are NO magic numbers!Successful Solutions Architecture is basically two things:CompromiseReduction of ComplexityEvaluate solution holistically ensuring adequate compromises.Test and monitor as you build and deploy your solution.Re-design the solution to ensure that you do not exceed capacity guidelines.Test, test, test!
- 37. Thank you for attending!
- 38. Patrick, we miss you