---
schema_version: "1"
id: 5c21517c182a06c2da8a9a6287dd8e3c597c6fade05a4bc042e885c7ece2a41b
title: Caching
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/mule-runtime/4.11/tuning-caching.md
canonical_url: https://docs.mulesoft.com/mule-runtime/4.11/tuning-caching
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 19534cee1507b84d9e2697ea7e008f173d7db05860432ecd0bd77feaf53a26cb
description: MuleSoft Documentation Site
release: "4.11"
latest: false
---
---
product: Mule Runtime
version: 4.11
---

# Caching

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Identifying key aspects of your data such as when to use cache and which cache strategy to follow,
helps you to improve processing performance:

- Is the data frequently called, with often repeated results?

- Can you afford eventual consistency between the data source and the cache information?  
  At least for a while until cache refreshes.

Mule runtime engine (Mule) offers customizable strategies, such as the Cache scope and the HTTP
Caching API Gateway policy, to enable cache according to your needs. Both strategies help
applications that constantly request the same data by reducing the processing load, especially
network interactions with a remote host.

For Cache scope, consider a production environment in which the default in-memory caching consumes
all of your memory resources. To avoid this consumption, use an object-store caching configuration
with well-defined storage and expiry policies.

## See Also

- [Cache Scope](https://docs.mulesoft.com/mule-runtime/4.11/cache-scope)

- [HTTP Caching](https://docs.mulesoft.com/gateway/latest/policies-included-http-caching)