- Can I use heristop/jobqueue-bundle in a Laravel application?
- No supported path exists. It is a Symfony bundle built around the Symfony FrameworkBundle dependency-injection extension model, and Laravel has no bundle or kernel-extension registration mechanism for it. The only conceivable route is a custom bridge around its Zend Queue adapters via QueueManager::extend(), which you would own and maintain indefinitely. Laravel's native queue drivers already cover durable asynchronous job processing.
- Does this package support Laravel 10 or Laravel 11?
- No. The last release was 2016-09-07 and it targets PHP 5.5–7.x and Symfony/Zend idioms. It will likely fail dependency resolution and language-level checks on modern Laravel and PHP 8+ stacks. Use Laravel's database, Redis, or SQS queue drivers instead.
- What is heristop/jobqueue-bundle actually for?
- It is a Symfony bundle for adding a persistent job queue: dispatching background jobs, running dedicated workers, handling retries and failures, and tracking job status with Doctrine-backed storage. It wraps Zend Queue adapters in Symfony dependency injection. That specific value proposition does not transfer to Laravel.
- How do you install and configure it in Symfony?
- Installation follows Symfony bundle conventions: install via Composer, register the bundle, and configure queue adapters and worker services through Symfony DI in YAML or XML. The bundle wraps Zend Queue adapter services, so you must supply a compatible adapter implementation. Exact configuration keys are not documented in the provided context, so inspect the bundle source before relying on it.
- Is heristop/jobqueue-bundle maintained and safe for production?
- No. It was last released in 2016, has 15 stars and zero dependents, with no issue triage, fork momentum, or observable production usage. It depends on the abandoned Zend Framework namespace, which has no security advisory or disclosure channel and no compatible release line with modern PHP. The MIT license is clean, but permissiveness does not mitigate abandonment; the package health score of 0.255 should be treated as a disqualifying signal.
- What PHP versions does heristop/jobqueue-bundle support?
- It almost certainly targets PHP 5.5–7.x idioms from its 2016 release. PHP 8.x breaks on issues such as reserved words, curly-brace string offsets, each() removal, and untyped null handling. There is no compatible release line with modern PHP, so validate in a throwaway application before considering any use.
- Can I bridge heristop/jobqueue-bundle to Laravel's Queue contract?
- Technically you can implement Illuminate\Contracts\Queue\Queue, or use QueueManager::extend(), around a Zend Queue adapter. However, Laravel expects a serialized job envelope with attempts, backoff, timeouts, and Queueable entity resolution, while Zend Queue messages are opaque strings. The adapter layer becomes a nontrivial serialization shim that you would own and maintain indefinitely. Extracting the bundle's logic is likely to yield little that Laravel does not already provide.
- What Laravel alternatives should I use for background jobs instead?
- Use Laravel's native queue system with the database, Redis, or SQS drivers, plus Horizon for Redis monitoring. These provide retries, backoff, timeouts, failed-job handling, and status visibility. They are actively maintained and integrate directly with Laravel's container, events, and service providers. There is no need for a Symfony or Zend Queue bundle.
- How should I test or spike this package before adopting it?
- Start with one to two days of discovery: read the bundle source and inventory the adapters and behaviors that cannot be reproduced with Laravel's Queue contract; expect the feature gap to be negligible. Then timebox a three-to-five-day spike in a throwaway Laravel app on the target PHP version, running static analysis and dependency resolution. PHP 8 incompatibility will likely surface there and terminate the spike. Only if it passes should you build a thin connector via QueueManager::extend() and fork or pin the Zend Queue dependency under your own namespace.
- Is there any reason to keep this package if we have a legacy Zend Queue broker?
- Only if you must read or drain an existing Zend Queue deployment, such as a legacy Memcache- or Mongo-backed queue, for continuity. Even then, isolate it as a read-and-drain bridge rather than adopting the bundle as your job system. Confirm whether the target runtime is pinned to an older PHP version, because modern PHP likely ends the evaluation. Otherwise, reimplement any genuinely useful adapter behavior natively.