Weave Code
Queue Bundle Laravel Package
symfony-bundles/queue-bundle
Symfony Queue Bundle integrates queue-based messaging into Symfony applications. It offers configuration and services for dispatching jobs, running worker consumers, and connecting supported queue backends with Symfony's service container and console commands, enabling background and asynchronous pr...
Symfony Queue Bundle
Frequently asked questions about Queue Bundle
- What is symfony-bundles/queue-bundle?
- It is a Symfony bundle that integrates queue-based messaging into Symfony applications. It provides configuration and services for dispatching jobs, running worker consumers, and connecting supported queue backends to Symfony's service container and console commands. It is designed for a Symfony Kernel with bundles.php registration, tagged services, compiler passes, and a Symfony Console application, not for Laravel.
- Can I use symfony-bundles/queue-bundle in a Laravel application?
- There is no supported integration path. Laravel runs on the Illuminate container with service providers and an artisan command bus, and it has no bundle loader to register this package's services, configuration tree, and compiler passes. Forcing it to work means manually instantiating the bundle's container extension and maintaining a compatibility shim, and Laravel's Queue::fake() and other testing helpers would not cover it. The recommendation is not to integrate it into a Laravel application.
- Does symfony-bundles/queue-bundle support Laravel 10, 11, or 12?
- No. The last release was October 2017, targeting the PHP 5.6/7.0-7.1 and Symfony 2.x/3.x era, long before those Laravel versions. It expects to boot through a Symfony Kernel, which modern Laravel does not provide. Expect Composer resolution problems as well, since its pinned dependencies can force downgrades elsewhere in a modern Laravel or Symfony component tree.
- Is symfony-bundles/queue-bundle compatible with PHP 8?
- Almost certainly not. A 2017 codebase of this vintage typically relies on deprecated constructs, removed functions, and older type semantics that break under PHP 8.x. There is also no evidence of CI or testing against modern PHP releases. Any PHP 8 support would have to be patched into a fork that you own.
- How do I install symfony-bundles/queue-bundle?
- In a Symfony project you install it with Composer, register the bundle in your kernel or bundles.php, and configure its queue services and backend connection. Workers are then started through the bundle's Symfony Console command. In a Laravel application none of those registration steps exist, so a plain composer require is not enough to make the package usable.
- How do I run queue workers with symfony-bundles/queue-bundle?
- The bundle exposes consumer workers driven by Symfony Console commands inside a Symfony application. In Laravel you would instead use queue:work under Supervisor or systemd, or Horizon for Redis-backed queues, with retries, backoff, and failed-job handling built in. Running both models side by side creates a parallel queue subsystem that is hard to reason about and harder to hand over.
- Is symfony-bundles/queue-bundle still maintained?
- There is no evidence of active maintenance. The last release was October 2017, and there is no visible CI, security response process, or published support policy. The MIT license is fine, but the practical constraint is that any CVE or PHP-version breakage becomes yours to patch in a fork, with no upstream to fix it. At roughly 31 stars, upstream momentum is minimal.
- What should I use instead of symfony-bundles/queue-bundle in Laravel?
- Laravel already ships a complete queue stack in Illuminate\Queue, configured in config/queue.php and broker-agnostic across Redis, database, SQS, and AMQP drivers. Jobs are plain classes with a handle() method dispatched through the container, with retries, backoff, queue:failed, and Horizon for supervision and metrics. If the real requirement is a durable queue with retries and a dead-letter path, the answer is configuration, not an additional package.
- Can Laravel producers and a Symfony consumer share the same queue?
- Yes, but through a sidecar pattern rather than direct integration. Run the bundle inside a small standalone Symfony worker application that shares the same broker, such as Redis, AMQP, or the database, with Laravel producers, and define a versioned message contract between them. This keeps Laravel's queue stack intact and isolates the Symfony dependency, at the cost of a second runtime, a second deployment unit, and a schema contract someone must govern.
- What are the production risks of adopting symfony-bundles/queue-bundle?
- The risks are high: an unmaintained 2017 codebase, likely PHP 8 and modern Symfony DI incompatibility, dependency pinning conflicts, and no upstream security response. You would also be operating a second runtime with its own deployment, configuration, and observability burden. Only pursue the sidecar-worker pattern if a concrete capability gap is documented first, and decide up front who owns the fork and what patch latency is acceptable for a security fix.
Weaver
How can I help you explore Laravel packages today?