Weave Code
Laravel Priority Queue Laravel Package
shipsaas/laravel-priority-queue
shipsaas/laravel-priority-queue adds priority-based job processing to Laravel queues, letting you assign priorities so urgent jobs run before lower-priority work. It provides a straightforward way to dispatch and manage prioritized jobs in your application.
Priority Queues driver implementation for Laravel. Utilizing DB Driver.
Frequently asked questions about Laravel Priority Queue
- What does shipsaas/laravel-priority-queue do?
- It adds priority-based job processing to Laravel queues so urgent jobs can run before lower-priority work. The package is a priority queue driver implementation that utilizes Laravel's database queue driver. You dispatch and manage prioritized jobs through the package's API rather than relying only on first-in-first-out database queue behavior.
- How do I install and configure shipsaas/laravel-priority-queue in a Laravel app?
- Install it with Composer using composer require shipsaas/laravel-priority-queue. Laravel package discovery typically registers the service provider automatically, but confirm this in the package documentation. Then configure your queue connection to use the package's database-backed priority driver and start a queue worker for that connection. Check the README for the exact connection and configuration keys because the provided excerpt does not list them.
- Which Laravel and PHP versions does shipsaas/laravel-priority-queue support?
- Version 1.1.0 supports Laravel 10 and Laravel 11 applications on PHP 8.2 or newer. The package is aimed at modern Laravel and PHP stacks. If you are on an older Laravel or PHP release, check the package's composer.json constraints before installing.
- Does shipsaas/laravel-priority-queue support Laravel 9 or PHP 8.1?
- No, v1.1.0 drops support for Laravel 9 and PHP 8.1. Teams still on those versions must either remain on an older package release or upgrade their host application to Laravel 10 or 11 and PHP 8.2 or newer first. This support drop is a de facto breaking change for legacy stacks even though the release notes claim no breaking changes.
- Is upgrading to shipsaas/laravel-priority-queue v1.1.0 a breaking change?
- It is a minor version bump, but it removes Laravel 9 and PHP 8.1 support, which is a de facto breaking change for applications on those platforms. No code changes are expected per the release notes, but undocumented internal changes may exist. Treat the upgrade as gated by your Laravel and PHP versions and run regression tests after updating.
- How do I upgrade to shipsaas/laravel-priority-queue v1.1.0?
- Upgrade your Laravel application to Laravel 10 or 11 and your PHP runtime to 8.2 or newer first. Then update the package with Composer and run your full test suite, especially if the queue touches core workflows. Review the changelog and composer.json constraints before rolling out across multiple services. If you cannot upgrade Laravel or PHP yet, stay on an older package version.
- How do I assign priorities to jobs with shipsaas/laravel-priority-queue?
- You assign a priority when dispatching jobs so the package can process urgent work before lower-priority jobs. The database driver stores and retrieves queued jobs according to that priority ordering. The exact dispatch API and priority values are defined in the package documentation, so verify the syntax there before changing production jobs.
- Does shipsaas/laravel-priority-queue require Redis or SQS?
- No, it utilizes Laravel's database queue driver, so it does not require Redis or SQS. This makes it a fit for applications that already use database-backed queues and want priority ordering without adding another queue backend. You still need a properly configured database queue table and workers running against the priority queue connection.
- How does shipsaas/laravel-priority-queue affect queue workers and production deployment?
- Your queue workers must run against the package's priority queue connection, and you should restart workers after deploying changes. The package has no direct scaling impact according to the assessment, but priority ordering can change job latency patterns under load. Plan regression tests and monitor worker behavior after upgrading or changing job priorities.
- Is shipsaas/laravel-priority-queue production-ready and how is it tested?
- The provided release notes only cover platform support changes and do not document test coverage or the CI matrix. Review the repository's tests and CI configuration before relying on it in production. Run your own regression tests, particularly after upgrading to v1.1.0, because Composer dependency conflicts are the primary integration risk.
Weaver
How can I help you explore Laravel packages today?