Intro to SharePoint 2013 Architecture Liam Cleary

About Me Solution Protiviti SharePoint MVP Everything SharePoint Architecture Infrastructure Development Security SharePoint Dreamer Speak at lots of community events

Agenda Logical Architecture Physical Architecture Final Thoughts

Logical Architecture Server Farms Service Applications Application Pools Web Applications Zone Content Database Site CollectionsSitesLists & Libraries

Logical Architecture Default Zone Windows NTLM Internal URL Internet Zone Forms Based External URL Web Application

Logical Architecture Service Applications Shared Services between Web Applications and SharePoint Farms Critical Service Applications User Profile Application Search Application Managed Metadata Service New Service Applications App Management Service Marketplace Permissions and connectivity Translation Service Auto translate files and content Work Management Service Aggregate tasks from SharePoint, Exchange, Project and any other Provider based platforms

Physical Architecture Farm ModelRAM (Per Server)CPU (Per Server) Single Server24 GB4 Cores Small Farm 1 x WEB/APP + SQL 16 GB WEB/APP 16 GB SQL 4-8 Cores Medium Farm 2 WEB APP + SQL 16 GB WEB 16 GB APP 32 GB SQL 4-8 Cores Large Farm 2-3 WEB APP + SQL 16 GB WEB 16 GB APP 32 GB SQL 4-8 Cores Hardware Requirements

Physical Architecture Support Systems Windows Server 2008 R2 SP1 or Windows Server 2012 Preference is Server 2012 SQL Server 2008 R2 SP1 or SQL Server 2012 / Enterprise Edition is needed for Always On Availability Groups Ensure cumulative updates

Physical Architecture Supported Topologies – Limited Deployments One Server FarmTwo Tier farm

Physical Architecture Supported Topologies – Small Multi Purpose Four Server Farm

Physical Architecture Supported Topologies – Medium Farm Six Server Farm

Physical Architecture Supported Topologies – Medium Farm + Office Web Apps Six Server Farm

Physical Architecture Supported Topologies – Large Large Farm

Physical Architecture Supported Topologies – Hybrid Hybrid Farm

Physical Architecture Stretched Farm

Physical Architecture New Features FeatureDetails Distributed Cache Stores Login Tokens and Security Trimming Custom components can utilize Request Management Manage incoming request based on rules engine Route requests Prioritize important requests Identity and block harmful requests Azure Workflow Separate download Scale to multiple servers – Not on the SharePoint Servers Creates multiple Databases for Scale and Configuration Office Web Apps Requires it’s own server infrastructure now Connect to SharePoint, Exchange and Lync Provides the Hover Panel Document Preview Capabilities

Physical Architecture New Features – Request Management

Physical Architecture Search (Attend Bert's Search Session) Massive Scale Topologies Continuous Crawling No need for Full / Incremental Distributed Design Multi Failover – Multi Subnets Always On Clustering PowerShell is the only way to manage the topology

Final Thoughts Topology limitations have been removed Distributed Cache limited to 4 servers Hybrid Solutions are now a viable option Windows Azure Amazon AWS Private Cloud Office 365 Stretched Farms require high latency Service Applications now allow for better scale and control over incoming requests REMEMBER: SharePoint 2013 is a memory eater TechNet Guidance “NEEDS” to be updated – Review constantly as things will change

Resources Virtualization Guidance Logical Architectures Global Deployments Performance & Capacity Authentication Backup & High Availability / Disaster Recovery

Contact Liam Cleary Blog: