Weave Code
Roadrunner Jobs Laravel Package
spiral/roadrunner-jobs
PHP bridge for the RoadRunner Jobs plugin, letting you push and consume queued jobs through RoadRunner's queue drivers such as memory, AMQP, SQS, Redis, and Beanstalk. Installs via Composer and is configured with a simple jobs pipeline YAML section.
spiral/roadrunner-jobs is the PHP bridge for the RoadRunner Jobs plugin, letting Laravel/PHP applications push and consume background jobs through a high-performance Go-based application server. Install it via Composer, configure one or more pipelines in your RoadRunner YAML (e.g. the memory driver), and start the server to get named job queues such as local.
- Multiple drivers: memory, AMQP, SQS, Redis, NATS, Beanstalk
- Priority and prefetch tuning per pipeline
- Push, consume, and delayed/retry job handling
- PSR-friendly codebase with Psalm, PHPUnit, and StyleCI coverage
- Works with the
spiral/roadrunner-cliinstaller for matching binaries
Frequently asked questions about Roadrunner Jobs
- How do I install spiral/roadrunner-jobs with Composer?
- Install the package with composer require spiral/roadrunner-jobs. For a compatible RoadRunner binary, the README also suggests composer require spiral/roadrunner-cli --dev and then vendor/bin/rr get. You will still need to add a jobs adapter to your RoadRunner configuration and wire up the worker bootstrap script.
- How do I configure a RoadRunner Jobs pipeline with the memory driver?
- Add a jobs section to your RoadRunner YAML with consume listing the pipeline and a pipelines entry using driver: memory. The README example sets rpc.listen, server.command to php consumer.php, server.relay to pipes, and memory config such as priority and prefetch. After startup, that pipeline name is available to your application.
- Can I use spiral/roadrunner-jobs as a Laravel queue driver?
- Yes, the package is used to integrate RoadRunner Jobs with Laravel's queue system by replacing process-per-job workers with persistent RoadRunner workers. It relies on Laravel's native dispatch and handler interfaces while RoadRunner handles processing. You configure the queue driver rather than rewriting job code.
- Which RoadRunner version does spiral/roadrunner-jobs 4.9.0 require?
- Release 4.9.0 adds support for RoadRunner v3, so that line is explicitly coupled to the v3 runtime. If you are still on RoadRunner v2, the assessment recommends confirming that you can stay on 4.8.x until a runtime upgrade is scheduled. Verify PHP and Laravel constraints from composer.json before committing.
- Is spiral/roadrunner-jobs 4.9.0 compatible with RoadRunner v2?
- The 4.9.0 release is described as the v3-capable line, and the evaluation warns that package version, RoadRunner binary, and spiral/roadrunner-* transport dependencies must move together. Teams on RoadRunner v2 should pin to 4.8.x and confirm with the maintainer whether patches continue. Do not treat 4.9.0 as a routine minor bump for a v2 runtime.
- What does the consume_all deprecation mean for AMQP and Beanstalk pipelines?
- In 4.9.0, consume_all is deprecated for AMQP and Beanstalk pipelines but still works for now. It is a config-level breaking change deferred to a future major, so inventory pipeline definitions and remove it ahead of removal. Other pipeline types are not affected, and the replacement semantics are not stated in the assessment.
- What queue drivers are available in RoadRunner Jobs?
- Drivers are configured in the RoadRunner jobs YAML; the README example uses the memory driver with priority and prefetch settings. The documentation covers additional drivers, and the assessment specifically mentions AMQP and Beanstalk pipelines in relation to consume_all. Check the RoadRunner queues documentation for the driver that matches your broker.
- Do I need to run RoadRunner as a separate service in production?
- Yes. RoadRunner remains a standalone service and becomes a new infrastructure dependency alongside your Laravel application. That is consistent with event-driven architectures, but it requires platform maturity to run and supervise the service. Fit weakens for teams that cannot operate a RoadRunner process fleet.
- What are alternatives to spiral/roadrunner-jobs for Laravel queues?
- Alternatives include keeping Laravel's default queue worker model or using other Laravel queue backends and worker supervisors. spiral/roadrunner-jobs is strongest where high job throughput makes per-job process startup cost material and you can run RoadRunner as a service. Evaluate operational overhead before replacing an existing worker fleet.
- How should I test and sequence a RoadRunner Jobs upgrade?
- Treat the upgrade as two tracks: upgrade RoadRunner v2 to v3 and then adopt 4.9.0, validating the v3 config schema, rerunning the worker bootstrap, and load-testing before shifting production traffic. Separately inventory and remove consume_all from AMQP and Beanstalk pipeline definitions. Teams unable to take the runtime upgrade should pin to 4.8.x and track 4.9.x for backported fixes.
Weaver
How can I help you explore Laravel packages today?