---
schema_version: "1"
id: 845342dfcf94856b882f6cf74ae127838a62ba001b1e0332f37bb192d1997567
title: Manage Application Data Storage with Object Stores
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/cloudhub/managing-application-data-with-object-stores.md
canonical_url: https://docs.mulesoft.com/cloudhub/managing-application-data-with-object-stores
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 1ddc88f59d736c45daf3e05a21054c2e376a1c8cda1674ba71522cf88a5686e8
description: MuleSoft Documentation Site
latest: true
---
---
product: CloudHub
---

# Manage Application Data Storage with Object Stores

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

CloudHub includes application data storage for each application it manages. This data is accessible
through the Mule object store and Object Store v2 functionality.

Object stores can be used to store anything, but two of the main uses are:

- Storing synchronization state: Your application might need to keep track of the last synchronized
  record, so that the next time the application synchronizes, it can resume where it left off.

- OAuth tokens: OAuth-enabled connectors can store tokens inside an object store with a few lines of
  configuration code.

Your application can also store custom integration data as well, within the limits outlined below.

> [!NOTE]
>
> - Object stores are handled in the way described in this document only for applications deployed
>   to CloudHub workers. For applications that you deploy via the Runtime Manager to local servers,
>   you must handle the storage of data in your own repository. See
>   [Deployment Options](https://docs.mulesoft.com/runtime-manager/deployment-strategies) for more details.
>
> - All data in Object Store v1 is handled by servers in the **US-East zone**, regardless of what
>   zone your application is deployed to. This may impact performance.
>
> - [Object Store v2](https://docs.mulesoft.com/object-store/osv2-faq) expands the number of cloud object store regions and
>   object store capabilities.

> [!IMPORTANT] CloudHub clears local disk storage when an app restarts or redeploys. Because Object
> Store v1 writes to local disk, data isn’t preserved, even if you configure `persistent="true"`.
>
> In Anypoint Studio and standalone Mule runtimes, the local file system persists, so object stores
> retain data across restarts. CloudHub workers use volatile disk storage.
>
> To persist data across restarts, use [Object Store v2](https://docs.mulesoft.com/object-store/) to store data externally.

## Store and Retrieve Data

To work with application data inside a Mule flow, use the Object Store connector. The connector
provides operations to store, retrieve, list, and remove data from a Runtime Manager Object Store.
The Object Store connector works with both Object Store v1 and Object Store v2.

### Retrieve OAuth Data

For information on how to retrieve OAuth tokens, see [OAuth Module](https://docs.mulesoft.com/oauth-module/latest/).

## View Application Data

To view application data in the object store, click your application name in Runtime Manager and
then click **Manage Application** > **Object Store**:

![Object Store in the left navigation pane](/mulesoft/current/en-us/cloudhub/_images/cloudhub-object-store-rtm.png)

Figure 1. The arrow shows **Object Store** in the left navigation pane.

If the application uses Object Store v1, the label is **Application Data**.

> [!TIP] To make properties secure so that they’re not visible using the Runtime Manager UI or
> anywhere else, see [Safely Hide Application Properties](https://docs.mulesoft.com/cloudhub/secure-application-properties).

## Semantics and Storage Limits

Object Store v1 provides read-after-write consistency and the last write wins for updates.

Object Store v1 has a:

- Maximum of 100,000 keys per application

- 768 byte key size

- 1 MB value size

- 1 GB of data per application

Object Store v2:

- Unlimited number of keys per application

- Values can be up to 10 MB

- Trial level 10 TPS, premium level 100 TPS

- Keys persist for up to 30 days

- Available in [all commercially available CloudHub regions](https://docs.mulesoft.com/object-store/osv2-faq).

## Advanced Information

Internally, Mule has several different types of object stores. Runtime Manager provides Object Store
v2. These object stores are for runtime information about your application, such as those use cases
mentioned above. You can find this object store internally in the Mule Registry under the
'\_defaultUserObjectStore\` if you want to access it directly. The Object Store module and
connectors use this store to store all their data by default.

### See also

- [Object Store v1](https://docs.mulesoft.com/mule-runtime/latest/mule-object-stores)

- [Object Store v2](https://docs.mulesoft.com/object-store/)

- [Tutorial: Object Store v2](https://docs.mulesoft.com/object-store/osv2-tutorial)

- [Object Store Connector for Mule 4 in Anypoint Exchange](https://www.mulesoft.com/exchange/org.mule.connectors/mule-objectstore-connector/)