Last updated Nov 11, 2024

Overview

Forge provides hosted storage capabilities that let you store data in your app installation. These storage capabilities are classified as either persistent or cache (currently in EAP).

Each installation of your app is subject to the Storage API's quotas and limits. See Storage quotas and Storage limits for more details.

Persistent

Use this for long-term storage until you need to delete or overwrite the data. Forge provides the following persistent storage capabilities:

Key-value store: lets you store data in key-value pairs.
Custom Entity Store: lets you store data based on custom data structures specific to your app’s needs and query patterns.
Forge SQL (Preview): lets you provision dedicated SQL database instances for each customer installation. You can then use these instances to store interrelated and complex datasets as required by your app.

These capabilities encrypt and store data on disk, optimising them for durability and persistence at the expense of performance.

Data recovery for apps with hosted storage

When a customer reinstalls an app that uses Forge hosted storage, data from the previous installation is not automatically restored. Forge hosted storage retains data for 28 days after uninstallation.

To recover this data for a customer, app developers must:

Get customer consent to restore data.
Submit a recovery request within 21 days of uninstallation. This is to ensure the request is processed before the 28-day retention ends.

To request recovery, raise a bug ticket on Developer Support. Use Re-linking reinstallation data as the summary, and provide customer details, site ID, and installation IDs.

Cache (EAP)

Forge Cache is now available as part of Forge Early Access Program (EAP). To start testing this feature, sign up using this form.

Forge Cache is an experimental feature offered to selected users for testing and feedback purposes. This feature is unsupported and subject to change without notice. Do not use Forge Cache in apps that handle sensitive information and customer data.

For more details, see Forge EAP, Preview, and GA.

Use the Forge Cache to store data temporarily but with faster access speeds (as in, higher throughput and lower latency).

The Forge Cache stores data on memory, optimising it for performance at the expense of persistence. In addition, data stored in Forge Cache is not encrypted. This makes Forge Cache unsuitable for storing sensitive data.