Weave Code
Redis Messenger Laravel Package
symfony/redis-messenger
Redis transport integration for Symfony Messenger, enabling queueing and async message handling backed by Redis. Part of the Symfony ecosystem, with links to contributing, issue reporting, and pull requests in the main Symfony repository.
Symfony Redis extension Messenger Bridge
Frequently asked questions about Redis Messenger
- Can I use symfony/redis-messenger directly in a Laravel project without Symfony Messenger?
- No, this package is a Symfony-specific extension. You’d need to integrate Symfony Messenger as a standalone component or build a custom Laravel Queue adapter to bridge the two. The Redis transport itself won’t work without Symfony’s core Messenger system.
- What Laravel versions are compatible with symfony/redis-messenger?
- Laravel 10+ is compatible, but the package itself is Symfony-focused. You’ll need to manually bridge Symfony Messenger into Laravel’s queue system or use it as a standalone library. No native Laravel integration exists.
- How do I configure Redis listable capabilities (e.g., BRPOPLPUSH-like operations) in Laravel?
- This feature is part of Symfony Messenger’s Redis transport and requires Redis 6.2+. In Laravel, you’d need to configure Symfony Messenger separately (e.g., via `MessengerTransportFactory`) and ensure your Redis client (ext-redis or predis) supports list operations. No direct Laravel config exists.
- Does symfony/redis-messenger support Laravel’s queue middleware or delayed jobs?
- No, this package doesn’t natively support Laravel’s queue middleware or delayed jobs. Symfony Messenger uses its own middleware system (stamps), and delayed jobs require custom implementation. For Laravel’s delayed queues, consider alternatives like `laravel-queue-redis` or `symfony/messenger` with a custom adapter.
- What’s the performance impact of using Symfony Messenger with Redis in Laravel?
- Performance depends on your setup. Symfony Messenger adds serialization overhead (JSON/PHP) compared to Laravel’s simpler approach. Redis listable capabilities may improve debugging but don’t resolve connection pooling or serialization bottlenecks. Benchmark with your workload.
- Can I migrate from Laravel’s default Redis queue to symfony/redis-messenger without downtime?
- Yes, but it requires dual implementations. Start by running non-critical jobs (e.g., analytics) through Symfony Messenger while keeping core queues in Laravel. Use Redis namespaces to isolate the two systems. The new listable features may help debug failed messages during migration.
- How do I handle message retries or failures in Laravel with symfony/redis-messenger?
- Symfony Messenger handles retries via its retry stack, but Laravel’s queue system won’t automatically integrate this. You’d need to build a custom Laravel command to consume messages via `symfony/messenger` or use Symfony’s `messenger:consume` CLI tool. Failed messages can be inspected using Redis list operations.
- Is symfony/redis-messenger suitable for high-throughput event-driven workflows like CQRS or sagas?
- Yes, it’s a strong fit for complex workflows. Symfony Messenger’s routing and middleware stacks excel in event-driven architectures, while Redis listable capabilities improve visibility for debugging sagas or CQRS commands. However, you’ll need to bridge it into Laravel manually.
- What Redis version is required, and how does it affect Laravel compatibility?
- Redis 6.2+ is required for listable capabilities. This aligns with modern Laravel setups (Laravel 10+ typically uses Redis 6+). If your Laravel project uses an older Redis version, you’ll need to upgrade or avoid the listable features.
- Are there alternatives to symfony/redis-messenger for Laravel Redis queues?
- Yes, for pure Laravel setups, consider `laravel-queue-redis` (native Laravel integration) or `spatie/laravel-queue-redis` for advanced features. If you need Symfony’s event-driven capabilities, `symfony/messenger` with a custom Laravel bridge is the closest alternative.
Weaver
How can I help you explore Laravel packages today?