Upload
tihomir-ignatov
View
1.611
Download
0
Embed Size (px)
DESCRIPTION
Sharepoint 2013 related guidance for IT Architects
Citation preview
Sharepoint 2013: Practical Architecture from the FieldTihomir IgnatovSenior ConsultantMicrosoft Corporation
Architecture in Sharepoint Deployments
Software ArchitectureDeployment Architecture
Network ArchitectureDeployment Architecture
Enterprise architectureServer architecture
Information architectureData architecture
Business architecture
Permission architectureCloud architecture
Infrastructure architecture
What is IT Architecture?
Architecture is Making ideas real
“Make everything as simple as possible, but not simpler.”
-Albert Einstein
Sharepoint Architecture… WTF?
Software Architecture
Infrastructure Architecture
Information
Architecture
Business Architectur
e
Enterprise Architectur
e
Sharepoint Architecture… WTF?
Sharepoint (product) Architecture?!?
Consulting ArchitectsOrganizational
Architects
The Role of the Architect
Presales Solution Governance
IT Architecture Tradeoff
Architecture Delivery
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
Architecture Delivery
Requirements Gathering
DESIGNConceptual, Logical, Physical,
Application, Storage,…
Document all your decisions!
As Architect DO NOT code your projects
IT Architecture Tradeoff
Design against
requirements ONLY
Avoid unsupported scenarios, this is a
BUMERANG
Propose business value,
use ROI calculators
Calculate the ROI of each pillar of your
design and sell it out to the stakeholders!
Solution Governance
Requirements Engineering
Change Management
Architecture Validation TQA
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
General Sharepoint Architecture GuidanceALWAYS design against SCENARIOS instead of featuresTake into account the product limits and boundariesTalk 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
PLA?
Lessons Learned – Infrastructure
Private Cloud driven deployments
Extranet scenarios /w federated
identity
Office 365 & hybrid Azure IaaS
Lessons Learned – Self-service BI
Consider the “3rd party” connectivity
Validate all use cases &
supportability
Architecture Validation
The business process on 1st
place
Lessons Learned – Collaboration
Start using SOCIAL collaboration
Devices & Services
SkyDrive ProThe AAA:
Anytime, Anywhere, Any device
Lessons Learned – Social
A game changer! Challenge!
Offload your mailbox
The social newsfeed vs.
Yammer
Contact me
My blog: http://tihomirignatov.blogspot.com
Sharepoint User Group Bulgaria: http://www.sugbg.org
E-mail: [email protected]
Q & A