Intro to SharePoint 2013 Architecture

Report
Intro to SharePoint 2013
Architecture
Liam Cleary
About Me
• Solution Architect @ 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
Content
Database
Zone
Web
Applications
Site Collections
Sites
Lists & Libraries
Web Application
Logical
Architecture
Default Zone
Internet Zone
Windows NTLM
Forms Based
Internal URL
External URL
• Service Applications
• Shared Services between Web Applications and SharePoint Farms
• Critical Service Applications
Logical
Architecture
• 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
Hardware Requirements
http://technet.microsoft.com/en-us/library/cc262485.aspx
Physical
Architecture
Farm Model
RAM (Per Server)
CPU (Per Server)
Single Server
24 GB
4 Cores
Small Farm
1 x WEB/APP + SQL
16 GB WEB/APP
16 GB SQL
4-8 Cores
Medium Farm
2 WEB + 1-2 APP + SQL
16 GB WEB
16 GB APP
32 GB SQL
4-8 Cores
Large Farm
2-3 WEB + 2-3 APP + SQL
16 GB WEB
16 GB APP
32 GB SQL
4-8 Cores
Support Systems
• Windows Server 2008 R2 SP1 or Windows Server 2012
• Preference is Server 2012
• SQL Server 2008 R2 SP1 or SQL Server 2012 / 2014
Physical
Architecture
• http://www.microsoft.com/en-us/sqlserver/sql-server-2014.aspx
• Enterprise Edition is needed for Always On Availability Groups
•
http://msdn.microsoft.com/en-us/library/ff877884.aspx
• Ensure cumulative updates
Supported Topologies – Limited Deployments
One Server Farm
Physical
Architecture
Two Tier farm
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
Load Balancer
Physical
Architecture
Supported Topologies – Large
Large Farm
Physical
Architecture
Web servers for all incoming requests
Dedicated web server(s) for crawling
and administration
Query and index servers
All other search components
All other services (use these servers for
the Central Admin site)
Content databases and configuration
database
Search databases
All other SharePoint databases
Servers for running sandboxed code
Supported Topologies – Hybrid
Hybrid Farm
Physical
Architecture
Load Balancer
On-Premise
COLO
10.10.1.254/24
192.168.1.254/24
Stretched Farm
10.10.1.100/24
192.168.1.100/24
10.10.1.101/24
10.10.1.102/24
192.168.1.101/24
10.10.1.103/24
10.10.1.104/24
192.168.1.102/24
Physical
Architecture
VIP Address
10.10.1.120/24
192.168.1.120/24
10.10.1.106/24
10.10.1.107/24
192.168.1.103/24
Always On – Availability Group
New Features
Physical
Architecture
Feature
Details
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
New Features – Request Management
Physical
Architecture
Requests for PDF, WMV
Requests for: http://intranet
Requests for: http://extranet
Requests for: http://www.site.com
Search (Attend Bert's Search Session)
• Massive Scale Topologies
• Continuous Crawling
• No need for Full / Incremental
Physical
Architecture
Load Balancer
Web
Server
Office
Web
Apps
Server
Web
Server
Office
Web
Apps
Server
• Distributed Design
• Multi Failover – Multi Subnets
• Always On Clustering
• PowerShell is the only way to
manage the topology
Application Server
Application Server
Query Processing
Query Processing
Replica
Application Server – All other
Application Server Roles
Crawl
All SharePoint Databases
Crawl DB
Index Partition 0
Replica
Application Server – All other
Application Server Roles
Crawl
All SharePoint Databases
• Topology limitations have been removed
• Distributed Cache limited to 4 servers
• Hybrid Solutions are now a viable option
Final
Thoughts
•
•
•
•
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
• Virtualization Guidance
• http://technet.microsoft.com/en-us/library/ff607968.aspx
• Logical Architectures
• http://technet.microsoft.com/en-us/library/ff829836.aspx
• Global Deployments
Resources
• http://technet.microsoft.com/en-us/library/gg441257.aspx
• Performance & Capacity
• http://technet.microsoft.com/en-us/library/cc262971.aspx
• Authentication
• http://technet.microsoft.com/en-us/library/ee794879.aspx
• Backup & High Availability / Disaster Recovery
• http://technet.microsoft.com/en-us/library/cc261687.aspx
• http://technet.microsoft.com/en-us/library/cc263031.aspx
Liam Cleary
Email: [email protected]
Twitter: @helloitsliam
Blog: http://blog.helloitsliam.com
Contact

similar documents