---
schema_version: "1"
id: 2de1d443110dcefd4479c0e3a95e320a30e6dba1a1b2f2ad7d49e0beb9b307fd
title: Caching
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/mule-runtime/latest/tuning-caching.md
canonical_url: https://docs.mulesoft.com/mule-runtime/latest/tuning-caching
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 7b154256e18f01d59803490b628306c81f6dedb25f52e5fb9ff3bc300ddc70ed
description: MuleSoft Documentation Site
release: "4.13"
latest: true
---
---
product: Mule Runtime
version: 4.13
is-latest-version: true
---

# 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/latest/cache-scope)

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