SharePoint 2010 -An Architectural OverviewJohan BuysmansSharePoint Solution Architect
Johan BuysmansSharePoint Architect @ OrdinaCompetence Center Leader+10 yrs ECMLast 3 yrs working @ Johnson & Johnson as a SharePoint Solution Architect  johan.buysmans@ordina.be
SharePoint 2010An Architecture OverviewFarm ArchitectureAdministrative featuresSharepoint Architecture
Farm Architecture4
Farm ArchitectureAll-in-one Server+All Roles and SQL on one serverOften seen in small farmsSQL contention with SharePointEasy to deploy, but not best practice-No ability for test environmentNOTE: Do not use SQL Express in Production!
Farm ArchitectureDedicated SQL Database Server+Dedicated SQL ServerAll SharePoint roles on single boxLess Disk IOGreater Performance-Still no test environment…
Farm ArchitectureSmallest Highly Available Farm2 Web/Query/Application /Central Admin/Inbound Email Servers1 Dedicated Index Server (With Web role to allow it to crawl content)2 SQL Standard Edition Cluster Nodes (Active/Passive) – Mirror also optionSmallest highly available farm
Farm ArchitectureScalabilityScale up and Scale out…
Farm ArchitectureScalabilityScale up and Scale out…
Virtualised Farm ArchitectureCost Effective Farm / No HAAllows organisations that wouldn’t normally be able to have a test environment to run one
Allows for separation of the database role onto a dedicated server
Can be easily scaled out in the futureHigh-Availability across Hosts
All components virtualised
Uses only two Windows Ent Edition LicensesVirtualised Farm ArchitectureFully Redundant Farm with only Two Servers
VirtualisedFarm ArchitectureBest Practise, Highly Available and  Scalable FarmHighest transaction servers are physical
Multiple farm support, with DBs for all farms on the SQL cluster
Only five physical servers total, but high performanceVirtualised Farm ArchitectureVirtualisation Scalability
High Availability ArchitectureSQL Database MirroringAvailable in SQL Server 2005/2008, both Standard and Enterprise MirroringKeep a full copy of Database on another serverAsynchronous (good for WAN scenarios, Enterprise edition only) or Synchronous
High Availability Architecture Database Mirroring – Single Site OptionSingle SiteSynchronous ReplicationUses a SQL Witness Server to Failover AutomaticallyMirror all SharePoint DBs in the FarmUse a SQL Alias to switch to Mirror Instance
High Availability Architecture Database Mirroring – Cross SiteTwo Sites1 ms Latency1GB BandwidthFarm Servers in each locationAuto Failover
High Availability Architecture Database Mirroring –  Warm Farm AsynchronousTwo SitesTwo Farms (one warm farm)Mirror only Content DBsFailover is ManualMust Reattach DBsMust re-index
Logical ArchitectureWeb Application  ArchitectureConsider creating multiple Web AppsExample:spca.companyabc.comssp1.companyabc.commysite.companyabc.comhome.companyabc.comFlexible and scalable!
Logical ArchitectureDistribute by DefaultDistribute content across multiple Site CollectionsDistribute Site Collections Across Multiple DBsMultiple databases = more controlled DB growthTry to keep your Content DBs manageable in size (50-100GB)
Hardware and SoftwareDisk, Memory, and ProcessorSQL Databases Require large amounts of space!Allocate Disk Space for Index and Query Servers as wellIndex corpus can grow to 5%-20% of total size of data indexedDatabase and Index Servers require most RAM (4GB, 8GB, or more)Multi-core processors recommended
Hardware and SoftwareWindows Server VersionsWindows Server 2008 R2 (or RTM) highly recommended!Critical that new servers run x64, required for SharePoint 2010SharePoint servers are fine with Standard edition of Windows, no extra gain for EnterpriseSQL Servers may require Enterprise edition if using SQL Enterprise
Hardware and SoftwareSQL Server VersionsSQL Server 2008 Recommended64 bit also highly recommended (required for SharePoint 2010)SQL Server 2005 still supportedSQL 2000 supported for Sharepoint 2007, but not for 2010, and not recommendedSeparate SQL Reporting Services server may be required for intensive reportingStandard edition of SQL generally fine, except for very large environments
Administrative Features23
Security is no more overhead to ITAutomatic Password ManagementServer addition secured by  PassphraseAPIs for permission reporting
Predictable UpgradeDo-no-harmPre-upgrade checkerVisual UpgradeResumable upgradeProgress reportsParallel DB upgrades
Logging, Monitoring, and AlertsKnow what is going onUnified LoggingOut-of-the-box reportsRicher Web AnalyticsOpen SchemaSCOM IntegrationULS LogsWindows EventsLogging DBPage requestsFeature LoggingHealth data
Proactive Resolution Get ahead of issuesDeveloper DashboardEmpower developers and usersIntegrated Health AnalyzerRuns when necessaryAlerts anomalies Fixes when it can
Developer DashboardInformation contained on the dashboard:Times to render various components on pagePage Checkout levelDatabase query informationWeb part processing timeAny critical events or alertsGood for diagnosing problem web parts on a page or long list load time
SharePoint Architecture29

Ordina SOFTC Presentation - SharePoint 2010 Architecture

  • 1.
    SharePoint 2010 -AnArchitectural OverviewJohan BuysmansSharePoint Solution Architect
  • 2.
    Johan BuysmansSharePoint Architect@ OrdinaCompetence Center Leader+10 yrs ECMLast 3 yrs working @ Johnson & Johnson as a SharePoint Solution Architect [email protected]
  • 3.
    SharePoint 2010An ArchitectureOverviewFarm ArchitectureAdministrative featuresSharepoint Architecture
  • 4.
  • 5.
    Farm ArchitectureAll-in-one Server+AllRoles and SQL on one serverOften seen in small farmsSQL contention with SharePointEasy to deploy, but not best practice-No ability for test environmentNOTE: Do not use SQL Express in Production!
  • 6.
    Farm ArchitectureDedicated SQLDatabase Server+Dedicated SQL ServerAll SharePoint roles on single boxLess Disk IOGreater Performance-Still no test environment…
  • 7.
    Farm ArchitectureSmallest HighlyAvailable Farm2 Web/Query/Application /Central Admin/Inbound Email Servers1 Dedicated Index Server (With Web role to allow it to crawl content)2 SQL Standard Edition Cluster Nodes (Active/Passive) – Mirror also optionSmallest highly available farm
  • 8.
  • 9.
  • 10.
    Virtualised Farm ArchitectureCostEffective Farm / No HAAllows organisations that wouldn’t normally be able to have a test environment to run one
  • 11.
    Allows for separationof the database role onto a dedicated server
  • 12.
    Can be easilyscaled out in the futureHigh-Availability across Hosts
  • 13.
  • 14.
    Uses only twoWindows Ent Edition LicensesVirtualised Farm ArchitectureFully Redundant Farm with only Two Servers
  • 15.
    VirtualisedFarm ArchitectureBest Practise,Highly Available and Scalable FarmHighest transaction servers are physical
  • 16.
    Multiple farm support,with DBs for all farms on the SQL cluster
  • 17.
    Only five physicalservers total, but high performanceVirtualised Farm ArchitectureVirtualisation Scalability
  • 18.
    High Availability ArchitectureSQLDatabase MirroringAvailable in SQL Server 2005/2008, both Standard and Enterprise MirroringKeep a full copy of Database on another serverAsynchronous (good for WAN scenarios, Enterprise edition only) or Synchronous
  • 19.
    High Availability ArchitectureDatabase Mirroring – Single Site OptionSingle SiteSynchronous ReplicationUses a SQL Witness Server to Failover AutomaticallyMirror all SharePoint DBs in the FarmUse a SQL Alias to switch to Mirror Instance
  • 20.
    High Availability ArchitectureDatabase Mirroring – Cross SiteTwo Sites1 ms Latency1GB BandwidthFarm Servers in each locationAuto Failover
  • 21.
    High Availability ArchitectureDatabase Mirroring – Warm Farm AsynchronousTwo SitesTwo Farms (one warm farm)Mirror only Content DBsFailover is ManualMust Reattach DBsMust re-index
  • 22.
    Logical ArchitectureWeb Application ArchitectureConsider creating multiple Web AppsExample:spca.companyabc.comssp1.companyabc.commysite.companyabc.comhome.companyabc.comFlexible and scalable!
  • 23.
    Logical ArchitectureDistribute byDefaultDistribute content across multiple Site CollectionsDistribute Site Collections Across Multiple DBsMultiple databases = more controlled DB growthTry to keep your Content DBs manageable in size (50-100GB)
  • 24.
    Hardware and SoftwareDisk,Memory, and ProcessorSQL Databases Require large amounts of space!Allocate Disk Space for Index and Query Servers as wellIndex corpus can grow to 5%-20% of total size of data indexedDatabase and Index Servers require most RAM (4GB, 8GB, or more)Multi-core processors recommended
  • 25.
    Hardware and SoftwareWindowsServer VersionsWindows Server 2008 R2 (or RTM) highly recommended!Critical that new servers run x64, required for SharePoint 2010SharePoint servers are fine with Standard edition of Windows, no extra gain for EnterpriseSQL Servers may require Enterprise edition if using SQL Enterprise
  • 26.
    Hardware and SoftwareSQLServer VersionsSQL Server 2008 Recommended64 bit also highly recommended (required for SharePoint 2010)SQL Server 2005 still supportedSQL 2000 supported for Sharepoint 2007, but not for 2010, and not recommendedSeparate SQL Reporting Services server may be required for intensive reportingStandard edition of SQL generally fine, except for very large environments
  • 27.
  • 28.
    Security is nomore overhead to ITAutomatic Password ManagementServer addition secured by PassphraseAPIs for permission reporting
  • 29.
    Predictable UpgradeDo-no-harmPre-upgrade checkerVisualUpgradeResumable upgradeProgress reportsParallel DB upgrades
  • 30.
    Logging, Monitoring, andAlertsKnow what is going onUnified LoggingOut-of-the-box reportsRicher Web AnalyticsOpen SchemaSCOM IntegrationULS LogsWindows EventsLogging DBPage requestsFeature LoggingHealth data
  • 31.
    Proactive Resolution Getahead of issuesDeveloper DashboardEmpower developers and usersIntegrated Health AnalyzerRuns when necessaryAlerts anomalies Fixes when it can
  • 32.
    Developer DashboardInformation containedon the dashboard:Times to render various components on pagePage Checkout levelDatabase query informationWeb part processing timeAny critical events or alertsGood for diagnosing problem web parts on a page or long list load time
  • 33.
  • 34.
    SharePoint 2010 ArchitectureSharePointServerClient AppsSharePoint Service ApplicationsProject Server2010Browsers (IE, Fire Fox)PowerPoint Broadcast ServiceSearch ServiceProject Web AccessOffice ClientExcel Calc ServiceWeb Analytics ServiceFAST Search ServiceVisio Graphics ServiceFAST 2010 OneNoteFAST Search ServiceUser ProfilesVisio Graphics ServiceBusinessConnection ServiceInfoPathAccess ServiceBusinessConnection ServiceAccess ServiceManaged MetadataOffice Web App ServiceProjectInfoPath ServiceManaged MetadataOutlook PerformancePointWord Conversion ServicePerformancePoint3rd PartyServices..RSS ViewersSharePoint FoundationSandboxed Code ServiceSharePoint WorkspaceSandboxed Code ServiceUsage & Health LoggingSharePoint DesignerVisioContentConfigWorkflowAccess
  • 35.
  • 36.
    W3C standards andaccessibility compliant
  • 37.
    Popular tools meansyou can deploy the site you want
  • 38.
    Communities through Web2.0 technologies
  • 39.
    Business Connectivity Servicesprovides integration and visualization of LOB data, securely, and simplyIntranetIntranetExtranetExtranetInternetInternet
  • 40.
    Key TakeawaysHighly considerVirtualization for SharePointCreate a test farm!Consider Database Mirroring and/or NLB for SharePoint HADeploy the ‘five server farm’ for full High AvailabilityPlan today for SharePoint 2010 !!
  • 41.
    Follow Ordina….33Share yourthoughts via #SOFTC Follow us on twitter: @OrdinaBEFind the presentationsonwww.slideshare.net/ordinaBeBe informed atwww.linkedin.com/company/ordina-belgium

Editor's Notes

  • #12 Key MessageSharePoint 2010 extends the base SharePoint Server 2007 architecture.Presenter NotesWSS 3.0 is now SharePoint Foundation and the Shared Service Provider has been replaced by a series of individual Service Applications.SharePoint Foundation now includes the functionality to provide Sandboxed Solutions and usage and health logging. This provides insights into what is happening on your farm and how pages are being used.The number and type of default services has increased to include a range of additional functions. These are individual, so you can more closely manage the functions that are available to each site. These can also be extended by 3rd Party services from ISVs or other software vendors.Extension services include FAST Search, which extends the capabilities of the default SharePoint Search and the Office Web Apps, which enable you to use browser-based Office functionality, without having to load the client applications.The number of integrated client apps has also been extended to include Access and Visio.
  • #32 Key Message: SharePoint delivers flexible, feature rich Internet solutionsPresenter Notes: Lecture from the slide.SharePoint can no longer be seen as a Microsoft-proprietary environment when it comes to browsers. It now supports leading browsers, including Firefox and Safari. It maintains the ability to automatically deploy content. This is configured through the central administration site, where you can deploy and configure all site. SharePoint 2010 delivers on W3C standards and accessibility compliant, which makes it far more attractive as an Internet-facing Web site for general users. The flexible development and user tools makes it easy to develop and deploy sites and information, so you can react to business change quickly.You can also deliver Web 2.0 functionality to customers, through social computing, tagging, and FAST Search. The flexibility to store and deliver any document format – multimedia or traditional documents – makes it all the more compelling for customers, and don’t forget the ease or deployment for staff. Even information that is “locked” securely in you LoB system, can be visualized to your customers through Business Connectivity Services, without any security reduction.