0
Mirjam van Olst

Best Practices & Considerations for Designing
Your SharePoint Logical Architecture
About me
http://sharepointchick.com
@mirjamvanolst
mirjam@outlook.com
Agenda
Introduction

Logical Architecture
Design

• Web Applications
• Service Applications
• Site Collections &
Content D...
Introduction
Logical Architecture

Configuration of
your SharePoint
environment

Continuous
monitoring
needed
Logical Architecture Design

Get the most
from out-of-thebox SharePoint

Be able to
scale your
environment

Avoid common
h...
Logical Architecture Design

Functional Drivers
• Shared security
• Content rollup
• Shared settings

Technical Drivers
• ...
Logical Architecture Design
Safest bet: use your crystal ball
Second best:
Good insight into
the environment
and the
organ...
SharePoint Hierarchy
Farm
Servers
Web Applications
Content Databases

Site Collections
Sites
Libraries and Lists
Items
Logical Architecture Design
Logical Architecture Design

1
Web
Applications

2

3

4

Service
Applications

Content
Databases
& Site
Collections

Site...
Web Application Considerations
Potential Influences:
– Intended Use
– Scalability
– SharePoint App policies
– Host Header ...
Host Named Site Collections

Best practice
for new
deployments

Created using
PowerShell
(no User
Interface)

Hosted in a
...
Host header-less web applications

SharePoint
Apps

Multi-Tenancy

Request
Management

…expect more
in the future

New cap...
When to use Path Based Sites

Self Service
Site Creation

Unique wild
card inclusion
Managed Paths

Security
isolation wit...
Host Named vs. Host Header

Host Named Site
Collections:

Host Header Web
applications:

•

•
•

1 web application

•

Por...
Custom Solutions
Custom solutions can be deployed to:
All Web
Applications

A specific Web
Application

The Farm
SharePoint Apps

App Catalog per
Web Application

App settings for
users per Web
Application
SharePoint Apps
Software Boundaries
Web Applications

Limit
Web Applications
Zone
Managed Path
Application Pools

Maximum Value
20 per far...
Reasons for multiple web apps

Usage

Service
Applications

SharePoint
Apps and
Custom
Solutions
Logical Architecture Design

1
Web
Applications

2

3

4

Service
Applications

Content
Databases
& Site
Collections

Site...
Service Application model

Service
Applications can
easily be scaled
out

Web applications
can pick and
choose service
app...
Service Applications
Proxy Groups
• A proxy group is a group of Service Application
Proxies (connections) that are selected for one or
more web...
Proxy Groups

User Profile

Business Data
Connectivity

http://my

App
Management

Machine
Translation

Excel

Managed
Met...
Service Application Considerations

Isolation

Scalability

What
functionality
and where?
Scaling of Services
• First role to move to a dedicated server is crawl
• Calculations in Excel Services could use a lot o...
Logical Architecture Design

1
Web
Applications

2

3

4

Service
Applications

Content
Databases
& Site
Collections

Site...
Content Databases
• A content database should be within 100 to 200 GB
• A site collection is always stored in a single con...
Sites and Site Collections
Influencers

People

Content

Site Types
Sites and Site Collections
Within a site collection the following things can shared:
•
•
•
•
•
•
•
•
•

Navigation
Content...
Sites and Site Collections
Functional reasons for multiple site collections

Complex
security

Separate
backup and
restore...
Sites and Site Collections
Architectural reasons for multiple site collections

More than
2000 sub
sites per “site
view”

...
Software Boundaries
Site Collections
Limit

Maximum Value

Limit Type

Site collections per farm

250,000 for non-personal...
Logical Architecture Design

1
Web
Applications

2

3

4

Service
Applications

Content
Databases
& Site
Collections

Site...
Software Boundaries
Security

Limit

Maximum Value

Limit Type

Security Scopes per list

5,000

Recommended

Number of Sh...
Security
Don’t use item level security if you can avoid it
– “Sharing” an item or document means using item level
security...
Security
Don’t use item level security if you can avoid it
– “Sharing” an item or document means using item level
security...
Wrap up
Wrap Up

Consider
Functional
and
Technical
drivers

Thorough
investigation
and planning
needed

Design for
growth

Custom
...
THANK YOU
SPCA2013 - Best Practices & Considerations for Designing Your SharePoint Logical Architecture
SPCA2013 - Best Practices & Considerations for Designing Your SharePoint Logical Architecture
SPCA2013 - Best Practices & Considerations for Designing Your SharePoint Logical Architecture
Upcoming SlideShare
Loading in...5
×

SPCA2013 - Best Practices & Considerations for Designing Your SharePoint Logical Architecture

583

Published on

Best Practices & Considerations for Designing Your SharePoint Logical Architecture

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
583
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
44
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Transcript of "SPCA2013 - Best Practices & Considerations for Designing Your SharePoint Logical Architecture"

  1. 1. Mirjam van Olst Best Practices & Considerations for Designing Your SharePoint Logical Architecture
  2. 2. About me http://sharepointchick.com @mirjamvanolst mirjam@outlook.com
  3. 3. Agenda Introduction Logical Architecture Design • Web Applications • Service Applications • Site Collections & Content Databases • Sites Wrap Up
  4. 4. Introduction
  5. 5. Logical Architecture Configuration of your SharePoint environment Continuous monitoring needed
  6. 6. Logical Architecture Design Get the most from out-of-thebox SharePoint Be able to scale your environment Avoid common health and performance challenges
  7. 7. Logical Architecture Design Functional Drivers • Shared security • Content rollup • Shared settings Technical Drivers • Boundaries
  8. 8. Logical Architecture Design Safest bet: use your crystal ball Second best: Good insight into the environment and the organization Thorough understanding of SharePoint internals
  9. 9. SharePoint Hierarchy Farm Servers Web Applications Content Databases Site Collections Sites Libraries and Lists Items
  10. 10. Logical Architecture Design
  11. 11. Logical Architecture Design 1 Web Applications 2 3 4 Service Applications Content Databases & Site Collections Sites
  12. 12. Web Application Considerations Potential Influences: – Intended Use – Scalability – SharePoint App policies – Host Header Web Applications vs. Host Named Site Collections
  13. 13. Host Named Site Collections Best practice for new deployments Created using PowerShell (no User Interface) Hosted in a single web application without a host header
  14. 14. Host header-less web applications SharePoint Apps Multi-Tenancy Request Management …expect more in the future New capabilities in SharePoint have been designed for, and expect a web application with no host header
  15. 15. When to use Path Based Sites Self Service Site Creation Unique wild card inclusion Managed Paths Security isolation with separate app pools
  16. 16. Host Named vs. Host Header Host Named Site Collections: Host Header Web applications: • • • 1 web application • Portal Team Sites / Project Sites My Sites
  17. 17. Custom Solutions Custom solutions can be deployed to: All Web Applications A specific Web Application The Farm
  18. 18. SharePoint Apps App Catalog per Web Application App settings for users per Web Application
  19. 19. SharePoint Apps
  20. 20. Software Boundaries Web Applications Limit Web Applications Zone Managed Path Application Pools Maximum Value 20 per farm 5 per web application 20 per web application 10 per web server Limit Type Supported Boundary Supported Supported
  21. 21. Reasons for multiple web apps Usage Service Applications SharePoint Apps and Custom Solutions
  22. 22. Logical Architecture Design 1 Web Applications 2 3 4 Service Applications Content Databases & Site Collections Sites
  23. 23. Service Application model Service Applications can easily be scaled out Web applications can pick and choose service applications Some Service Applications can be shared across farms
  24. 24. Service Applications
  25. 25. Proxy Groups • A proxy group is a group of Service Application Proxies (connections) that are selected for one or more web applications • By default, all Service Application Proxies are included in the default proxy group • A web application can: • Use the default proxy group • Use a custom proxy group and select service application proxies • A custom proxy group is specific to a web application when using the user interface
  26. 26. Proxy Groups User Profile Business Data Connectivity http://my App Management Machine Translation Excel Managed Metadata Excel Search Secure Store Visio Graphics http://teams http://projects http://intranet http://communities
  27. 27. Service Application Considerations Isolation Scalability What functionality and where?
  28. 28. Scaling of Services • First role to move to a dedicated server is crawl • Calculations in Excel Services could use a lot of CPU • User Profile synchronization single point of failure • Only one User Profile Service Application and one Search Service Application per server • Access Services needs it’s own SQL Server instance or SQL Server server
  29. 29. Logical Architecture Design 1 Web Applications 2 3 4 Service Applications Content Databases & Site Collections Sites
  30. 30. Content Databases • A content database should be within 100 to 200 GB • A site collection is always stored in a single content database • Limiting the size of a content database could be a reason to use multiple site collections
  31. 31. Sites and Site Collections Influencers People Content Site Types
  32. 32. Sites and Site Collections Within a site collection the following things can shared: • • • • • • • • • Navigation Content types Site Columns SharePoint Apps Master pages SharePoint Security groups Lookup fields for lists Search scopes Feature set
  33. 33. Sites and Site Collections Functional reasons for multiple site collections Complex security Separate backup and restore schedules and demands Site Collection quotas Decentralized administration
  34. 34. Sites and Site Collections Architectural reasons for multiple site collections More than 2000 sub sites per “site view” More than 250,000 sub sites More than 100-200GB of content Complex authorization structures per site
  35. 35. Software Boundaries Site Collections Limit Maximum Value Limit Type Site collections per farm 250,000 for non-personal site collections Supported Site collections per farm 750,000 Supported Site collections per content database 2,500 for non-personal site collections Supported Site collections per content database 5,000 Recommended Users in a site collection 2 million (after more than 1,000 the user interface will no longer scale and PowerShell should be used) Supported
  36. 36. Logical Architecture Design 1 Web Applications 2 3 4 Service Applications Content Databases & Site Collections Sites
  37. 37. Software Boundaries Security Limit Maximum Value Limit Type Security Scopes per list 5,000 Recommended Number of SharePoint groups a user can belong to 5,000 Supported Users in a SharePoint group 5,000 Supported Security principal per Access Control List (ACL) 5,000 Supported
  38. 38. Security Don’t use item level security if you can avoid it – “Sharing” an item or document means using item level security!
  39. 39. Security Don’t use item level security if you can avoid it – “Sharing” an item or document means using item level security!
  40. 40. Wrap up
  41. 41. Wrap Up Consider Functional and Technical drivers Thorough investigation and planning needed Design for growth Custom solutions add complexity and risk
  42. 42. THANK YOU
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×