- Is an1zhegorodov/j-queue-bundle compatible with Laravel?
- No. It is a Symfony2 bundle built around Symfony's Kernel, dependency injection, and event dispatcher, not Laravel's service providers or Illuminate\Contracts\Queue. There is no shared abstraction surface, so it cannot be dropped into a Laravel app. Laravel's native queue subsystem is the correct choice.
- Can I install j-queue-bundle in a Laravel project with Composer?
- Technically you might be able to add the Composer package, but it will not function as a Laravel queue. The bundle expects Symfony 2.x components and PHP 5.x-era APIs that are removed or renamed in modern PHP and Symfony. It will not install against PHP 8.2+ without a fork. Integration would require a bespoke bridge that is not advised.
- What Laravel versions does j-queue-bundle support?
- None. The package is a Symfony2 bundle and does not declare support for Laravel. It is bound to Symfony 2.x, which reached end of life in 2018. Laravel developers should use Illuminate\Queue with the database or Redis driver instead.
- Does j-queue-bundle work with PHP 8.2?
- No, not without a fork. The evaluation infers PHP 5.x constraints from the Symfony 2.x dependency graph, and those versions are long past supported. Composer will likely block installation on PHP 8.2+ due to platform requirements. Modernizing it would require dropping Symfony DI and EventDispatcher coupling.
- Is j-queue-bundle maintained or abandoned?
- The evaluation describes it as effectively abandoned: zero stars, zero dependents, and no observable community. There is no evidenced test coverage and no CVE triage. That makes it a correctness and security liability for production use.
- What are the best alternatives to j-queue-bundle for Laravel?
- Laravel ships with a complete queue subsystem: drivers for database, Redis, SQS, and beanstalkd; Job classes with tries, backoff, and timeout; failed_jobs persistence; middleware; batching; and Horizon for observability. It is already installed and requires zero new dependencies. Use Illuminate\Queue rather than adopting an unmaintained Symfony bundle.
- Does j-queue-bundle support retries, timeouts, or failed jobs?
- That is unknown and flagged as a key question in the evaluation. The bundle is described as simple queueing, and with no evidenced tests you should not assume production-grade visibility timeouts, retries, or a dead-letter path. Verify the source before relying on any such behavior.
- Can I fork j-queue-bundle and adapt it for Laravel?
- A fork is technically possible but expensive: you would drop all Symfony DI and EventDispatcher coupling, target PHP 8.2+, pin to illuminate/* contracts, add a QueueServiceProvider, and build a parity test suite. The evaluation estimates 2–3 sprints for one engineer plus ongoing ownership. Only do this if source review reveals non-trivial domain logic absent from Laravel's queue.
- Why should I avoid using j-queue-bundle in a Laravel application?
- Because it offers negative value in a Laravel context. Adopting it means replacing a mature, supported, documented subsystem with an unmaintained one plus a bespoke bridge. The architecture fit is poor, technical risk is high, and Laravel's native queue already solves the problem. Treat it as a design reference only, if at all.
- How do I use j-queue-bundle's queue logic in Laravel?
- You should not integrate the bundle directly. The recommended path is to read its source for any specific priority or deduplication approach, then implement the equivalent as a Laravel Job class with queue middleware. That costs hours and carries no risk. Do not bridge the bundle as-is.