Configure cache frontends and types

A cache frontend connects Commerce cache types to cache storage. You can define multiple frontends and assign specific cache types to each frontend.

Use the following relationship to determine where a cache type stores its data:

cache type → cache frontend → cache backend

For an overview of the Commerce caching architecture, see Caching overview and configuration options.

Use the default frontend

Commerce provides a default frontend that can be used by all cache types.

In most cases, you do not need to define a custom frontend. If all cache types can use the same backend and backend options, use the default frontend and configure its backend. See Cache backend options for backend-specific configuration.

For Adobe Commerce versions before 2.4.9, the default frontend uses the legacy Zend-based cache implementation. The Magento\Framework\Cache\Core frontend extends Zend_Cache_Core. Adobe Commerce 2.4.9 and later use the modern Symfony implementation. See Cache backend options for version-specific guidance.

Define a custom frontend

Use a custom cache frontend when one or more cache types need backend settings that differ from those of the default frontend.

For on-premises deployments, define the frontend in app/etc/env.php. Then assign one or more cache types to it:

'cache' => [
    'frontend' => [
        '<frontend-id>' => [
            'backend' => '<backend-type>',
            'backend_options' => [
                // Backend-specific options
            ],
        ],
    ],
    'type' => [
        '<cache-type-id>' => [
            'frontend' => '<frontend-id>',
        ],
    ],
],

Where:

For backend types, supported options, and release-specific configuration examples, see Cache backend options.

Assign a cache type to a frontend

The type configuration maps a cache type to a frontend:

'type' => [
    'full_page' => [
        'frontend' => 'page_cache',
    ],
],

Where: