Weave Code
Queue Bundle Laravel Package
kfzteile24/queue-bundle
kfzteile24/queue-bundle is a Symfony bundle that simplifies message queue integration, providing configuration and services for dispatching and consuming asynchronous jobs reliably in PHP applications.
At a glance
Frequently asked questions about Queue Bundle
- Can I install kfzteile24/queue-bundle in a Laravel app with Composer?
- Not usefully. The package is a Symfony bundle that relies on Symfony's bundle registration, DI extension, and configuration tree, and it ships its producer and consumer abstractions as container-wired services. Laravel's container will not autoconfigure those services, so a direct composer require into a Laravel app means hand-wiring everything yourself. The recommended path is to treat it as a design reference rather than a dependency.
- Is kfzteile24/queue-bundle a Laravel package?
- No. It is a Symfony bundle published by kfzteile24, a German e-commerce operator, and it targets Symfony conventions throughout. Package-level fit with a Laravel codebase is poor, although the underlying patterns are worth studying. If you are searching for a Laravel queue package, keep looking.
- What message broker does kfzteile24/queue-bundle support?
- The bundle is RabbitMQ and AMQP-centric, providing producer and consumer abstractions over that broker. It does not target Redis or SQS, which is what most Laravel applications use through the native queue system. Adopting it therefore means adopting RabbitMQ plus a separate Symfony worker runtime.
- How does kfzteile24/queue-bundle handle retries, backoff, and dead-letter queues?
- The bundle implements retry-counter handling and dead-letter routing as part of its consumer flow, which is its most transferable idea. Whether that logic lives in standalone service classes or is entangled with Symfony event dispatchers and the config tree is unverified and needs a source audit. Read the consumer loop and the retry/DLQ implementation before assuming you can lift it.
- What is the best way to use kfzteile24/queue-bundle in a Laravel project?
- Harvest the patterns instead of adopting the package. Read its consumer loop, retry-counter handling, and dead-letter routing, then encode equivalent guarantees natively using job middleware for retry and backoff, failed_jobs plus a dead-letter table for terminal failures, and idempotency keys for at-least-once delivery. You keep the operational lessons and drop a 2-star dependency.
- Can I run kfzteile24/queue-bundle as a standalone consumer process alongside my Laravel app?
- It is feasible only if your organization already operates Symfony services, in which case you can stand up a separate consumer process sharing the same RabbitMQ broker as the Laravel app. That gives you a clean, low-coupling broker-level integration. If you have no Symfony footprint, the cost of introducing one just for this bundle is not justified.
- Is kfzteile24/queue-bundle actively maintained and safe for production?
- The signals are mixed. It has roughly 2 stars and zero dependents, a single-vendor maintainer, and a thin README, which suggests an extracted internal library published for convenience rather than a community-supported project. The mitigating factor is recency: a June 2025 release implies the owner still exercises it in production. Bus factor, not code quality, is the principal risk.
- Which PHP and Symfony versions does kfzteile24/queue-bundle require?
- That is not established from the available information, and with zero dependents there is no ecosystem evidence of compatibility breadth. The maintainer's own application is effectively the only tested configuration. Read composer.json and verify the PHP and Symfony constraints against your runtime baseline before any spike, and budget time for a compatibility check rather than assuming it works.
- Should I fork kfzteile24/queue-bundle and strip out the Symfony layer to use it in Laravel?
- Avoid that path. The MIT license makes forking legally cheap, but it transfers the entire engineering and maintenance burden to you, and you would be maintaining a stripped fork of a 2-star package indefinitely. It is a maintenance trap compared with reimplementing retry, backoff, and dead-letter semantics natively in Laravel.
- How does kfzteile24/queue-bundle compare with Laravel's native queue, Horizon, and job middleware?
- They solve similar problems in different ecosystems. Laravel's native queue plus job middleware, failed_jobs, and Horizon already covers retry, backoff, and failure handling for Redis or SQS workloads, while this bundle presumes RabbitMQ, a separate worker runtime, and Symfony conventions. For a Laravel team the native stack is the better fit; the bundle is useful as a compact reference for retry and dead-letter semantics.
Weaver
How can I help you explore Laravel packages today?