Symfony 4.4 Messenger - Different middleware on the consumer and producer side

AddConsumerBusNameStampMiddleware.php

<?php

namespace App\Messenger\Middleware;

use Symfony\Component\Messenger\Middleware\MiddlewareInterface;
use Symfony\Component\Messenger\Middleware\StackInterface;
use Symfony\Component\Messenger\Envelope;
use Symfony\Component\Messenger\Stamp\BusNameStamp;

# This is sort of a workaround, read more here:
# https://github.com/symfony/symfony/issues/32436#issuecomment-530565499

final class AddConsumerBusNameStampMiddleware implements MiddlewareInterface
{
    public function handle(Envelope $envelope, StackInterface $stack): Envelope
    {
        $envelope = $envelope->with(new BusNameStamp('consumer.bus'));

        return $stack->next()->handle($envelope, $stack);
    }
}

messenger.yaml

framework:
    messenger:
        # ...
        
        default_bus: command.bus
        buses:
            command.bus:
                # Will be run in the producer context (message sender)
                middleware:
                    # Override the bus name that should receive and handle messages (bus name: consumer.bus)
                    - App\Messenger\Middleware\AddConsumerBusNameStampMiddleware

            consumer.bus:
                # Will be run in the consumer context (message receiver -> worker)
                middleware:
                    - doctrine_ping_connection
                    - doctrine_transaction