What are the three types of cache in Confluence?

What are the three types of cache in Confluence?

• A. Local, Distributed, Hybrid
• B. Global, Local, Remote
• C. Client, Server, Proxy
• D. In-Memory, Disk, Network

Answer: (A)

Confluence uses a layered caching approach in a clustered environment, consisting of a node-local cache, a cluster-wide distributed cache, and an optional hybrid cache that combines both strategies for better balance of speed and coherence. The node-local cache lives on each application node and stores frequently accessed data there for rapid access. This boosts performance for requests that hit that particular node, but the cached data isn’t automatically shared with other nodes. The distributed cache is shared across all nodes in the cluster, ensuring data consistency and reducing repeated data fetches across the entire cluster. It helps keep things like permissions or shared content coherent no matter which node serves a request. The hybrid cache leverages both approaches, using the local cache for fast, node-local hits while still using the distributed cache to maintain cross-node consistency and optimize overall memory usage. Other options don’t align with how Confluence describes its caching layers. Terms like global/remote, or architectures such as client/server/proxy, or generic in-memory/disk/network categorizations don’t reflect the official Confluence caching model.

Confluence uses a layered caching approach in a clustered environment, consisting of a node-local cache, a cluster-wide distributed cache, and an optional hybrid cache that combines both strategies for better balance of speed and coherence.

The node-local cache lives on each application node and stores frequently accessed data there for rapid access. This boosts performance for requests that hit that particular node, but the cached data isn’t automatically shared with other nodes. The distributed cache is shared across all nodes in the cluster, ensuring data consistency and reducing repeated data fetches across the entire cluster. It helps keep things like permissions or shared content coherent no matter which node serves a request. The hybrid cache leverages both approaches, using the local cache for fast, node-local hits while still using the distributed cache to maintain cross-node consistency and optimize overall memory usage.

Other options don’t align with how Confluence describes its caching layers. Terms like global/remote, or architectures such as client/server/proxy, or generic in-memory/disk/network categorizations don’t reflect the official Confluence caching model.