Distributed Cache in SharePoint Server 2016 IT Preview


Overview

The Distributed Cache service provides in-memory caching services to several features in SharePoint Server 2016 IT Preview.

Some of the features that use the Distributed Cache service include:

  • Newsfeeds
  • Authentication
  • OneNote client access
  • Security Trimming
  • Page load performance

These features use the Distributed Cache for quick data retrieval. The Distributed Cache service stores data in memory and does not have a dependency on databases in SharePoint Server 2016 IT Preview. However, some SharePoint features may store data in both the Distributed Cache and databases.

Distributed Cache Improvements in SharePoint Server 2016 IT Preview

SharePoint Server 2016 IT Preview improves Distributed Cache performance and resiliency through a change which switches off NTLM authentication between SharePoint and the cache cluster; instead relying on encryption of cache data before transport.  In SharePoint Server 2013 under load/high scale – the cluster would start getting unresponsive to calls from SharePoint due to authentication overhead. i.e. every call from SharePoint, the cluster had to authenticate the call with AD.  This change also allows SharePoint Server 2016 IT Preview Distributed Cache clusters to scale up the number of client connections to help with throughput.

Topologies with MinRole and Distributed Cache

The Distributed Cache component is on by default in the SingleServerFarm role and in the Cache role for SharePoint Server 2016 IT Preview. 

To learn more about MinRole roles and services see also https://technet.microsoft.com/en-us/library/mt346114(v=office.16).aspx.

 

MinRole Roles and Distributed Cache

Role Name

Display Name Description Distributed Cache
WebFrontEnd Front End Services end user requests.  Optimized for low latency. No
Application Application Services backend jobs or requests triggered by backend jobs.  Optimized for high throughput. No
Cache Distributed Cache Services Distributed Cache.  Servers assigned to this role can load balance end user requests among Web Front End servers. Yes
Search Search Reserved for Search services. No
Custom Custom

Reserved for services to be isolated from other services, I.e. 3rd party, PerformancePoint, etc.

No
SingleServerFarm Single Server Farm

Provisions all services on the server for a single server deployment.  This role is provided for evaluation and development purposes.

Yes

 

Single Server Farm Example

All services isolated to the scope of single machine to include Distributed Cache.

SingleServerFarm

Content + Search Farm Example

All services isolated with the scope of a server farm.  Distributed Cache hosted on one or more dedicated servers.

ContentandSearchFarm

Content Farm + Search Farm Example

Services distributed across one or more content farms and one dedicated search farm.  Distributed cache hosted on one or more dedicated servers with the scope of the content farm.

ContentSearchFarm

Content + Service Farm Example

Services distributed across one or more content farms and one dedicated service farms.  Distributed cache hosted on one or more dedicated servers with the scope of the content and/or service farm.

ContentServiceFarm

Comments (7)

  1. MsSPJ says:

    Thank you so much Bill !!

  2. MsSPJ says:

    is there any SharePoint API interact with distributed cache to retrieve data for

    Newsfeeds
    Authentication
    OneNote client access
    Security Trimming
    Page load performance

    ?

  3. Ahmad Hamade says:

    As a developer, can we utilize distributed cache to save information? or its only used internally by SharePoint?

  4. Dennis Gaida says:

    MsSPJ: You can leverage the regular REST API to access available information. There is no official API to directly interact with cache objects.
    Ahmed: In SharePoint 2013 this was not allowed and not supported. You were always supposed to create your own cache cluster to interact with – since AppFabric standalone is discontinued there is no ways you can save information in any supported way leveraging
    this cache.

    Bill: The hardware requirements for SP2016 did not really change
    https://msdn.microsoft.com/en-us/library/cc262485(v=office.16).aspx, but we do have MinRoles now which is the new way to do things. MinRoles would mean that a "small farm" is at least 4 servers now. Customers with e.g. 1000 users wouldn’t really understand
    why they would need that many servers with that much RAM etc. – will there be any changes for the requirements? Also you often talk about a content & a service farm. That would mean double the farm licenses, again a hard sell why we would need a content and
    a service farm. If we’re talking 10.000 users and more users, maybe. Does MinRoles really mean "at least four servers"?

  5. Is there any recommendation for HA of Distributed Cache?

  6. Anonymous says:

    Estrenamos nuevo mes en el blog y toca compartir con todos vosotros la 2ª Edición del recopilatorio de

Skip to main content