Resque Bundle Laravel Package

Product Decisions This Supports

• Async job processing architecture — the underlying capability (offloading emails, exports, image processing, webhook fan-out, third-party API calls off the request cycle into a Redis-backed worker pool) is a legitimate and common product need.
• Build vs. buy for infrastructure glue — this package is a thin Symfony 2 service-container integration for the PHP-Resque library. The "buy" side is weak: the integration surface is small enough to hand-roll in tens of lines, so the decision is really "adopt an unmaintained adapter" vs. "write the wiring ourselves."
• Vendor risk and tech-debt assessment — zero stars, zero dependents, no community validation, targeting a framework branch (Symfony 2) that reached end of life in 2019. Useful as a data point in a dependency audit or legacy-portfolio review, not as a greenfield choice.
• Roadmap input for legacy migrations — if this appears in an existing codebase, it signals a Symfony 2 application that likely needs a broader upgrade plan (to Symfony Messenger, Enqueue, or a framework-native queue) rather than incremental patching.

When to Consider This Package

Consider only if:

• You are maintaining an existing Symfony 2.x application that already runs PHP-Resque and you want a pre-built container/service wiring rather than writing it yourself.
• The application is frozen, internal-only, and low-risk, with no upgrade path budgeted.
• You are studying historical integration patterns ahead of a migration.

Look elsewhere if:

• The project is on Symfony 3.4+ or later — use Symfony Messenger with a Redis, Doctrine, or AMQP transport, or Enqueue.
• The project is Laravel (note: this is a Symfony bundle, despite the framing — it won't drop into a Laravel app) — use Laravel's native queue with Horizon or a Redis driver.
• You need PHP 8 compatibility, security patches, active maintenance, documentation, or any community support. All of these are absent here.
• You have production SLAs, compliance requirements, or on-call rotation. An abandoned dependency with no patch path is an operational liability.
• You need observability (job metrics, retries, dead-letter queues, dashboards) — modern alternatives provide this; this bundle does not.

How to Pitch It (Stakeholders)

Executive summary — recommendation: do not adopt.

The problem this package addresses is real: moving slow work out of the request cycle is standard practice and worth investing in. The package itself is not the right instrument. It has no adoption, no maintainers of record, no security patching, and targets Symfony 2, which has been end-of-life since 2019. The savings it offers over writing the integration ourselves are marginal — it is a thin adapter, not a platform.

For engineering: it is a dependency-integration shim for PHP-Resque. If PHP-Resque is genuinely required in a legacy context, vendor it or write the service wiring directly so we control the code. For anything new, standardize on Symfony Messenger (Symfony) or the native queue plus Horizon (Laravel).

For the business: the risk-reward is unfavorable — negligible time saved, meaningful downside in unpatched code and bus factor. We should solve async processing with a maintained option and treat this package as a migration artifact, not a building block.