Weave Code
Symfony Messenger Redis Laravel Package
krak/symfony-messenger-redis
Redis transport for Symfony Messenger, enabling asynchronous message dispatch and consumption through Redis. Integrates with Messenger’s transport system to support queue-based workflows in Symfony applications.
Symfony Messenger Redis Adapter
Frequently asked questions about Symfony Messenger Redis
- Can I use krak/symfony-messenger-redis with Laravel queues?
- No, not directly. The package implements Symfony Messenger's TransportInterface, which Laravel's Illuminate\Queue worker, dispatcher, and job lifecycle do not understand. Using it means running a second messaging substrate alongside Laravel queues for mail, broadcasting, notifications, and dispatch() calls. For most Laravel applications the built-in Redis queue driver is the correct choice.
- How do I install krak/symfony-messenger-redis in a Laravel application?
- You can require it with Composer, but there is no Laravel service provider, config stub, or facade. You would have to bridge Symfony's ContainerInterface to Laravel's container, register the transport in Messenger config, write a custom consume command to replace queue:work, and wire handler discovery, serialization, and retry/failure transports yourself. That is a multi-week integration spike, not an afternoon.
- Which Symfony versions does krak/symfony-messenger-redis support?
- Version 0.1.8 adds support for Symfony 5, which points the compatibility ceiling at an end-of-life Symfony major rather than Symfony 7.x. The changelog does not disclose the exact constraint, so read composer.json directly. Either the range is ^5.x only, a hard conflict with modern Laravel, or it was widened to ^5.4|^6.x, which still falls short of 7.x.
- Is krak/symfony-messenger-redis compatible with Laravel 11 or Laravel 12?
- There is no documented Laravel path and no Laravel integration surface in v0.1.8. Laravel 11 and 12 depend on Symfony 6.4 and 7.x components, while this package's declared range appears anchored to Symfony 5.x. Unless composer.json proves a 7.x-compatible constraint, expect a Composer conflict. Even if it resolves, all framework glue remains your responsibility.
- Does krak/symfony-messenger-redis use Redis Streams or simple list operations?
- The overview claims native Redis Streams with consumer groups, but the release notes do not confirm whether the transport uses XADD/XREADGROUP or LPUSH/BRPOP. That distinction determines at-least-once delivery, message acknowledgement, pending-entry handling, and multi-consumer safety. List-based transports can silently lose messages under concurrent consumers, so verify it from source before relying on it.
- How does krak/symfony-messenger-redis compare to Laravel's built-in Redis queue driver?
- Laravel ships a first-class Redis queue driver backed by Illuminate\Queue and integrated with queue:work, failed_jobs, events, batching, and Horizon. This package is the Redis transport shim underneath Symfony Messenger, and Messenger's differentiators such as envelope middleware, per-bus routing, and handler-based dispatch are Symfony component features, not features of this package. Adopting it buys you a capability Laravel already provides as a config flag, at significant architectural cost.
- Is krak/symfony-messenger-redis production-ready and actively maintained?
- It is a v0.1.x package with a bus factor of one and near-zero adoption, with no dependents and no evidence of production use. No downstream pressure exists to fix bugs, so effectively you adopt a fork you maintain. The MIT license is clean and remains the one low-risk dimension.
- Does krak/symfony-messenger-redis support retries and failed message handling?
- The overview states compatibility with Symfony retry and failure transports. That is Messenger's own retry strategy and failure transport mechanism, not Laravel's failed_jobs table or queue:failed commands. You would configure and operate Messenger retry semantics separately, and you should confirm how they behave with Redis Streams pending entries in your setup.
- How do I test messages sent through krak/symfony-messenger-redis in Laravel?
- There are no Laravel testing helpers for this package: no facade, no Queue::fake() integration, and no documented test path. You would test Symfony Messenger transport behavior directly, typically against a real Redis instance or an in-memory Messenger transport. Expect to build your own harness around handler discovery and serialization.
- What license does krak/symfony-messenger-redis use and what are the alternatives?
- The package is MIT licensed. For Laravel applications the practical alternative is the native Redis queue driver with Horizon, which already provides reliable async processing with first-class framework integration. If you are on Symfony rather than Laravel, Symfony Messenger's official Redis transport is the maintained path, and for raw Streams semantics you can implement XADD/XREADGROUP directly.
Weaver
How can I help you explore Laravel packages today?