The EPiServer API does a lot of caching in the background to help improve your website's performance. This is one of the main reasons Episerver API works so quickly. It also makes the developers' lives easier as it is normally one less thing to worry about.
When we build large scale applications that get large numbers of traffic, it is important to understand how and when EPiServer caches data to ensure your website runs in the most efficient manner.
The object cache is built on top of the ASP.NET runtime cache. As mentioned in Why are Pages and Blocks Returned From The Episerver API Read-Only?. Th API only returns read-only objects for better performance. This mechanism enhances scalability, as multiple threads can reading the same data.
<applicationSettings pageCacheSlidingExpiration="1:00:0" httpCacheability="Public" pageValidateTemplate="false" uiShowGlobalizationUserInterface="true" urlRebaseKind="ToRootRelative" uiUrl="~/epiui/edit/CMS/" utilUrl="~/util/" uiEditorCssPaths="~/static/tinymce/css/editor.css" />
Software Architect, Programmer and Technologist Jon Jones is founder and CEO of London-based tech firm Digital Prompt. He has been working in the field for nearly a decade, specializing in new technologies and technical solution research in the web business. A passionate blogger by heart , speaker & consultant from England.. always on the hunt for the next challenge