Weave Code
Job Queue Bundle Laravel Package
markup/job-queue-bundle
A Symfony bundle for background job processing and queues. Dispatch, process, and manage asynchronous tasks with pluggable queue backends, keeping time-consuming work out of the request cycle so your application stays fast and responsive.
The Markup Job Queue bundle integrates with RabbitMQ (via https://github.com/videlalvaro/RabbitMqBundle) to provide automatic scheduling of recurring console commands (i.e cron) and commands to help with deployment
Frequently asked questions about Job Queue Bundle
- Can I use markup/job-queue-bundle in a Laravel application?
- Not directly. It is a Symfony bundle that registers MarkupJobQueueBundle in a Symfony kernel and relies on Symfony's DI container and Console component, with no Laravel service provider, facade, or config publishing. Making it run alongside Laravel would mean booting two competing containers and event dispatchers, which the technical evaluation rates as a fragile pattern. The recommended path is to port the pattern, not adopt the package.
- What does markup/job-queue-bundle actually do?
- It adds a persistent, broker-backed job queue and scheduler to Symfony applications. Recurring console commands are published into RabbitMQ as delayed messages and executed by workers, replacing host-level cron. It also ships deployment-time commands for pause, resume, drain, and queue setup. The idea is sound; the implementation is tied to Symfony.
- Is markup/job-queue-bundle a drop-in replacement for Laravel's scheduler?
- No. Laravel's console kernel plus schedule:run already provides recurring triggers, and the queue abstraction provides asynchronous dispatch. The bundle's differentiators, delayed and priority dispatch of commands plus deployment-time queue control, are reproducible in Laravel with dispatch()->delay(), queue priority configuration, and a few artisan commands. The evaluation treats it as a reference architecture rather than a dependency.
- How do I install markup/job-queue-bundle?
- In a Symfony app you would require it with Composer, register the bundle in your kernel, and configure the RabbitMqBundle dependency plus a queue setup command. There is no Laravel installation path because there is no service provider or config publishing. For a Laravel codebase, expect to write an adapter or skip it entirely.
- Does markup/job-queue-bundle support Laravel 10, 11, or 12?
- There is no Laravel integration in any version, so Laravel framework version support does not apply. The last release was November 2022, and the exact PHP and Symfony versions it supports were not verified in the evaluation. Check the Composer constraints before assuming compatibility with your runtime. For Laravel, the package is out of scope.
- What are the alternatives for background job processing in Laravel?
- Laravel's built-in queue system supports database, Redis, SQS, and other drivers, with Horizon for Redis monitoring. If you specifically want RabbitMQ, vladimir-yuldashev/laravel-queue-rabbitmq is the mature driver the evaluation points to for broker-backed dispatch. Pair either with Laravel's scheduler for recurring work and you have the bundle's feature set natively.
- Is markup/job-queue-bundle safe to use in production?
- The maintenance signals are weak. It has 17 stars, zero dependents, a single-maintainer organization, and its last release was November 2022, roughly three years stale. It also depends on videlalvaro/RabbitMqBundle, whose own maintenance cadence and PHP support were not verified. For a package on the critical path of job execution, silent failures make staleness especially risky.
- How do I test a Laravel job queue if I port this pattern?
- Use Queue::fake() and assertPushed or assertDispatched to verify jobs are enqueued without running them, and dispatchSync or Bus::fake for synchronous paths. Test scheduled enqueueing with artisan schedule:list and by invoking the scheduler entry point directly. Keep the enqueue step separate from job execution so both sides can be tested in isolation.
- What infrastructure does markup/job-queue-bundle require?
- It requires a RabbitMQ broker, accessed through the videlalvaro/RabbitMqBundle dependency built on php-amqplib. That introduces a broker as a new failure domain for scheduling alone, which the evaluation flags as a question worth answering before adoption. Laravel teams already running RabbitMQ can use a native driver instead of a hybrid adapter.
- How do I reproduce the bundle's delayed dispatch and pause/drain commands in Laravel?
- Dispatch work with delay() and configure queue priorities rather than porting the bundle's command semantics. Add a small set of artisan commands for pause, drain, health, and dead-letter inspection. Make the scheduler entry point enqueue jobs instead of executing them, and add delay or priority only where a job genuinely needs it.
Weaver
How can I help you explore Laravel packages today?