Use and configure Redis as a key-value storage

Edit on GitHub

This document describes how Redis is used within Spryker. The current functionality can be extended according to your needs.

About Redis

Redis is a key-value data storage, and for the values, it supports a large collection of data structures, such as strings, hashes, lists, or sets.

The following table shows how translations are stored:

de_DE Warenkorb
en_US Cart

The values for the translations are stored as strings, but more complex types, such as product information, are stored in JSON format.

The key name follows this format: kv:{store}{locale}{resource-type}{key}.

Redis data storage

The data stored in Redis includes the following:

  • URL mappings
  • Product details
  • Product category details
  • Stock information
  • Translations
  • CMS pages and blocks

How data is loaded into Redis

Data is loaded in Redis through a dedicated console command. This console command is executed when the application is initially installed, but you can execute it also from the command line:

console sync:data

For more information about how the Publish and Synchronization process works and how to extend them, see Publish and Synchronization.

How data is kept in sync

Of course, the data stored in the SQL database is the subject of change; data can be updated or deleted, or new entries can be added. The data currently stored in Redis is a snapshot of the data in the SQL database from when the last update was run. The key-value data storage must be kept in sync with the data persisted in the SQL database. To achieve this, you must set up a cron job that runs on a specified time interval and updates the key-value data storage.

For more information, see Cronjob scheduling.

Also, you need to find out which data has changed because you don’t want to completely reload the content stored in Redis. The Touch module takes care of marking the items that were updated in the meantime.


Every time you make an update delete insert request for data that is also stored in Redis, you must touch that data so that it’s marked for export when the next storage update task runs.

Browse the data from Redis

To browse the data that’s stored in Redis, you need to set up Redis Desktop Manager (RDS). Install RDS and then configure it as shown on the following screenshot.

Find the current Redis Port in config/Shared/config_default-development.php. Redis setup

Make sure that your virtual machine is up and running.

Use the data stored in Redis

This section describes how you can use data stored in Redis.


To show content translated according to the selected locale, you can use the translation extension from the twig file; you need to specify the key name and pipe it to the trans extension. When rendered, the value corresponding to the selected locale for that key is be shown—for example:

<button>{{ "page.detail.add-to-cart"|trans }}</button>

The caption for the button depends on the selected locale:

de_DE In den Warenkorb.
en_US Add to Cart .

Access the Redis data storage

Redis data storage is accessed using StorageClient.

The StorageClient can be obtained as an external dependency in the client layer for Yves. In the dependency provider of the client layer from your module, add the StorageClient dependency as in the following example:



     * @param \Spryker\Client\Kernel\Container $container
     * @return \Spryker\Client\Kernel\Container
    public function provideServiceLayerDependencies(Container $container)
        $container[static::CLIENT_STORAGE] = function (Container $container) {
            return $container->getLocator()->storage()->client();

        return $container;

Add a method that retrieves an instance of the key-value storage in the factory of the Client layer of your module:


     * @return \Spryker\Client\Storage\StorageClientInterface
    public function getStorageClient()
        return $this->getProvidedDependency(MyBundleDependencyProvider::CLIENT_STORAGE);

To retrieve the value for a given key, you can use the get($key) operation from StorageClient.

$storedValue = $this->storageClient->get($myKey);

Use a password for accessing Redis

You can define a password to restrict access to Redis. Spryker provides the \Spryker\Shared\Storage\StorageConstants::STORAGE_REDIS_PASSWORD configuration option that can be used to configure the Redis client to authenticate Spryker.

To activate it, specify the redis protocol for \Spryker\Shared\Storage\StorageConstants::STORAGE_REDIS_SCHEME (the Spryker Demo Shop uses tcp by default).

Use and configure Redis cache

To boost the performance in Spryker even more, we have built a caching mechanism to cache all used Redis keys on any page in the shop.

A page in the shop often contains many different Redis entries for various content and information it has. For example, a product title, a description, and attributes on a product details page. All of this data is stored in many Redis key-value pairs. To retrieve the data for a page, multiple Redis GET requests are needed, so if a page uses 100 Redis key-value pairs, then 100 Redis GET requests are needed to retrieve the data.

To optimize the data retrieval from Redis, we designed an algorithm to store all the needed keys in a given page in the shop in only one Redis key and then use one Redis MGET (multi-get) request to retrieve all the data. Using the implemented algorithm, only two requests to Redis are needed for most of the pages: one GET request to get the cache entry and one MGET requests to get all the data.

The Redis cache for a page is basically a key-value pair. The key of the cache is the prefix StorageClient_ followed by the URL of the page, while the value of the cache is simply a list of all Redis keys used on the cached page.

When accessing a new page, the algorithm checks if a cache for it is already built. If yes, the page uses or refreshes the cache if needed; otherwise, the algorithm builds a new cache.

Spryker provides three caching strategies to build the list of the keys in the cache entry:

  • Replacement strategy. This strategy overwrites the list of the keys in a cache with a new one every time a cached page is accessed. This strategy is useful with static pages where the list of keys for these does not change often. This is a default strategy when a strategy is not specified.
  • Incremental strategy. This strategy increments the list of keys inside the cache until the limit is exceeded. The default limit is 1000 keys. The incremental strategy is useful with a page that uses configurators—for example, variants where the cache stores all the different combinations.
  • Inactive strategy. This strategy deactivates the cache for a specified page.

All the cache entries have a default TTL of one day. The cache is removed after one day, and a new one is generated for different pages when accessing them.

How to add and configure the cache

The cache works on the controller level. This means that you can define what strategy a controller uses for all of its actions. By default, the cache is active and uses the Replace strategy.

To specify what cache strategy a controller uses, only two steps are required:

  1. Use the Yves AbstractController.
use Pyz\Yves\Application\Controller\AbstractController;
  1. Define the cache strategy by assigning the value to the STORAGE_CACHE_STRATEGY constant—for example, an incremental strategy is defined in the following code.

That is it!

To change the default configuration values for the TTL and the key-size limit for the incremental strategy, you can extend StorageConfig and override the following methods:

  • To change the limit size for the incremental strategy, override getStorageCacheIncrementalStrategyKeySizeLimit.
  • To change the TTL for the cache, override getStorageCacheTtl.