Configure cache frontends and types

A cache frontend is an interface between Commerce cache types and the cache storage backend. You can define multiple frontends, each with different backend settings, and then assign specific cache types to each frontend.

Use this relationship to decide where each cache type stores data:

cache type -> cache frontend -> cache backend

This is useful when you want to use different cache backends or configurations for different types of cached data. For example, you might assign the full_page cache type to a page_cache frontend that uses a dedicated Valkey database, while other cache types use the default frontend.

Use the default frontend

Commerce provides a default cache frontend that works for all cache types. It extends Zend_Cache_Core by implementing the Magento\Framework\Cache\Core frontend cache.

In most cases, you do not need to customize the frontend. You only need to configure the backend. See Cache backend options.

Define a custom cache frontend

The following steps walk through associating a cache frontend with a cache type.

Step 1: Define a cache frontend and assign cache types

To define a custom cache frontend, add the configuration to app/etc/env.php (which overrides di.xml):

'cache' => [
    'frontend' => [
        '<unique frontend id>' => [
             <cache options>
        ],
    ],
    'type' => [
         <cache type 1> => [
             'frontend' => '<unique frontend id>'
        ],
         <cache type 2> => [
             'frontend' => '<unique frontend id>'
        ],
    ],
],

Where:

Step 2: Configure frontend and backend options

You can specify frontend and backend cache configuration options in env.php or di.xml. This task is optional. If you do not specify options, Commerce uses the default frontend and backend settings.

env.php example:

'frontend' => <frontend_type>,
'frontend_options' => [
    <frontend_option> => <frontend_option_value>,
    ...
],
'backend' => <backend_type>,
'backend_options' => [
    <backend_option> => <backend_option_value>,
    ...
],

Where:

See the Laminas documentation for Zend-based options. For Symfony Cache configuration, see the Redis and Valkey articles in this documentation.