08 Jun 2012
07 Jun 2012
Link to this post
We have a question about how and when Sitefinity invalidates content in its cache. We assume that changes made to content through the CMS will invalidate the cache for the edited item so the next request for that item will get the fresh content.
We have a client with a non-standard server configuration. There are a number of production servers that are used by a load balancer. Each of these runs an instance of Sitefinity, and all point to the same database.
There is a separate "admin" server used to manage all content changes. The Sitefinity instance on this server is pointed to the same database as all of the load-balanced instances. All servers, including the admin server are on completely separate physical boxes.
Currently, we are trying to track down a content publishing delay issue where changes made on the admin instance do not immediately appear when browsing the production instance(s). We are investigating the load-balancer to see if it is providing caching that could be causing the delay, but we want to know if the current production configuration of Sitefinity server(s) described above could be the issue.
Our main question is this: If multiple server instances share the same CMS database, and content is edited using any one of those instances, will the SF caching in the other server instances be correctly invalidated for the changed content? Or, is our setup a recipe for a caching disaster?
Thanks for any insight!