This session walks you through the necessary steps to design a SharePoint 2013 architecture. It explains what information is needed to actually design such an architecture and discusses the many things you need to know to make the right decisions. It helps you to design a small, medium or large SharePoint farm for your customers.
11.
Groups of people Location Data Accessed
Internal employees Intranet Intranet Portal, Company information, internal
data, internal project sites, my sites and profiles.
External employees Internet, Remote Session Same as internal employees
Partners Internet, Remote Session Project sites, Partner Portal
Visitors Internet A companies website, customer Portal
15. SharePoint Online Hybrid
Azure On Premises
Subscription
Search
portal
On premises
Sites
Reverse
proxy
SharePoint
Server 2013
Search
portal
Sites
SharePoint Online
Web servers
All databases
Application
servers
Dedicated application
servers for search
components
Active
Directory
On Premises
On premises
SharePoint Online
Active
Directory
Directory
synchronization
Windows Azure Active
Directory Tenant
Windows Azure
Subscription
Virtual Network
Cloud Service
AD 1 AD 2
On Premises
WFE1
WFE2
WFE3
App
App
SQL 1
SQL 2
Cloud Service
SharePoint Farm Windows Server Active
Directory and DNS
80/443
Windows Azure
VPN Tunnel
Active
Directory
19.
http://my/personal/<user>
http://my
Application Pool
HR
http://Fabrikam
Application Pool
Facilities Purchasing
http://communities
Web Application—Published Intranet Content Web Application—My Sites Web Application—Community Sites
Application Pool
IIS Web Site— SharePoint Web Services
Default group
Team 1
http://team
Team 2 Team 3
Web Application—Team Sites
Excel
Services
Business Data
Connectivity
Managed
Metadata
App
Management
Machine
Translation
Word
Automation
Access
Services
Visio
Graphics
Work
Management
Search
Secure Store
Service
User Profile
23. Role Traditional Topology Streamlined Topology
(each tier optimized)
Streamlined
Topology
(Optimize for)
Web Server /
Front-end server
Fast, Light-weight server which
responds to user requests from web
pages. All web servers are mirrors of
each other and load balanced.
Directs requests to the appropriate
application servers
Service Applications, Services
and components that serve
user requests directly
Low latency
Access Services, BCS,
Metadata, User Profile
Application
Server / Batch-
processing server
Runs one or more services in the
SharePoint Farm. Load balancing
possible by redundant application
servers
Service Applications, Services
and components that process
background tasks. Also called
batch processing.
Load
User Profile
Synchronization, Workflow,
Machine translation, Work
management
Search on separate
dedicated machines
Database Server Stores content and service data.
Databases can be clustered or
mirrored for failover protection
Stores content and service
data. Databases can be
clustered or mirrored for
failover protection
Throughput
24. Farm Number of
servers
Purpose
Limited Deployment 1-2 Used for product evaluation, development and testing
with a limited number of users
Small farm 3-4 Serve a large number of users and scales out based on
how heavily services are used. These types of farms are
not always fault-tolerant
Medium farm 6+ Serve a large number of users and scales out based on
how heavily services are used. Their goal is a multi-
purpose environment with possible optimalisation.
These farms are always fault-tolerant.
Large farm Mostly a lot Serve a large number of users. Group service
applications, services or databases that have similar
performance characteristics on dedicated servers
Limit Maximum value Limit type Notes Application pools - 10 per web serverThreshold - The maximum number is determined by hardware capabilities.This limit is dependent largely upon: The amount of memory allocated to the web servers. The workload that the farm is serving, that is, the user base and the usage characteristics (a single highly active application pool can utilize 10 GB or more)
As an alternative to the traditional farm design, Microsoft® SharePoint® 2013 topologies can be designed to optimize system resources and to maximize performance for users. Optimizing each tierFront-end servers — Service applications, services, and components that serve user requests directly are placed on front-end servers. These servers are optimized for fast performance. Batch-processing servers — Service applications, services, and components that process background tasks are placed on a middle-tier of servers referred to as batch processing servers. These servers are optimized to maximize system resources. These servers can tolerate greater loads because these tasks do not affect performance observed by users.Database-servers — guidance for deploying database servers remains the same.In a small farm, server roles can be combined on one or two servers. For example, front-end services and batch-processing services can be combined on a single server or on two or more servers to achieve redundancy.