Hiya,
In order to better understand the SP2013 architecture, there are of course a few questions underway. One of them is around the distributed cache. I'd like the sanity check on the following statements regarding setup of same. First of, my approach to SharePoint installations is to ONLY install what is required. In other words, my default settings for this service would be disabled.
Distributed Cache should only be installed if required. The following cases serves as examples to a distributed cache:
1: Cases with federated authentication and 2 or more active web-front servers. This in order to reduce logon times, using the logon token cache.
2: If your solution uses news feed function on MySites. Distributed Cache is a prerequisite.
3: If your solution supports 10000+ Users.
4: If your solution has other elements from distributed cache as prerequisite.
I am not even sure I would install it, if I had 4 active web front ends in a intranet solution. Unless geographically different locations etc. I would probably use some other method to insure correct users on correct server.
The argumentation comes from the following:
1: When running the Distributed Cache service on a server, it must not be running with dynamic memory. (Cost goes up)
2: When running the Distributed Cache, it is recommended to be run on a dedicated server. (Cost goes up)
3: The amount of problems that can arise when not Installed/configured according to usage.
4: If its not needed, dont install it.
In my upinion the entire feed handling should be placed in a Service application, rather than a Cache service instance. Or atleast be split up to its own.
I'd like to hear any argumentation why I should include this service as a basic service to my SharePoint 2013 installation.
Basically derived from:
Overview of microblog features, feeds, and the Distributed Cache service in SharePoint Server 2013
http://technet.microsoft.com/en-us/library/jj219700.aspx
Plan for feeds and the Distributed Cache service in SharePoint Server 2013
http://technet.microsoft.com/en-us/library/jj219572.aspx
AppFabric Caching and SharePoint: Concepts and Examples (Part 1)
http://blogs.msdn.com/b/besidethepoint/archive/2013/03/27/appfabric-caching-and-sharepoint-1.aspx
AppFabric Caching (and SharePoint): Configuration and Deployment (Part 2)
http://blogs.msdn.com/b/besidethepoint/archive/2013/03/27/appfabric-caching-and-sharepoint-2.aspx
In order to better understand the SP2013 architecture, there are of course a few questions underway. One of them is around the distributed cache. I'd like the sanity check on the following statements regarding setup of same. First of, my approach to SharePoint installations is to ONLY install what is required. In other words, my default settings for this service would be disabled.
Distributed Cache should only be installed if required. The following cases serves as examples to a distributed cache:
1: Cases with federated authentication and 2 or more active web-front servers. This in order to reduce logon times, using the logon token cache.
2: If your solution uses news feed function on MySites. Distributed Cache is a prerequisite.
3: If your solution supports 10000+ Users.
4: If your solution has other elements from distributed cache as prerequisite.
I am not even sure I would install it, if I had 4 active web front ends in a intranet solution. Unless geographically different locations etc. I would probably use some other method to insure correct users on correct server.
The argumentation comes from the following:
1: When running the Distributed Cache service on a server, it must not be running with dynamic memory. (Cost goes up)
2: When running the Distributed Cache, it is recommended to be run on a dedicated server. (Cost goes up)
3: The amount of problems that can arise when not Installed/configured according to usage.
4: If its not needed, dont install it.
In my upinion the entire feed handling should be placed in a Service application, rather than a Cache service instance. Or atleast be split up to its own.
I'd like to hear any argumentation why I should include this service as a basic service to my SharePoint 2013 installation.
Basically derived from:
Overview of microblog features, feeds, and the Distributed Cache service in SharePoint Server 2013
http://technet.microsoft.com/en-us/library/jj219700.aspx
Plan for feeds and the Distributed Cache service in SharePoint Server 2013
http://technet.microsoft.com/en-us/library/jj219572.aspx
AppFabric Caching and SharePoint: Concepts and Examples (Part 1)
http://blogs.msdn.com/b/besidethepoint/archive/2013/03/27/appfabric-caching-and-sharepoint-1.aspx
AppFabric Caching (and SharePoint): Configuration and Deployment (Part 2)
http://blogs.msdn.com/b/besidethepoint/archive/2013/03/27/appfabric-caching-and-sharepoint-2.aspx