Caching Overview
  • 18 Oct 2021
  • 1 Minute to read
  • Dark
    Light
  This documentation version is deprecated, please click here for the latest version.

Caching Overview

  • Dark
    Light

Article summary

Overview 

In terms of Computing and Decisions, Data Caching describes when a copy of data is temporarily stored in a designated location known as a Data Cache. This information is stored within a Cache rather than the typical System file storage for ease of access, and for frequent use. 

In Decisions, Designers leverage the power of the Flow Engine as well as the Designer Studio to interact with a Data Cache. This allows users to achieve Data Caching through two primary levels; Bespoke and Outcome.

The following document defines these primary levels Caching Levels and acts as a hub to further Caching documentation.


Bespoke Caching

As the name suggests, Bespoke Caching is a type of Data Caching that is designed to cater more specifically to the user's needs. Bespoke Data Caches are managed with intent in that they utilize steps and methodologies to put add data Items to a Cache when the user wishes/needs to. This is achieved through a data save and retrieval pattern that intentionally utilizes the cache.

In order to more purposefully save information to the Cache and ensure that the right information is retrieved, data is stored and fetched using a Key, via an Input on the Put In Cache and Get From Cache Flow steps. Further, additional steps exist that allow users to clear or manage their Data Cache from the Flow Designer

Additional Information
For further information on Bespoke Caching and Cache steps, see Cache Fetch Flow Behavior.


Outcome Caching

The other style of Caching is Outcome Caching. Outcome Caching is a type of Caching that is established and setup on the Outcome paths of a step or multiple steps.
Upon saving data to the Cache, the information is stored for a set period of time via the user-defined Cache Timespan Property that appears when a Cache Outcome is established on a step. 

This type of Caching is beneficial to instances that require a quick fetch or for customers that simply want a copy of a Flow's Outcome that can be quickly accessed. 


Cache Definitions

In order to help users better customize the storage behaviors of their Data Caches, users may utilize System Admin Cache Settings to establish a Cache Definition.

Cache Definitions allow users to do things such as control the amount of Time that Items remain in a specific Cache, the size of the data stored within the Cache, the location of a Cache itself, etc. 

 Additionally, Cache Definitions allow users to control different aspects of certain Cache Types, such as Database, File, or FileDirectory Caches. 

Additional Information 
For more information on how to use Cache Definitions, see:



Was this article helpful?

What's Next