sharepoint 2013 applied architecture from the field (v2)

33
Tihomir Ignatov Senior Consultant Microsoft Corporation Sharepoint 2013: Applied Architecture from the Field October 23 rd 2013

Upload: tihomir-ignatov

Post on 28-May-2015

1.006 views

Category:

Technology


1 download

DESCRIPTION

A presentation from Sinergija 13 conference in Belgrade

TRANSCRIPT

Page 1: Sharepoint 2013 applied architecture from the field (v2)

Tihomir IgnatovSenior ConsultantMicrosoft Corporation

Sharepoint 2013: Applied Architecture from the Field

October 23rd 2013

Page 2: Sharepoint 2013 applied architecture from the field (v2)

AgendaWhat is IT Architecture

The Architect’s Obligations

The IT Architect and Sharepoint

Sharepoint 2013 Apps

Sharepoint Infrastructure Decisions

Page 3: Sharepoint 2013 applied architecture from the field (v2)

Software ArchitectureDeployment Architecture

Network ArchitectureDeployment Architecture

Enterprise architectureServer architecture

Information architectureData architecture

Business architecture

Permission architectureCloud architecture

Infrastructure architecture

Page 4: Sharepoint 2013 applied architecture from the field (v2)

What is IT Architecture?

Page 5: Sharepoint 2013 applied architecture from the field (v2)

Architecture is Making ideas real

“Make everything as simple as possible, but not simpler.”

-Albert Einstein

Page 6: Sharepoint 2013 applied architecture from the field (v2)

www.iasaglobal.org

Page 7: Sharepoint 2013 applied architecture from the field (v2)

Sharepoint Architecture… ?!?

Software Architecture

Infrastructure Architecture

Information Architecture

Business Architecture

Enterprise Architecture

Page 8: Sharepoint 2013 applied architecture from the field (v2)

Sharepoint (product) Architecture?!?

Consulting Architects Org. Architects

Presales

Solution Governance

IT Architecture Tradeoff

Architecture Delivery

Presales

Page 9: Sharepoint 2013 applied architecture from the field (v2)

Presales

Step into Customer’s

shoes

Always try to maximize the VALUE for the customer

The Sharepoint solutions are COMPLEX, ask your SMEs for support when

needed

Clearly define the in scope, out of scope,

constraints and limitations

Page 10: Sharepoint 2013 applied architecture from the field (v2)

Architecture Delivery

Requirements Engineering

DESIGNConceptual, Logical, Physical,

Application, Storage,…

Document all your decisions!

As Architect DO NOT code your projects

Page 11: Sharepoint 2013 applied architecture from the field (v2)

IT Architecture Tradeoff

Design against requirements

ONLY

Avoid unsupported scenarios, this is a

BUMERANG

Propose business value, use ROI

calculations

Calculate the ROI of each pillar of your design and

sell it out to the stakeholders!

Page 12: Sharepoint 2013 applied architecture from the field (v2)

Solution Governance

Requirements Traceability Change Management

Architecture Validation TQA

Page 13: Sharepoint 2013 applied architecture from the field (v2)

Technical Principles

CLOUD first Configure before customize

SolutionsNOT products

1 2 3

Page 14: Sharepoint 2013 applied architecture from the field (v2)

Sharepoint 2013 sales points

New BCM and DR model

More scalable incl. WFM & WAC

New search capabilities

The Collaboration is better with Lync and Ex (UCS & WAC)

Improved WCM (incl. licensing)

The new APP mode – huge partner opportunity

Page 15: Sharepoint 2013 applied architecture from the field (v2)

General Sharepoint Architecture Guidance

ALWAYS design against scenarios NOT features

Take into account the product limits and boundaries

Talk about RECOMMENDED and CURRENT instead of BEST practices

Ask Microsoft Premier support about supportability

Plan and maintain the capacity

Add the Governance plan in scope

Page 16: Sharepoint 2013 applied architecture from the field (v2)

WHAT IS PLA?SHAREPOINT, LYNC & EXCHANGE

MCS, PG & CSS

DELIVERY THROUGH MCS

Page 17: Sharepoint 2013 applied architecture from the field (v2)

Lessons Learned – SP Apps

Key Requirements Possible Approaches

Page 18: Sharepoint 2013 applied architecture from the field (v2)

Apps – Key Requirements

Consider your identity sources

Consider your App permissions level – hosting web/ tenant/…?

Cloud dependency – TO BE OR NOT TO BE?

Team skills – Sharepoint, ASP.NET, etc.

Page 19: Sharepoint 2013 applied architecture from the field (v2)

O365 (SPO)

Sharepoint 2013

Sharepoint hosted App

Cloud

On premise

Sharepoint hosted App

Sharepoint-Hosted App

• Any supported AutH sources• Client side code only

Page 20: Sharepoint 2013 applied architecture from the field (v2)

O365 (SPO) Azure PaaS

Remote App

Cloud

On premise

Sharepoint Auto-hosted

App

Auto-hosted App

• 100% cloud scenario• Any supported identity• Identity through Azure ACS

ACS

Page 21: Sharepoint 2013 applied architecture from the field (v2)

Any Data Center

Sharepoint 2013

Remote Web

Internet

On premise

Provider hosted App

Provider-Hosted App (Low-trust)

• Any supported AutH sources• Server side code in Remote

Web• Depends on Azure ACS

Azure

ACS

Context token

Page 22: Sharepoint 2013 applied architecture from the field (v2)

Web serverSharepoint 2013

Remote Web

Internet

On premise

Provider hosted App

Provider-Hosted App (High-trust)• Any supported AutH sources• You have to take care about remote

web identity and SSO• Server side code in Remote Web• NO cloud dependency

S2S STS

Page 23: Sharepoint 2013 applied architecture from the field (v2)

Web UI

A

B

C

Custom DB

Entity Framework

BizTalk

SPS and Content DBs

D

F

G

H

810 13

Presentation Layer

Application Layer

Data Layer

Web Services/Web API

7

I

E

User

Attached Files and Metadata

C

Page 24: Sharepoint 2013 applied architecture from the field (v2)

Lessons Learned – SP Infrastructure

Key Requirements Possible Approaches

Page 25: Sharepoint 2013 applied architecture from the field (v2)

SP Infra – Key Considerations (1)

Consider the availability and resources

Plan your servers and capacity, plan also the data growth…

Take into account the skills of the operations personnel

According to the new SP Apps infrastructure plan to have a SP Web application with no host header

Use host header site collections when you need site with unique URL

After Sharepoint deployment always deliver a Governance plan document, even in “lite” format

Page 26: Sharepoint 2013 applied architecture from the field (v2)

SP Infra – Key Considerations (2)

ALWAYS setup at least 2 environments – TEST & PRODUCTION

Create a simple application to track site collection requests

Plan a process for site collections and content DBs management

Use QUOTAs

Page 27: Sharepoint 2013 applied architecture from the field (v2)

Recommended Topologies (1)WFE

Front End Services

Distributed Cache

Back End Services

Workflow Manager

Crawl

Admin

Analytics

Content Processing

Index Partition #0Replica

DB

Content Databases

Search Databases

Config & Service DBs

• No HA• All services in a single box• Single point of failure• The data is not reserved• Up to 10M searchable

items

Page 28: Sharepoint 2013 applied architecture from the field (v2)

Recommended Topologies (2)

DB-1 DB-2

Content Databases

Search Databases

Config & Service apps DBs

WFE-1

Front End Services

Distributed Cache

Back End Services

Workflow Manager

Crawl

Admin

Analytics

Content Processing

Index Partition #0Replica

WFE-2

Front End Services

Distributed Cache

Back End Services

Workflow Manager

Crawl

Admin

Analytics

Content Processing

Replica

• There is HA• All services and the data

are reserved• Up to 10M searchable

items• Recommended for

business critical scenarios with small load

Page 29: Sharepoint 2013 applied architecture from the field (v2)

Recommended Topologies (3)

DB-1 DB-2

Content Databases

Search Databases

Config & Service apps DBs

WFE-1

Front End Services

Distributed Cache

WFE-2

Front End Services

Distributed Cache

APP-1

Back End Services

Workflow Manager

Crawl

Admin

Analytics

Content Processing

Index Partition #0Replica

APP-2

Back End Services

Workflow Manager

Crawl

Admin

Analytics

Content Processing

Replica

• There is HA• All services and the data

are reserved• Up to 10M searchable

items• Recommended for

business critical scenarios with big load

Page 30: Sharepoint 2013 applied architecture from the field (v2)

Recommended Topologies (4)

DB-1 DB-2

Content Databases

Search Databases

Config & Service apps DBs

WFE-1

Front End Services

Distributed Cache

WFE-2

Front End Services

Distributed Cache

APP-1

Back End Services

Workflow Manager

APP-2

Back End Services

Workflow Manager

APP-SRC-1

Crawl

Admin

Analytics

Content Processing

Index Partition #0Replica

APP-SRC-2

Crawl

Admin

Analytics

Content Processing

Replica

• There is HA• All services and the data

are reserved• Up to 10M searchable

items• Recommended for

business critical scenarios with big load and significant search requirements

Page 31: Sharepoint 2013 applied architecture from the field (v2)

Contact me

• My blog: http://tihomirignatov.blogspot.com• Sharepoint User Group Bulgaria:

http://www.sugbg.org • E-mail: [email protected]

Page 32: Sharepoint 2013 applied architecture from the field (v2)

Q & A

Page 33: Sharepoint 2013 applied architecture from the field (v2)

Please rate this lecture

and win Window Phone NOKIA Lumia 920

Help us choose the best Sinergija lecturer! Microsoft will award you – at the conference end, we’ll give one NOKIA Lumia 920 to someone from the audience – randomly.

Go to www.mssinergija.net, log in and cast your votes!

You can rate only lectures that you were present at, just once. More lectures you rate, more chances you have.

Winner will be announced at the official Sinergija web portal, www.mssinergija.net