Sitefinity is the most popular CMS that is considered by business owners to create a rich and functional website. The CMS now supports distributed output cache that helps to deliver about 200 times better performance in some scenarios. If you are now aware of this recent feature of Sitefinity, then this blog will help you to understand it better.
In case you are familiar with this concept and are equally excited to know more about this feature in Sitefinity development then read this.
Here, we will explain what Sitefinity CMS distributed output cache is and the reasons why you should consider it.
Understanding Output Cache:
As per Microsoft’s definition, output cache is an optimization mechanism that enables ASP.NET to send the pre-processed copy of a page without having to go through the entire process of running DB queries, assembling the web pages and then sending the final output to the client. This helps to reduce the web server response time.
It is also the most crucial caching layer as it is the first one that is hit by any request and also ensures that the web page content is served quickly from the cache instead of having it being processed on the server every time there is a hit.
Sitefinity CMS uses the web server memory by default to store the output cache items and this option often boosts the speed of getting the content from the cache and delivering it to the website visitors, thereby, delivering the best response time.
When it is all about maintenance, in-memory output cache storage does not need any extra maintenance and configuration, as the server memory is used for an easier solution. Though it has some effects on the server memory consumption footprint, the in-memory output cache does not need any additional cost for any external cache storage.
Also Read: How To Prepare a Content Plan for Your Sitefinity Website?
Why is it important to have a distributed output cache?
Using the distributed cache often has various advantages when compared to the storing cache items in-memory. It solves the following problems:
1.Reduced Memory and CPU utilization on the web server nodes
2.When the worker process recycles, the cache data is not lost
3.Pages load very fast from the first request
4.The time to scale is reduced with an additional web server.
Is it easy to switch to distributed output cache?
The distributed output cache is not available as an add-on or any other format. It is in fact a fully supported out of the box feature and takes a few seconds to configure on Sitefinity CMS.
While selecting your cache provider, you can choose between industry recognized data storage options like Memchached and Redis. In case you are using Amazon services with Sitefinity, you will see DynamoDB listed in the other supported distributed cache storages.
Each of the above options has its own benefits and so you can always pick the best solution that suits your business needs. All you need to do is to configure your provider so that Sitefinity CMS connects to the distributed cache store and starts working.
Using distributed cache in Sitefinity enhances the overall startup performance by about 200 times and also warms up a cold start when the pages are not yet compiled. The result helps to improve high availability and improved scalability together with a better browsing experience.
Also Read: How Sitefinity Successfully Tackles Security Vulnerabilities?
