Boosting Shopware Performance: A Deep Dive into Prioritized Redis Transports

Photo by Acton Crawford on Unsplash

When utilizing the Shopware asynchronous system, managing a large volume of messages in the queue becomes crucial, especially when some messages take precedence over others. To address this, Shopware allows you to prioritize messages by creating multiple Redis transport types, ensuring specific messages are executed before others.

Setting Priorities

Let’s consider a scenario where you want to establish three priority levels:

1. High Priority
2. Medium Priority
3. Low Priority

To consume messages in this order, use the following command:

bin/console messenger:consume high_priority medium_priority low_priority

This command instructs the consumer to process messages from high_priority first, followed by medium_priority, and then low_priority. You can expand this hierarchy by adding more transports.

Configuring Transports

Define transports in the Shopware .yaml configuration file:

framework:
    messenger:
        transports:
            high_priority:
                dsn: '%env(MESSENGER_TRANSPORT_DSN)%'
                options:
                    stream: high_priority
            medium_priority:
                dsn: '%env(MESSENGER_TRANSPORT_DSN)%'
                options:
                    stream: medium_priority
            low_priority:
                dsn: '%env(MESSENGER_TRANSPORT_DSN)%'
                options:
                    stream: low_priority

Ensure to set the MESSENGER_TRANSPORT_DSN in the .env file for Redis transport to function.

Routing Messages

With transports defined, configure routes for messages:

framework:
  messenger:
    routing:
      'Shopware\Core\Content\ImportExport\ScheduledTask\CleanupImportExportFileTask': high_priority
      'Shopware\Core\Framework\App\ScheduledTask\DeleteCascadeAppsTask': medium_priority
      'Shopware\Core\Content\ImportExport\Message\ImportExportMessage': low_priority