---
title: "Caching Systems"
slug: "caching-systems"
updated: 2024-12-11T13:38:03Z
published: 2024-12-11T13:38:03Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.decisions.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Caching Systems

Below are diagrams of caching systems within Decisions.

---

## Current Version Diagram

## ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/v8.3%20current%20best%20v2(1)12-11-24.png)

As of v8.3, and going into the current version of v9, caching is handled by a Redis server. Local cache is still available, but it is not the default location. Redis only holds object ids so all servers in a cluster can know when something has been changed. Flow data is not cached in Redis.

## Prior Versions

## v7 and Below (Multi-server)

![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/v7%20best%202.0(1).png)

The Decisions application server has a local cache that is different than the database. Using the various cache Steps affect this cache. However if there are multiple servers in a cluster, each of those servers has its own cache. Each server keeps separate versions of objects in cache local to them. Those servers send events to each other to clear and refresh those objects from cache.

## v8 and Below (Single Server)

![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/v8.2%20best%20v2(2).png)

The Decisions application server has a local cache that is different than the database. Using the various cache Steps affect this cache.

## 

##