This article describes the technical details of how caching works in Atlas. If you simply want to know how to clear your cache please see here: How to completely clear Atlas caches
In this article:
Browser caching
Atlas is using the browser's Session Storage and Local Storage to cache data on each device.
- Session Storage data persists until the browser application is closed.
- Local Storage persists even after the browser is closed and, in fact, has no expiration time by default.
Atlas is using a custom implementation to manage browser's Local Storage by adding an expiration token to the storage items. If the storage item goes beyond the expiration date, it is then renewed. - File Storage stores file assets such as images, styling sheets or JavaScript files. It has variable expiration that can be set for some assets, it depends on the operating system and browser policies of the browser client used to access the web (cannot be controlled by Atlas).
Local Storage keys
Header/Footer
| Storage key | Description | Expiration |
|
cp_atlas_hasbackground
|
Prevents header theme flicker when there is a background image
|
7 days |
|
cp_atlas_feedback_{site_name}
|
Cache feedback subjects associated with current site
|
7 days |
Launchpad
| Storage key | Description | Expiration |
|
cp_atlas_launchpad_{configurationSiteUrl}
|
Caching launchpad items
|
7 days |
Navigation
| Storage key | Description | Expiration |
|
cp_atlas_navigationconfig
|
Cache the items in the navigation configuration list
|
365 days*
|
|
cp_atlas_groups
|
Cache all users/groups with membership with configuration site
|
365 days* |
|
cp_atlas_termset_{termset_id}
|
Prevents loading the navigation on each render
|
365 days*
|
|
cp_atlas_templatemanagement_permissions
|
Cache the user's permission to access Connex Studio
|
7 days
|
|
cp_atlas_languagemanagement_permissions
|
Cache the user's permission to access Language settings
|
7 days
|
* Initially planned to be updated to 7 days in Atlas 4.0 release, this change will take effect from Atlas 4.1 release.
Footer
| Storage key | Description | Expiration |
|
isCollapsed
|
For collapsing the footer
|
never |
|
cp_atlas_footerlinks_{site_name}
|
Cache footer links
|
7 days |
|
cp_atlas_copyright_{site_name}
|
Cache copyright message
|
7 days |
|
cp_atlas_social_{site_name}
|
Cache social links
|
7 days |
|
Storage key |
Description |
Expiration |
|
cp_atlas_addit_permissions
|
Workspace listing permissions when using configuration file
|
7 days |
Languages
| Storage key | Description | Expiration |
|
cp_atlas_languages_available_{user_name}
|
Cache available languages for the user
|
7 days |
|
cp_atlas_languages_supported_{user_name}
|
Cache Atlas supported languages
|
7 days |
Connex Studio
| Storage key | Description | Expiration |
|
cp_atlas_templates_tpls_supported_{url}_{user}
|
Cache the request to disable the 'New Workspace Template' form
|
7 days |
ConneX
| Storage key | Description | Expiration |
|
cp_atlas_connect_tpls_permissions
|
Cache the request to hide the 'New Workspace' button
|
7 days |
|
cp_atlas_connect_tplCategories
|
Cache workspace template names
|
7 days |
SharePoint Tenant Properties
Session Storage keys
My Links
| Storage key | Description | Expiration |
|
cp_atlas_{user}_myLinks
|
Cache users 'My Links' items from profile property
|
session |
|
cp_atlas_{user}_suggestedLinks
|
Cache suggested links from list
|
session |
Server Caching
Azure Cache for Redis provides an in-memory data store based on the Redis software. Redis improves the performance and scalability of an application that uses backend data stores heavily. It's able to process large volumes of application requests by keeping frequently accessed data in the server memory, which can be written to and read from quickly. Redis brings a critical low-latency and high-throughput data storage solution to modern applications.
As part of Atlas infrastructure, Azure Cache for Redis is deployed. There are a few components/cases in the solution that are using it, check the below table to get more information.
| Component | Description | Time |
| User authentication token | Atlas is caching the user authentication token to avoid unnecessary requests. | 1 hour |
| Add it JSON files | Some JSON configuration files used by Add It are cached | 24 hours |
| ConneX filters | ConneX list of filters in ConneX web part configuration (it doesn't affect end-users browsing pages) | No expiration |
| User membership | Groups membership is cached, and this affects ConneX Dashboard groups visibility | 1 hour |
| Sharing capabilities | Sharing options are cached at tenant and site collection level | 30 minutes |
Comments
0 comments
Please sign in to leave a comment.