Weave Code
Roadrunner Laravel Laravel Package
spiral/roadrunner-laravel
RoadRunner-powered application server for Laravel: replaces PHP-FPM with a high-performance Go worker, boosting throughput and cutting latency. Includes config publishing, Laravel integrations, and support for HTTP and queues via a simple composer install.
Complete Laravel integration for RoadRunner with support for HTTP, Jobs, gRPC, and Temporal plugins - going beyond Octane's capabilities
Frequently asked questions about Roadrunner Laravel
- What is spiral/roadrunner-laravel and how does it differ from Laravel Octane?
- spiral/roadrunner-laravel is a complete Laravel integration for RoadRunner, a high-performance Go application server that replaces PHP-FPM with long-running workers. It supports HTTP, Jobs, gRPC, and Temporal plugins, going beyond Octane's capabilities. Use it when you want RoadRunner worker lifecycle control or Temporal workflows, not just faster HTTP handling.
- How do I install spiral/roadrunner-laravel in a Laravel app?
- Install it with Composer, publish its configuration, and run Laravel through a RoadRunner worker instead of PHP-FPM. The Composer and Laravel configuration steps are straightforward, but you must also install and operate the RoadRunner binary. Pilot on a non-critical service or queue before production rollout.
- Which Laravel, PHP, and RoadRunner versions does spiral/roadrunner-laravel support?
- The release notes and Composer constraints are the source of truth, because the bridge must track Laravel, PHP, RoadRunner, and optional Temporal compatibility. Version 6.6.2 is a maintenance patch rather than a new feature release. Verify supported versions in staging before upgrading, especially if you use Temporal.
- Does spiral/roadrunner-laravel support Laravel queues and jobs?
- Yes, it integrates Laravel queues through RoadRunner's Jobs plugin. Version 6.6.2 fixes delayed job release units, max-tries fallback, failed jobs without exceptions, and array backoff handling. Regression-test retry counts, delays, backoff, and failure visibility because corrected semantics can change observed runtime behavior.
- Should I upgrade to spiral/roadrunner-laravel 6.6.2?
- It is a maintenance patch that corrects queue, cache, and Temporal edge cases, including cache TTL preservation on increment/decrement and Temporal activity exception propagation. The release notes do not indicate breaking API changes, but the fixes can alter retry counts, delays, backoff, cache expiry, and failure visibility. Upgrade in staging and regression-test critical queue and cache paths before production.
- Can I run Temporal workflows from Laravel with this package?
- Yes, the package includes optional Temporal integration alongside HTTP, Jobs, and gRPC plugins. Version 6.6.2 corrects Temporal activity exception propagation, so activity failures surface correctly. Validate your Temporal worker configuration and activity failure handling in staging if workflows are on critical paths.
- What are the main production risks of running Laravel on RoadRunner?
- Primary risks include long-running worker state leakage, changed queue semantics after upgrades, cache counters or rate limiters losing TTL in edge cases, and Temporal workflows not surfacing activity failures. You also need observability for worker crashes, retries, and failed jobs. RoadRunner worker lifecycle and binary upgrades require clear operational ownership.
- How should I regression-test a spiral/roadrunner-laravel upgrade?
- Test cache increment and decrement TTL behavior, delayed job release timing, max-tries fallback, array backoff, exception-less job failures, and non-object task payloads. If you use Temporal, verify activity exception propagation. Run these checks in staging against a RoadRunner worker, then canary with metrics and rollback criteria.
- Do I need to know Go to use spiral/roadrunner-laravel?
- You do not need Go to install the Composer package or configure Laravel, but you do need operational expertise for the RoadRunner binary and worker lifecycle. Teams without RoadRunner experience should build that knowledge before production adoption. The package is an integration layer, not a replacement for RoadRunner operations ownership.
- What are the alternatives to spiral/roadrunner-laravel?
- Laravel Octane is the common alternative for running Laravel on long-running workers, but this package adds Jobs, gRPC, and Temporal plugins beyond Octane's capabilities. Standard PHP-FPM with Laravel queue workers remains sufficient for many applications. Choose RoadRunner when performance, worker lifecycle control, or Temporal workflows justify the extra operational overhead.
Weaver
How can I help you explore Laravel packages today?