Create a Yii Messenger package based on the Symfony Messenger package

[klsoft-web]

The Symfony Messenger package is a robust, well-documented library for message queues.
The transport configuration has equivalents of the Yii Queue adapters.
Since the Yii3 console is based on the Symfony console, the Symfony Messenger commands can be integrated seamlessly.
This could be a good alternative to, or even a complete replacement for, the Yii Queue package.

These are the Symfony Messenger equivalents of the Yii Queue:

$queue->push ->  $bus->dispatch
Adapter -> Transport
./yii queue:listen [queueName] -> php bin/console messenger:consume receiver1

[rossaddison]

Claude's persepective: the Queue/transport parallel is a good observation, and it's true that yiisoft/yii-console already wraps symfony/console, so the ecosystem isn't allergic to Symfony components where it makes sense.
One thing worth separating out before this becomes a package, though: Symfony Messenger and yiisoft/queue aren't really equivalent in scope, so "Messenger as an alternative or replacement for Queue" undersells what Messenger actually is.
yiisoft/queue is a transport layer: push a job, an adapter moves it, a worker pops and runs it.
Symfony Messenger is a message bus: dispatch() goes through a middleware stack (validation, transaction wrapping, retry, etc.) to a handler, and async is just one middleware in that stack (SendMessageMiddleware routing to a transport). Sync command/event dispatch and async queuing share the same bus on purpose.
So a straight port would mean building the bus + middleware + handler-resolution machinery from scratch, not just relabeling push→dispatch and adapters→transports — that's a much bigger surface (envelopes, stamps, retry strategies, middleware composition) than Queue ever tried to cover, and duplicating Queue's existing adapters under it seems like wasted effort.
Two directions I'd find more promising than a from-scratch clone:
A thin bus abstraction on top of the existing yiisoft/queue adapters — get the dispatch/middleware ergonomics without reinventing transport code that already exists and is tested.
Scope it as sync-dispatch only (command bus / event bus, PSR-14-friendly) and explicitly punt on async to the existing Queue package, rather than trying to be both.
Either way, given Yii3's PSR-first, swap-any-component philosophy, I think the value-add here is the bus/middleware pattern itself, not re-deriving what transport abstraction already gives Symfony users. Curious what @samdark / @vjik think about scope before this turns into an RFC.

[klsoft-web]

Claude's persepective: the Queue/transport parallel is a good observation, and it's true that yiisoft/yii-console already wraps symfony/console, so the ecosystem isn't allergic to Symfony components where it makes sense. One thing worth separating out before this becomes a package, though: Symfony Messenger and yiisoft/queue aren't really equivalent in scope, so "Messenger as an alternative or replacement for Queue" undersells what Messenger actually is. yiisoft/queue is a transport layer: push a job, an adapter moves it, a worker pops and runs it. Symfony Messenger is a message bus: dispatch() goes through a middleware stack (validation, transaction wrapping, retry, etc.) to a handler, and async is just one middleware in that stack (SendMessageMiddleware routing to a transport). Sync command/event dispatch and async queuing share the same bus on purpose. So a straight port would mean building the bus + middleware + handler-resolution machinery from scratch, not just relabeling push→dispatch and adapters→transports — that's a much bigger surface (envelopes, stamps, retry strategies, middleware composition) than Queue ever tried to cover, and duplicating Queue's existing adapters under it seems like wasted effort. Two directions I'd find more promising than a from-scratch clone: A thin bus abstraction on top of the existing yiisoft/queue adapters — get the dispatch/middleware ergonomics without reinventing transport code that already exists and is tested. Scope it as sync-dispatch only (command bus / event bus, PSR-14-friendly) and explicitly punt on async to the existing Queue package, rather than trying to be both. Either way, given Yii3's PSR-first, swap-any-component philosophy, I think the value-add here is the bus/middleware pattern itself, not re-deriving what transport abstraction already gives Symfony users. Curious what @samdark / @vjik think about scope before this turns into an RFC.

We do not need to "building the bus + middleware + handler-resolution machinery from scratch" to use the Symfony Messenger in a Yii3 application.
The Yii Messenger package can be implemented with minimal effort. The following is an example configuration:

//vendor/yiisoft/messenger/config/params-console.php
use Symfony\Component\Messenger\Command\ConsumeMessagesCommand;

return [
    'yiisoft/yii-console' => [
        'commands' => [
            'messenger:consume' => ConsumeMessagesCommand::class,
        ]
    ]
];

[samdark]

@klsoft-web, it could be used directly if you want without any wrapper if I'm not mistaken. Btw., the queue is almost finished. Thanks again for your interfaces segregation idea.

@rossaddison I can run Claude myself :), and it hallucinated quite significantly about scope.

[klsoft-web]

@klsoft-web, it could be used directly if you want without any wrapper if I'm not mistaken. Btw., the queue is almost finished. Thanks again for your interfaces segregation idea.

@rossaddison I can run Claude myself :), and it hallucinated quite significantly about scope.

Yes, we can use the Symfony Messenger package directly.
The Yii Messenger package can integrate Symfony Messenger commands into the Yii3 console.

First add the 'messenger:consume' command to the Yii3 console.

//vendor/yiisoft/messenger/config/params-console.php
use Symfony\Component\Messenger\Command\ConsumeMessagesCommand;

return [
    'yiisoft/yii-console' => [
        'commands' => [
            'messenger:consume' => ConsumeMessagesCommand::class,
        ]
    ]
];

Then you can consume messages using the Yii3 console:
./yii messenger:consume reciver1 --bus=MyMessageBus

[samdark]

The Yii Messenger package can integrate Symfony Messenger commands into the Yii3 console.

I think it is better to describe it in something like a cookbook rather than creating another integration package.

[klsoft-web]

I ended up creating the klsoft/yii3-symfony-messenger package I had suggested.
The main advantage of using the package is that you don't have to write boilerplate configuration.

[vjik]

Can you create article for cookbook with this configuration and short description about Symfony Messenger usage with Yii3? It will be useful.

[klsoft-web]

Can you create article for cookbook with this configuration and short description about Symfony Messenger usage with Yii3? It will be useful.

I did it, but apparently it's no longer necessary.

[samdark]

Not "no longer necessary" but might be a bit conflicting with yiisoft/queue.