Burrow Bundle Laravel Package

Product Decisions This Supports

• Messaging architecture choice: Whether to standardize AMQP integration through a Symfony bundle versus native Symfony Messenger. This package is a thin integration layer over evaneos/burrow; it should not be treated as a strategic messaging platform.
• Build vs. buy/inherit: The wrapper is small, low-adoption (2 stars, 0 dependents), and last released in 2022. Building a minimal adapter on a maintained AMQP client or adopting Symfony Messenger is likely lower-risk than inheriting this dependency.
• Feature scope: It can support basic Symfony DI/configuration for AMQP producers/consumers, but it does not meaningfully address retries, dead-letter queues, observability, multi-transport routing, or modern Symfony compatibility. Product capabilities should not be planned around it.
• Roadmap and modernization: If a product already uses evaneos/burrow, this package supports a containment strategy and migration planning toward Symfony Messenger or another maintained transport.
• Use cases: Reasonable only for legacy Symfony Standard applications with an existing burrow commitment, internal tools, or short-lived proofs of concept. Poor fit for customer-facing, high-scale, long-lived, or security-sensitive products.

When to Consider This Package

Consider it only when:

• You maintain a legacy Symfony Standard application that already uses evaneos/burrow and needs bundle-level configuration/DI wiring.
• You need a short-lived internal migration or proof of concept where burrow is already accepted and the team accepts ownership of the dependency.
• You require only thin Symfony integration, not advanced messaging semantics.
• You are prepared to vendor/fork and maintain the package, because ecosystem signals are weak: 2 stars, 0 dependents, last release November 2022, and limited maturity evidence.

Look elsewhere when:

• You are building a new Symfony application or targeting modern Symfony versions.
• You need active maintenance, security updates, community support, or predictable compatibility.
• You need retries, dead-letter queues, observability, routing flexibility, or multi-transport support.
• You want a strategic, long-term messaging foundation. Prefer Symfony Messenger with AMQP transport, php-amqplib, Enqueue, or a managed cloud queue.

How to Pitch It (Stakeholders)

Executive summary: This is a very small, low-adoption Symfony bundle for AMQP messaging with no recent releases and no dependent ecosystem. It is not a strategic investment and creates maintenance and compatibility risk. We should avoid it for new products and, if already present, contain it and budget a migration to a maintained messaging approach.

Engineering summary: evaneos/burrow-bundle is a thin Symfony wrapper around the evaneos/burrow AMQP library. It may be acceptable only for legacy Symfony Standard services already committed to burrow. For greenfield work, use Symfony Messenger with AMQP transport or a maintained AMQP client. If adopted, plan to fork/vendor, pin versions, and own updates.