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.

1. Design a SharePoint 2013 Architecture -the
basics
Alexander Meijers
Netherlands, GMT+1
April 17th, 2014

2. SharePoint Lead
Architect
Portiva
Nieuwegein
Netherlands
Contact
@ameijers
ameijers@portiva.nl
www.SharePointInspiration.com (occasionally)

3. 

4. 









5. How to
create an
architecture

6. 
















7. Load Balancer
My Sites Intranet Internet

8. Explain the
steps in
creating an
architecture

9. 












10. 

















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

12. 











13. 






14. 









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

16. Business
Owners
Steering
committee
IT
Management
Risk &
Security
Compliance
Development
Team
End users

17. 





18. 



New!
New!
New!
New!

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

20. 








Enterprise
Enterprise
Enterprise

21. Topologies

22. 









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

25. Start designing
your SharePoint
2013
architecture

26. 

 http://technet.microsoft.com/en-us/library/cc263199.aspx



38. Load Balancer

39. Load Balancer

40. 













41. the complete
picture

42. Load Balancer
My Sites Intranet Internet

43. 











44. Other
important
things that
concern
architecture

45. 









46. 




