Weave Code
Queue Bundle Laravel Package
kuborgh/queue-bundle
A Symfony bundle that adds queue-based background job processing to your application. It provides configuration, services, and console commands for publishing and consuming queued messages, helping you offload time-consuming tasks to workers with minimal setup.
kuborgh/queue-bundle adds a lightweight, dependable queue layer to your PHP application, letting you move slow work—emails, exports, webhooks, image processing—out of the request cycle and into background workers. Define a job, dispatch it, and the bundle handles the rest: pushing messages onto a queue, running workers, and keeping failures contained so your application stays fast and responsive under load.
- Pluggable backends for queue storage and transport
- Automatic retries with configurable backoff and failure handling
- Priority queues so critical jobs are processed first
- Long-running worker commands suitable for process supervisors
- Straightforward service integration with minimal configuration
Frequently asked questions about Queue Bundle
- Is kuborgh/queue-bundle compatible with Laravel?
- No. kuborgh/queue-bundle is a Symfony bundle built around DependencyInjection compiler passes, container tags, and kernel bundle registration, so it cannot be installed into a Laravel application as-is. Laravel's service-provider model has no meaningful equivalent for those Symfony integration points. For Laravel, use the framework-native queue with the database, Redis, or SQS driver and Horizon for supervision.
- Can I install kuborgh/queue-bundle in a Laravel application via Composer?
- You should not attempt it. Composer may resolve the package, but the bundle expects Symfony kernel registration and container tags that Laravel does not provide, so it will not boot correctly. Even in a Symfony app, the 2016 release is expected to fail or produce deprecation noise on modern PHP 8.1+ and Symfony 5.4, 6.4, or 7.x. Use Laravel's native queue system instead.
- What Laravel version does kuborgh/queue-bundle support?
- None. The package is a Symfony bundle, not a Laravel package, and its metadata shows no Laravel support at all. It has had no release since May 2016, which predates modern Laravel queue features and Laravel 5.x-era compatibility assumptions. There is no supported Laravel version to target.
- How do I install and configure kuborgh/queue-bundle?
- In a Symfony application you would historically add the bundle to composer.json, register it in the kernel, and configure queues and workers through bundle configuration. However, installation against modern PHP and Symfony LTS is expected to fail on transitive constraints or to install with unpatched code paths. There is no Laravel installation path, and the repository has no visible CI or test suite to validate setup. Do not plan a new installation around it.
- Does kuborgh/queue-bundle work with Symfony 6 or 7?
- It is not expected to work cleanly. The last release was May 2016, before Symfony Flex, default autowiring, and Symfony Messenger, and Composer resolution against Symfony 6.4 or 7.x is likely to fail on version constraints. Even if it installs, the code paths are unmaintained and untested on current runtimes. Use Symfony Messenger with a Doctrine, Redis, or AMQP transport instead.
- What should I use instead of kuborgh/queue-bundle in Laravel?
- Use Laravel's first-party queue system with the database, Redis, or SQS driver, and add Horizon for supervision and observability. That gives you retries, backoff, failed-job handling, and worker management without taking on abandoned legacy code. If you are actually on Symfony, use Symfony Messenger rather than this bundle.
- Is kuborgh/queue-bundle maintained or safe for production?
- No. It is an abandoned, single-maintainer bundle with no release since May 2016, three stars, zero dependents, and no security policy or advisory monitoring. The technical risk is high: unmaintained code plus transitive dependencies that have not been patch-reviewed in roughly nine years. There is no visible CI or test suite, and the bus factor is one. Do not adopt it for production.
- How does kuborgh/queue-bundle persist queued jobs?
- The persistence backend is not established from the package metadata. It is unclear whether it uses the filesystem, a database table, or a broker, so you cannot reason about at-least-once versus at-most-once delivery from the available information. That ambiguity makes duplicate or lost work a real unknown risk. Resolve the storage model before considering any use.
- Can kuborgh/queue-bundle run queued Symfony console commands asynchronously?
- That is the bundle's stated purpose: it queues Symfony console command invocations so time-consuming tasks run in asynchronous workers outside the request cycle. However, coupling a queue to shell-invokable commands is a narrow abstraction that impedes serializable messages, idempotency, testing, and result handling. Symfony Messenger solves the same problem with transports, middleware, retries, and a failure transport, and it is first-party and maintained.
- What are alternatives to kuborgh/queue-bundle for background jobs?
- For Laravel, use the native queue drivers (database, Redis, or SQS) with Horizon for supervision. For Symfony, use Symfony Messenger with Doctrine, Redis, or AMQP transports, plus messenger:consume workers, retries, backoff, and a failure transport. Both are first-party, actively maintained, and strict supersets of this bundle's console-command queueing. If you need cross-framework messaging, evaluate a broker-backed solution rather than this abandoned bundle.
Weaver
How can I help you explore Laravel packages today?