- Is levuro/job-queue-bundle a Laravel package?
- No. levuro/job-queue-bundle is a Symfony bundle built on Doctrine ORM, FrameworkBundle, and the Symfony console. It ships no Laravel service provider, facade, publishable config, or integration with Laravel's queue contract, Illuminate\Bus, or Eloquent. Composer installability alone does not make it a Laravel package.
- Can I use levuro/job-queue-bundle in a Laravel application?
- Not as a drop-in package. You would need to bridge Symfony console commands, Doctrine entities, and the bundle's worker into Laravel, which is significant custom work. For most Laravel apps, the built-in database queue plus a thin job audit table, or Horizon, delivers the same durable job records and operator visibility with far less risk.
- How do I install and configure levuro/job-queue-bundle?
- In a Symfony app, install with composer require levuro/job-queue-bundle, register JMSJobQueueBundle in the kernel, ensure Doctrine ORM is configured, and create the job tables from the bundle's schema or migrations. Then run the jms-job-queue:run worker command to process queued jobs. There is no Laravel config file to publish or Laravel service provider to register.
- What Laravel versions does levuro/job-queue-bundle support?
- There are no supported Laravel versions because the package has no Laravel integration. Laravel version compatibility is therefore not a meaningful evaluation axis. If you need Laravel queue features, evaluate Laravel's queue drivers, Horizon, or a Laravel-native package instead.
- What Symfony and PHP versions does levuro/job-queue-bundle require?
- The release context points to Symfony 4.4 or newer because version 1.10.9 requires symfony/error-handler, which exists from Symfony 4.4 onward. Always check the package's composer.json for the exact declared PHP and Symfony constraints and confirm the lowest supported Symfony version is tested in CI. The bundle is best suited to Symfony 4.4+, ideally 5.4 or 6.x, with Doctrine ORM already present.
- Does levuro/job-queue-bundle support retries, failures, and delayed jobs?
- Yes. The bundle provides a persistent database-backed queue with retry and failure states, delayed execution, recurring or cron-style scheduling, and an admin web UI for inspection. Jobs are processed by the jms-job-queue:run worker command, and each job is stored as a database record. That makes failures and history queryable rather than buried in logs.
- What are Laravel alternatives to levuro/job-queue-bundle?
- The closest Laravel equivalents are the database queue driver, Redis with Horizon, and a small job audit table when you need durable history. The bundle's genuine advantages are transactional enqueue in the same database transaction as business data and job history as first-class data. Laravel can approximate both with afterCommit, the database driver, and Horizon's failed-job and metrics stores, so the bundle is rarely the cheapest path in a Laravel estate.
- Is levuro/job-queue-bundle safe for production at scale?
- Treat it as suitable for low volume, roughly low thousands of jobs per hour or less, in a Symfony 4.4+ app that already uses Doctrine ORM. The project has very low adoption, zero dependents, and a bus factor of effectively one, so you are implicitly the QA. It is not a good anchor for a large-scale, multi-year roadmap without a fork-and-own plan.
- How is levuro/job-queue-bundle maintained?
- The project is effectively feature-frozen. Release 1.10.9 from April 2024 was a dependency swap that dropped symfony/debug and required symfony/error-handler, with no new features or API changes. It also shipped as a patch release despite changing Composer constraints, which signals limited release discipline and a real risk of silent transitive removal for anything relying on symfony/debug.
- How should I test levuro/job-queue-bundle before adopting it?
- For a Laravel evaluation, do not test it as a Laravel package because it is not one. In a Symfony spike, verify transactional enqueue, worker exception and error paths after the error-handler dependency change, retry and failure behavior, and the job schema under Doctrine. If you only need Laravel background jobs, test the database queue driver with afterCommit plus a job audit table, or Horizon, before considering a custom Symfony bridge.