SharePoint Saturday (Belgium): Designing complex SharePoint architectures

416
-1

Published on

Published in: Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
416
On Slideshare
0
From Embeds
0
Number of Embeds
6
Actions
Shares
0
Downloads
0
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide
  • Template may not be modified Twitter hashtag: #spsbe for all sessions
  • Please use a picture of yourself in a mountain/cloudscene
  • SharePoint Saturday (Belgium): Designing complex SharePoint architectures

    1. 1. Designing complexSharePointarchitectures#spsbeJussi Roinejussi@onsight.fi
    2. 2. Thanks to ourSponsorsPlatinumGoldSilver
    3. 3. About meJussi Roine // jussi@onsight.fi@jussiroine /jussiroine
    4. 4. Agenda(or how Ihope you’llstay awake)• SharePoint architecture overview• Changes, limitations and supported models• Topologies for internet, extranet and internet• Extending to Windows Azure and Office 365
    5. 5. Belgium is sogreat!You’ve got..
    6. 6. We’ve got..
    7. 7. Butsadly, we’vealso got..
    8. 8. So..Can you adopt me?please?
    9. 9. SharePointarchitectureoverview
    10. 10. There’s morethan onearchitectureto considerInformationarchitecture (IA)LogicalarchitecturePhysicalarchitectureStrategy and planfor informationaccess Navigation Sites and sitecollectionsstructure Taxonomies andmetadataNonphysicalstructure of solution Reflects businessfunctionality Readable fornontechnicalbusiness users Maps to solutionarchitectureHardware, softwareand topologies CPU, memory,storage Software Network Topologies Cloudconsiderations
    11. 11. LogicalarchitecturecomponentsServer FarmsService ApplicationsApplication PoolsWeb ApplicationsZonesContent DatabasesSite CollectionsSites, Lists, LibrariesDo you really need more than 1 farm? Why?Consistent with SP2010 – consider if you’ll need all SA’sUse shared App Pools, unless business drivers dictateotherwiseSeparate Web Apps for security, performance andcustomizationsMinimize number of zones used – default zone is importantStrong recommendations for sizing :-)Single site collection is easier but not always possibleAvoid folders – use available workarounds
    12. 12. ServiceApplications• Service Apps maintain consistency withSP2010 Service Apps• Avoid complexity – cross-farm servicesisn’t the best of ideas• The critical ones are UPA, Search andMMS• 3 new Service AppsApp ManagementServiceTranslation Service Work ManagementService
    13. 13. Keep theseclose to yourheart andpillow• SharePoint 2013 softwareboundaries and limitshttp://bit.ly/Znx466• Plan logical architecturehttp://bit.ly/11HzuKV• Keep the architecture simple• No bonus points for having the mostadvanced setup in the world!
    14. 14. Physicalarchitecture• Simplicity is the ultimate form of SharePointsophistication• Start with 1 farm – virtual or physical• Get familiar with Microsoft Product LineArchitecture guidance http://bit.ly/12FeYeL• Align with SharePoint Online using reasonableeffort• In fact, what’s the reason for staying on-premises?• Host-named site collections vs. Path-based sitecollections• Drive for HA while keeping SLA in mind
    15. 15. What’s the”bestpractice”?• There isn’t one!• It fully depends onresources, budget, businessrequirements, people andexperience• Who defines the real bestpractice?• Meetings with multiplevendors, each arguing about whatthey’ve found on the Internet to bethe truth.. are not productive (unless
    16. 16. Changes,supportedmodels,limitations
    17. 17. Changes:HardwarerequirementsHardware requirementsFarm model RAM CPUSingle server 24 GB 4 coresSmall farm1 App/WFE + SQL16 GB (App/WFE)16 GB (SQL)4-8 coresMedium farm2 WFE + 1-2 App +SQL16 GB (WFE)16 GB (App)32 GB (SQL)4-8 coresLarge farm2-3 WFE + 2-3 App+ SQL16 GB (WFE)16 GB (App)32 GB (SQL)4-8 cores
    18. 18. Changes: OSand SQLversionsWindows Server 2008 R2 SP1/2012• Either one is fine but 2012 is an obviouschoice by nowSQL Server 2008 R2 SP1/2012• Remember Cumulative Updates• Enterprise Edition is needed for AlwaysOnAvailability Groups and snapshots duringupgrades
    19. 19. Service LevelAgreements(SLA)Forget ”the 5 nines”• No sense to target 99,999% with SP – that’s 6,05seconds of downtime per week• Azure IaaS is operating at 99,95% (5,04mins/week)• SP Online and Google Apps are 99,9% (10,1mins/week)• You’ll always need regular maintenance breaks forWindows and SP patchingDefine what ’available’ means in the context
    20. 20. Supportedmodels:StretchedfarmStretched farm is back• Not supported during RTM, support restored 4th ofApril, 2013• Requires low latency (<1ms) between components of thefarm• Requires 1 Gigabit connectivity for intrafarm connectionsIt’s not a default option• Don’t do it for fun or just as a precaution• Not a replacement for DR and HA!
    21. 21. StretchedfarmexplainedDatacenter ADatacenter BStretched farm requires additional planning for:Reverse Proxy Proxies Firewall(s)Load balancingRemote access Scalability
    22. 22. DistributedCacheOverview• Distributed Cache provides support for 10caches, including Login Tokens and SecurityTrimming• Cache Cluster can be distributed or dedicated• SharePoint assigns 10% of total physical memoryto Distributed Cache• Half of that is used for data storage (ascache), other half is overhead• Cache might eventually use the whole 10% ofallocated memory
    23. 23. DistributedCacheLessons learned• If you add physical memory, reconfigureDistributed Cache• Graceful shutdown during maintenance andserver reboots, which nobody really does..• Max 4 servers can run DistributedCache, even if Technet states 12 inBoundaries guidance• Max 16 GB cache per host (64 GB total with4 hosts)
    24. 24. Licensing forInternet andExtranetExtranet• Server license + CALs for internal users only• No CALs for external usersInternet• Server license• No CALs for external or internal usersWindows Server and SQL Server licensednormally
    25. 25. Special cases New low-latency layer• Distributed Cache and Request Management canform their own very low-latency layer in front ofWFE’sWindows Azure Workflow• Service Bus requires 3 servers for high availabilityOffice Web Apps• Use dedicated servers, even if you could install onsame boxes with SharePoint roles
    26. 26. Topologiesfor Intranet,Extranet andInternet
    27. 27. Start withexistingguidance• Architectural guidance is solid http://bit.ly/Matt1S• Not all farms and services will have tens orhundreds of thousands of users• A 250 user farm still needs proper architecturedesign, even if it feels simple• Since hardware and licenses are alwaysexpensive, be clear on what is needed• Plan for growth and future, remember PLA
    28. 28. Farms inSP2013Small farmMedium farmLarge farm
    29. 29. In the endWe’re all farmers..
    30. 30. Internet farmtopology• At least 2 WFE’s and 2 App Servers• SQL must be HA – not necessarily atraditional Active/Passive cluster• QA, test and dev environmentsstrongly recommended• You can and should leverage AzureIaaS (or similar offerings)
    31. 31. The switchmodel – orachievinghigh SLA’sTwo farms• One for production, one for staging/QA• Switch production between the two farms• Licensing and hardware is costly – cannot sharebetween farms• Huge overhead, somewhat complex to manage• It’s advanced and rare, but still an optionFor high SLA but at a steep cost!
    32. 32. The switchvisualizedFarm A Farm BLoad-balancingDNSPROD QA
    33. 33. Extranet farmtopology• Can be collocated with intranet/internet farm(s)• On-premises vs. Cloud considerations• Distributed Cache is crucial, keep in mind thelimitations• IA is more important, sites tend to grow• DR is more important than HA• Authentication, authorization and federationshould be carefully planned
    34. 34. Multi-tenancy• Multi-tenancy: Just.. don’t• Challenging to configure and maintain• Adds complexity• Created for Office 365, not on-premises• But if you think you’ll need it, rethink itonce more ;-)
    35. 35. Sampleintranettopology• Intranet with search, collaboration andteam sites• 8000 users, global audience• ”Profile only” experience, no My Sites• Multilingual content, variations notused• On-Prem for now, O365 in the future• Development and testing done inAzure
    36. 36. SampleintranettopologyProductionQA
    37. 37. But we needeverything!DC + RMWFEAppSQLWAWOffice WebApps
    38. 38. Contentpublishing• Content Deployment is dead – let it restin peace pieces• Cross Site Publishing (XSP) is not adirect replacement but a spiritualsuccessor• XSP is still 1.0 and has limitations andflaws (March PU)• Do you need content publishing withinmultiple farms?
    39. 39. Cross-FarmServices andmultiplefarmsUsed to share SA’s that are beneficialto share• Search, UPA, BCS, MMS are quickwins• Adds complexity• Requires some IT Pro work forconfiguring and managing
    40. 40. SharePointApps• SP Apps are really for intranet and verytrusted use• Luckily UAG provides SP2013 supportwith SP3.. except for apps• Little guidance available for recovery, HAand DR (Technet, I love to hate you)• So think for the future, decide how you’llembrace the new app model
    41. 41. Extending toWindowsAzure andOffice 365
    42. 42. Hybriddeployments• Certain workloads work better in on-premises or the cloud• Getting the best from Office 365 and on-premises investments• Hybrid model currently supported forSearch, BCS and Duet Enterprise• Requires a fair amount of configuration• Guidance available http://bit.ly/UM5mLx
    43. 43. HybridSearchUse a single query to retrieve search results from bothindexesChoose one or both• Get search results from SPO for on-prem• Get search results from on-prem for SPOYou’ll need• Domain federation• Server-to-server trust and identity management• Service integration
    44. 44. HybridSearchSource: Microsoft (http://technet.microsoft.com/en-us/library/dn197168.aspx)
    45. 45. WindowsAzure IaaS• Azure IaaS is great• But it’s not cheap http://bit.ly/uRVnjf• Cost-savings can be achieved by destroyingthe VMs when inactive• Challenging to get political approval for VirtualNetwork (site-to-site VPN)• Best suited for development and test –possibly also QA• It’s yet another cloud
    46. 46. WindowsAzure IaaSVirtualNetwork• $36/month (or $0.05 * 720 hours)• Technically easy to set up, but requirescareful design• Difficult to debugAzure VM’sCorporatenetworkSite-to-site VPNAD DCAD DC
    47. 47. Summary • Aim for simple, you’ll end upcomplex anyway• Consider the workloads, budgetyour farm(s) accordingly• Brace yourself for the cloud• Just because it’s new, doesn’tmean it’s working
    48. 48. THANK YOUJussi Roine, Onsight HelsinkiEmail and Lync: jussi@onsight.fiBlog: http://jussionsharepoint.comTwitter: @jussiroine

    ×