This document discusses different approaches to architecting SharePoint solutions. It describes enterprise SharePoint solutions, SharePoint sandbox solutions, and solutions that use SharePoint data without being deployed to SharePoint. It covers considerations for each like security, performance, and deployment approach. It also provides examples of architecture patterns and best practices for designing flexible and maintainable SharePoint solutions.

1. SharePoint Solution
Architecture
Adis Jugo
managing consultant

2. Perception of SharePoint applications
Adis Jugo, PlanB.

3. Impact
Inspiration
Business
Operations
Case
Deploy
Life Require-
Cycle
ments
Testing / Solution
QA Architect.
Develop
Adis Jugo, PlanB.

4. Requirements
Inspiration
Business
Operations
Case
Deploy
Life Require-
Cycle
ments
Testing / Solution
QA Architect.
Develop
Adis Jugo, PlanB.

5. Time and Costs estimation
Inspiration
Business
Operations
Case
Deploy
Life Require-
Cycle
ments
Testing / Solution
QA Architect.
Develop
Adis Jugo, PlanB.

6. Time and Costs estimation
Adis Jugo, PlanB.

7. Architecture
Inspiration
Business
Operations
Case
Deploy
Life Require-
Cycle
ments
Testing / Solution
QA Architect.
Develop
Adis Jugo, PlanB.

8. Architecting SharePoint solutions
Adis Jugo, PlanB.

9. What is wrong with this web part?
Adis Jugo, PlanB.

10. Types of SharePoint solutions
• Enterprise SharePoint Solutions
• SharePoint SandBox Solutions
• Solutions that use SharePoint data

11. 4 questions for architects
• How will the users be using the application?
• How will the application be deployed into production and
managed?
• What are the quality attribute requirements for the application
(security, performance, concurrency, localization, and configuration)
• How can the application be designed to be flexible and maintainable
over time?

12. Architecture Considerations
• Considerations • Quality attributes
o Impersonation o Security
o Logging o Performance
o Caching o Concurrency
o Testing o Localization /
o Deployment Internationalization
o Flexibility / Manageability / o Configuration
FutureProof o …

13. SHAREPOINT ENTERPRISE SOLUTIONS

14. A SharePoint Solution
Managet
Code /
Workflows Silverlight Ajax
Office
Timer Jobs
Clients
!NET /
Event
Mobile/
Receivers
Tablet
InPage
SP WinRT /
Solution Metro
Adis Jugo, PlanB.

16. BL Classes not
SPContext Aware
SPContext
Transport/Creation?
SPContext Aware
Infrastructure Layer
Classes
Dependency
injection

18. Logging
• Logging from the BL
• ULS for SharePoint
• Different
implementations
LOGGING

19. Caching, Persistence
• Caching in front-end
Web Server
o AppFabric for
Windows Server
Caching, persistence
o NCache
• Persistence
o SPPersistedObject

20. Localization / Internationalization
• Chrome
• User Interface
• Navigation
• Content
Adis Jugo, PlanB.

21. Architecting InPage elements: MVP Model
Adis Jugo, PlanB.

22. Unit Testing
• Unit Testing Business
Layer
• Unit Testing
SharePoint DAL
o nUnit
• Unit Testing InPage
o presenter
Adis Jugo, PlanB.

23. DEMO
SHAREPOINT ENTERPRISE APPLICATION LAYOUT

24. SharePoint Enterprise Solutions
• Considerations • Quality attributes
o Impersonation  o Security 
o Logging o Performance => ?
o Caching o Concurrency 
o Testing o Localization /
o Deployment  Internationalization
o Flexibility / Manageability / o Configuration 
FutureProof 

25. Where is the catch
• Everything is SharePoint App Pool
o Deep impact on SharePoint Server
• Deployment to SharePoint Server
o Policies
o Maintenance
• Not possible with Office 365 (or other hosted services)

26. SHAREPOINT SANDBOX SOLUTIONS

27. SHAREPOINT SANDBOX SOLUTIONS

28. SandBox Solutions
• Considerations • Quality attributes
o Impersonation  o Security 
o Logging  o Performance => ?
o Caching  o Concurrency 
o Testing  o Localization /
o Deployment  Internationalization 
o Flexibility / Manageability / o Configuration 
FutureProof 

29. SOLUTIONS THAT USE SHAREPOINT DATA

30. SOLUTIONS WITH SHAREPOINT DATA
• Considerations • Quality attributes
o Impersonation =>  o Security 
o Logging  => No ULS o Performance 
o Caching  o Concurrency 
o Testing  o Localization /
o Deployment  Internationalization 
o Flexibility / Manageability / o Configuration 
FutureProof 

31. No SPContext aware
Components

32. SharePoint Enterprise Solutions
• Considerations • Quality attributes
o Impersonation => ? o Security 
o Logging  => No ULS o Performance 
o Caching  o Concurrency 
o Testing  o Localization /
o Deployment  Internationalization 
o Flexibility / Manageability / o Configuration 
FutureProof 

33. Limitations
• ASMX Services
• OData
• CSOM (Client SharePoint Object Model)
• No advanced list-data management
• No Event Receivers, Timer Jobs
• Outside of SharePoint user interface
• Suitable for integrating other solutions with SharePoint

34. And finally
Adis Jugo, PlanB.

35. Resources
• MS P&P: SharePoint Guide • Asterix and Cleopatra
http://spg.codeplex.com http://www.amazon.com/s/ref
=nb_sb_noss?url=search-
• MVP pattern in SharePoint alias%3Daps&field-
InPage elements (WebParts, keywords=asterix+and+cleopa
ASPX) tra&x=0&y=0
http://msdn.microsoft.com/en-
us/library/ee413740.aspx
http://www.plan-b-gmbh.com

36. • http://www.plan-b-gmbh.com
• http://www.adisjugo.com
@adisjugo
Adis Jugo, PlanB.