Being a SharePoint architect can be challenging - you need to deal with everything from hardware, resources, requirements, business continuity management, a budget and of course customers. You, the architect, have to manage all this and in the end deliver a good architecture that satisfies all the needs of your customer. Along the line you have to make decisions based on experience, facts and sometimes the gut feeling. In this session we will cover some of the architectural changes in the SharePoint 2013 architecture, some of the new guidance from Microsoft and provide insight into a number of successful real-world scenarios. You will see what decisions were made while designing and implementing these projects with emphasis on why they were made.
Session “Real-world SharePoint architecture decisions” by Wictor Wilén, here are my notes:
Distributed Cache Service: Patches will be separately delivered. Wictor recommends to use the latest CU.
Request Management: Rule-based, software load balancing. Missconfigured rules can take down your farm.
Search: Rearchitectured and rewritten with using features from both FAST and SharePoint Search are implemented. Same engine is used for Exchange.
Office Web Apps (WAC): Wictor’s favorite service – separate application, separate server, separate patches.
Workflow: separate product – can be shared with multiple farms (not recommended)
Claims Based Authentication: the new default.
OAuth: Used for Authentication. A basic understanding really helps.
S2S Auth: Apps, Workflow use server to server authentication.
There is no perfect architecture you can download and apply.
Or as I would say: It depends.
3 is the new 2 – and 7 is the new 5
Means you need more servers – but think about the fault domain, if you virtualize you need redundant VM servers, if you do load balancing you need redundancy there. Always ask yourself how to patch this?
Routing, caching and database must be fast – every request go through there, if they are slow your farm will be slow.
Search Layer should have <500 msec latency. Many components are based on Search – make it fast!
Search requires different planning in 203 – cross site publishing, analytics, recommendations need to be taken care of. October 2013 CU contains huge improvements.
Workflow Server: You can install it on 1 or 3 servers – no other options.
Office Web Apps: Separate servers – no other option.
App Server: On prem, co-locate with SP server, Azure or other hosting options (LAMP) to offload the workload.
Certifcates: You should use certificates for about everything – when someone steals your oauth token they could access sensible data. Apps, WAC - and more.
Firewall: Firewall team should be involved early. Wictor will provide a firewall cheat sheet, because Technet lacks a good one.
User Profile: ADI, built-in FIM, External FIM are the options. He suggest to use external FIM but you need to license it.
MySites, Social, Yammer: MySite is a must. DirSync is a must for Yammer (to make it fault tolerant you need 4 additional servers, 2 ADFS, 2 Web Proxies)
Hybrid: Search is the key to hybrid, Mysites can be deployed on-prem or on O365.
Look and Feel: If you want to customize deploy the MySite on-prem.
Social. Yammer is the way forward.
Single Web Application approach
One WebApp to listen to all host headers, and is recommended. AppCatalog has to be in the same WebApp – if you use two, you need two AppCatalogs.
Memory footprint reduced.
Most often requires Host Named Site Collections.
For Host Named Site Collections he recommends a custom site creation provider.
Root Site Collection is required.
You need a load balancer for the custom http header.
Wictor showed us how to create a Host Named Site Collection (HNSC) with PowerShell. Very straight forward, worked like a charm and is another good reason to use PowerShell.
Then Wictor showed some pretty extensive samples – can not write them down, was too complex to summarize, but was very useful to see complex scenarios – would love to see them in Technet as reference.
List of things people often forget in SharePoint architectures:
- High Availability and Desaster recovery
- 20% of the farms Wictor sees have 99.9% uptime
- 10% had 100% uptime requirements (impossible).
- Affects the cost
- Provider Hosted Apps
- Access Services 2013
Things to avoid / consider
Multi-tenancy, often done for the wrong reasons. For large-scale hosting consider O365.
Streched Farms – read http://askwictor.com/spstreched
Service Farms and Service Application federation: Makes solution more complex, understand limitations upfront. Managed Metadata Service is a good service to federate.
So many good sessions in parallel – Future of Infopath or the session by Spencer Harbar about Identity Federation (homework) – I am still glad that I attended Wictor’s session, good stuff, I learned quite a lot and “refreshed” many topics I tend to forget. The room was packed, there is obviously a huge demand!
Wictor delivered so many stuff in a short time (my notes are therefore not complete!) – he is really fast paced