Telligent Enterprise 3.0 has incorporated Windows Server AppFabric caching, a technology used to enhance system performance by distributing system cache over different servers. Windows Server AppFabric is Telligent's officially supported distributed cache.
In AppFabric caching, data items stored in memory can be called independently of the system database. The net effect of caching is to remove database bottlenecks and improve system performance. (For general information about AppFabric, refer to the Microsoft documentation.)
Because Windows Server AppFabric is based on IIS, it maps well into the concept of a Web farm. Conceptually, AppFabric security must be configured properly at a domain level before configuring AppFabric on a Web farm. If you are familiar with configuring Web farms, you should be able to follow Microsoft's guidelines for enabling AppFabric caching on your Web farm.
Here is a summary of situations in which to apply AppFabric within your Web Farm:
Please see following url for full architecture information:
Scenario 1: 1 Web server, 1 database server
In this configuration, all .NET Framework 4 WCF/WF services are managed on one AppFabric hosting and management server. The persistence and monitoring databases exist on a separate server running SQL Server. Multiple clients access the .NET Framework 4 WCF/WF services through the single AppFabric hosting and management Web server.
Scenario 2: n Web servers, 1 database server
For load balancing to work effectively on an AppFabric Web farm, the configuration on all the AppFabric servers in the cluster must appear identical to clients. Each cluster server should contain the same .NET Framework 4 WCF/WF services and inherit the same configuration settings.
All servers share the same SQL Server monitoring and persistence databases. This means that all display the same configuration and data within the AppFabric user interface. Because all have the same applications, configuration, and databases, all computers will display the same monitoring metrics in their AppFabric Dashboard and related Tracked Events, Persisted WF Instances, and Tracked WF Instances pages.
Scenario 3: n web servers, m service machines*, 1 database server
The above diagram shows a load-balanced AppFabric Web farm cluster that uses the AppFabric caching server to store ASP.NET session state. This caching cluster is a separate logical cluster from the AppFabric hosting and management Web farm cluster. In the diagram, all computers in the AppFabric caching server cluster access either the SQL Server configuration store, or the Windows Server XML cache configuration store - but not both.
*(where service machines run tasks or AppFabric)
Full architecture information: http://msdn.microsoft.com/en-us/library/ee677374.aspx