• Like

SharePoint App Model Architecture & Design Considerations - Sean Hester

  • 2,898 views
Uploaded on

Sean Hester's presentation on SharePoint App Model Architecture & Design Considerations. This was first presented at SharePoint Saturday in Atlanta in 2014.

Sean Hester's presentation on SharePoint App Model Architecture & Design Considerations. This was first presented at SharePoint Saturday in Atlanta in 2014.

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
2,898
On Slideshare
0
From Embeds
0
Number of Embeds
5

Actions

Shares
Downloads
5
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. ‹#› SharePoint Saturday Atlanta|SharePoint Saturday Atlanta Please thank our sponsors! Platinum Sponsors
  • 2. ‹#› SharePoint Saturday Atlanta|SharePoint Saturday Atlanta Please thank our sponsors! Gold Sponsors
  • 3. ‹#› SharePoint Saturday Atlanta|SharePoint Saturday Atlanta Please thank our sponsors! Silver Sponsors
  • 4. ‹#› SharePoint Saturday Atlanta|SharePoint Saturday Atlanta Lunch Snack SharePint Please thank our sponsors! Item & Event Sponsors SpeakerShirts Attendee Shirts AbelSolutions SpeakerDinner
  • 5. ‹#› SharePoint Saturday Atlanta Sean Hester – Senior Research Engineer, ThreeWill SharePoint 2013 Application Models: Architecture & Design Considerations
  • 6. ‹#› SharePoint Saturday Atlanta|SharePoint Saturday Atlanta SeanHester SeniorResearchEngineer,ThreeWillLabs shester@threewill.com @seansageek @threewilllabs ResearchEmergingTechnologies&BestPractices WebDev1997/.NET2001/SharePoint2008 MCSDWebApps,MCTSSharePoint About your presenter…
  • 7. ‹#› SharePoint Saturday Atlanta|SharePoint Saturday Atlanta 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
  • 8. ‹#› SharePoint Saturday Atlanta|SharePoint Saturday Atlanta #BoldStatement I Say You’ve Only Got One: 1. Where Are You Going To Host Your Provider-Hosted App?
  • 9. ‹#› SharePoint Saturday Atlanta|SharePoint Saturday Atlanta 2001 Team Services 1.0 No There There (Dev-Wise) 2003 WSS/Portal Server 2.0 .NET Web Parts Custom Forms 2007 WSS/Portal Server 3.0 Application Pages Custom Features 2010 WSS/Portal Server 4.0 Custom Admin ListData.svc Sandbox Solutions 2013 SharePoint Server 2013 SharePoint Online / O365 Hosted Solutions Expanded REST + CSOM You Are Here
  • 10. ‹#› SharePoint Saturday Atlanta|SharePoint Saturday Atlanta Don’t Panic
  • 11. ‹#› SharePoint Saturday Atlanta|SharePoint Saturday Atlanta App Web App
  • 12. ‹#› SharePoint Saturday Atlanta|SharePoint Saturday Atlanta SharePoint (Farm or Online) Host Web OotB / Out-of-Band 1.Users 2.CAML (Lists… Anything) 3.Web Parts 4.App Pages 5.Controls 6.Etc. Browser App Web API SharePoint-Hosted App 1. CAML (Lists, Fields) 2. Web Artifacts (HTML, JS, CSS) 3. App Parts 4. Custom Actions Cloud Friendly SharePoint Only Simple Structure No Middle Tier Fragile Integration Exposed Flanks Design Limitations Data Limitations Reduced Productivity ~
  • 13. ‹#› SharePoint Saturday Atlanta|SharePoint Saturday Atlanta 1. All Your Use Cases Are Strictly UX Related 2. You Don’t Need Private Logic 3. You Don’t Need App-Specific Security 4. Your Data Needs Are Simple 5. You Don’t Have Strict Availability Requirements Sweet Spot
  • 14. ‹#› SharePoint Saturday Atlanta|SharePoint Saturday Atlanta Host Web App
  • 15. ‹#› SharePoint Saturday Atlanta|SharePoint Saturday Atlanta SharePoint (Farm or Online) Host Web OotB / Out-of-Band 1.Users 2.CAML (Lists… Anything) 3.Web Parts 4.App Pages 5.Controls 6.Etc. Browser App Web API SharePoint-Hosted App 1. CAML (Lists, Fields) 2. Web Artifacts (HTML, JS, CSS) 3. App Parts 4. Custom Actions Cloud Friendly SharePoint Only Simple Structure No Middle Tier Fragile Integration Exposed Flanks Design Limitations Data Limitations Reduced Productivity ~
  • 16. ‹#› SharePoint Saturday Atlanta|SharePoint Saturday Atlanta SharePoint (Farm or Online) Host Web OotB / Out-of-Band 1.Users 2.CAML (Lists… Anything) 3.Web Parts 4.App Pages 5.Controls 6.Etc. API Browser App WebHost Web OotB / Out-of-Band 1.Users 2.CAML (Lists… Anything) 3.Web Parts 4.App Pages 5.Controls 6.Etc. SharePoint-Hosted App 1. CAML (Lists, Fields) 2. Web Artifacts (HTML, JS, CSS) 3. App Parts 4. Custom Actions 5. ??? No Silo Improved Data Security… More Fragile Integration Out-of-Band Sync Reduced Host Security Improved Integration
  • 17. ‹#› SharePoint Saturday Atlanta|SharePoint Saturday Atlanta 1. All Your Use Cases Are Strictly UX Related 2. You Don’t Need Private Logic 3. You Don’t Need App-Specific Security 4. Your Data Needs Are Simple 5. You Don’t Have Strict Availability Requirements Sweet Spot
  • 18. ‹#› SharePoint Saturday Atlanta|SharePoint Saturday Atlanta 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)
  • 19. ‹#› SharePoint Saturday Atlanta|SharePoint Saturday Atlanta Provider-Hosted App
  • 20. ‹#› SharePoint Saturday Atlanta|SharePoint Saturday Atlanta “Provider” (Azure or Wherever) Provider Web / Services Provider App 1. CSOM (Broad Support) 2. Events 3. Timer Jobs 4. Workflow 5. App Services 6. Anything! SharePoint (Farm or Online) App WebHost Web OotB / Out-of- Band API BrowserSP App API SQL NoSQL Queue * Stable(r) Integration Design Choices Performance Controls Revenue Options ALM Full Featured Integration Full Middle Tier! !
  • 21. ‹#› SharePoint Saturday Atlanta|SharePoint Saturday Atlanta “Provider” (Azure or Wherever) Provider Web / Services Provider App 1. CSOM (Broad Support) 2. Events 3. Timer Jobs 4. Workflow 5. App Services 6. Anything! SharePoint (Farm or Online) App WebHost Web OotB / Out-of- Band API BrowserSP App API SQL NoSQL Queue * Complex Increased Effort Learning Curve Tooling Lacking Reduced Capability (vs Farm Solutions)
  • 22. ‹#› SharePoint Saturday Atlanta|SharePoint Saturday Atlanta 1. Your Use Cases Exceed UX 2. You Need Private Logic 3. You Need App-Specific Security 4. You Need Complex and/or App-Specific Data 5. You Have Strict Availability Requirements 6. You Want To Leverage Server Side Code 7. You Need Agency Beyond A Browser Sweet Spot
  • 23. ‹#› SharePoint Saturday Atlanta|SharePoint Saturday Atlanta Sweet Spot 8. You Have Tolerance For Complexity 9. You Have Time To Learn
  • 24. ‹#› SharePoint Saturday Atlanta|SharePoint Saturday Atlanta Capability Farm App Web Host Web Provider Availability, Stability 4 3 3 4 Schema, Data Management 5 3 3 5 Design Flexibility 5 2 2 5 Operational Capability 4 3 3 4 Packaging, 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
  • 25. ‹#› SharePoint Saturday Atlanta|SharePoint Saturday Atlanta Where Are You Going To Host Your Provider-Hosted App?
  • 26. ‹#› SharePoint Saturday Atlanta|SharePoint Saturday Atlanta Presentation Deck Demo Code Complete Absence & Vacation Request, Help Desk Partials of Extranet Time & Task Entry Reference List White Paper (Coming Soon!) Materials Available
  • 27. ‹#› SharePoint Saturday Atlanta|SharePoint Saturday Atlanta Questions, Comments, Accusations…
  • 28. ‹#› SharePoint Saturday Atlanta|SharePoint Saturday Atlanta Sean Hester Senior Research Engineer, ThreeWill shester@threewill.com @seansageek @threewilllabs End of Session We value your feedback… please complete event evaluation