sharepoint app model architecture & design considerations - sean hester

‹#› SharePoint Saturday Atlanta|SharePoint Saturday Atlanta

Please thank our sponsors!Platinum Sponsors


Please thank our sponsors!Gold Sponsors


Please thank our sponsors!Silver Sponsors


Lunch Snack

SharePint

Please thank our sponsors!Item & Event Sponsors

Speaker ShirtsAttendee Shirts

Abel Solutions

Speaker Dinner

‹#› SharePoint Saturday Atlanta

Sean Hester – Senior Research Engineer, ThreeWill

SharePoint 2013 Application Models: Architecture & Design Considerations


Sean HesterSenior Research Engineer, ThreeWill [email protected]@seansageek@threewilllabs

Research Emerging Technologies & Best PracticesWeb Dev 1997 / .NET 2001 / SharePoint 2008MCSD Web Apps, MCTS SharePoint

About your presenter…


You Might Think You’ve Got Two Or Three Choices for SharePoint App Model Development: 1.App Web App (SharePoint-Hosted)2.Host Web App (SharePoint-Hosted)3.Provider-Hosted

#BoldStatement


#BoldStatementI Say You’ve Only Got One:

1.Where Are You Going To Host Your Provider-Hosted App?


2001

Team Services 1.0No There There

(Dev-Wise)

2003

WSS/Portal Server 2.0.NET

Web PartsCustom Forms

2007

WSS/Portal Server 3.0Application PagesCustom Features

2010

WSS/Portal Server 4.0Custom AdminListData.svc

Sandbox Solutions

2013

SharePoint Server 2013SharePoint Online / O365

Hosted SolutionsExpanded REST + CSOM

You Are

Here

BPOS.NET 1.0

Web MVC

(Struts)

ASP.NET MVC CTP

ASP.NET MVC

1.0

AngularBackbo

ne(i.e.

SPAs)

NHibernate

(.NET ORM)

EF 1.0

SharePoint’s Fundament

al Web Technologie

s

HTML 5.NET 4.5

MVC 5.0

EF 6.0Web API

2Signal R

…


Don’t Panic


App Web App


SharePoint (Farm or Online)

Host Web

OotB / Out-of-Band1.Users2.CAML

(Lists… Anything)

3.Web Parts4.App Pages5.Controls6.Etc.

Browser

App Web API

SharePoint-Hosted App1. CAML (Lists,

Fields)2. Web Artifacts

(HTML, JS, CSS)3. App Parts4. Custom Actions

Cloud Friendly

SharePoint Only

Simple Structure

No Middle

Tier

Fragile Integrati

on

Exposed Flanks

Design Limitations

Data Limitations

Reduced Productivit

y

~


1.All Your Use Cases Are Strictly UX Related

2.You Don’t Need Private Logic3.You Don’t Need App-Specific Security4.Your Data Needs Are Simple5.You Don’t Have Strict Availability

Requirements

Sweet Spot


Host Web App



Host Web


(Lists… Anything)


Browser

App Web API



(HTML, JS, CSS)3. App Parts4. Custom Actions

Cloud Friendly

SharePoint Only

Simple Structure

No Middle

Tier

Fragile Integratio

n

Exposed Flanks

Design Limitations

Data Limitations

Reduced Productivit

y

~



Host Web


(Lists… Anything)


API

Browser

App WebHost Web


(Lists… Anything)




(HTML, JS, CSS)3. App Parts4. Custom Actions5. ???

No Silo

Improved Data

Security… More Fragile Integration

Out-of-Band Sync

Reduced Host Security

ImprovedIntegration


1.All Your Use Cases Are Strictly UX Related

2.You Don’t Need Private Logic3.You Don’t Need App-Specific Security4.Your Data Needs Are Simple5.You Don’t Have Strict Availability

Requirements

Sweet Spot


Sweet Spot

6.Your Data Already Exists In A SharePoint Web

7.You Want Your Data To Live In The Host Web (For Whatever Reason)


Provider-Hosted App


“Provider” (Azure or Wherever)

Provider Web / Services

Provider App

1.CSOM (Broad Support) 2.Events3.Timer Jobs4.Workflow 5.App Services6.Anything!


App WebHost Web

OotB / Out-of-Band

API

Browser

SP App

API

SQL NoSQL Queue *Stable(r) Integratio

n

DesignChoices

Performance Controls

Revenue OptionsALM

Full Featured

Integration

Full Middle Tier! !


“Provider” (Azure or Wherever)

Provider Web / Services

Provider App

1.CSOM (Broad Support) 2.Events3.Timer Jobs4.Workflow 5.App Services6.Anything!


App WebHost Web

OotB / Out-of-Band

API

Browser

SP App

API

SQL NoSQL Queue *

Complex

Increased Effort

Learning Curve

Tooling LackingReduced Capability (vs Farm Solutions)


1.Your Use Cases Exceed UX2.You Need Private Logic3.You Need App-Specific Security4.You Need Complex and/or App-Specific

Data5.You Have Strict Availability

Requirements6.You Want To Leverage Server Side Code7.You Need Agency Beyond A Browser

Sweet Spot


Sweet Spot

8.You Have Tolerance For Complexity9.You Have Time To Learn


Capability Farm App Web Host Web ProviderAvailability, Stability 4 3 3 4

Schema, Data Management 5 3 3 5Design Flexibility

5 2 2 5

Operational Capability 4 3 3 4Packaging, Distribution, Deployment 4 2 2 4

Productivity, Resourcing, Tooling 5 2 2 3

User Experience 4 4 4 5

User Management, Security 5 1 1 5Biggest Delta


Where Are You Going To Host Your Provider-Hosted App?


Presentation DeckDemo Code

Complete Absence & Vacation Request, Help DeskPartials of Extranet Time & Task Entry

Reference ListWhite Paper (Coming Soon!)

Materials Available


Questions, Comments, Accusations…


Sean HesterSenior Research

Engineer, [email protected]@seansageek@threewilllabs

End of SessionWe value your feedback… please

complete event evaluation

sharepoint app model architecture & design considerations - sean hester

Technology