Weave Code
Event Queue Bundle Laravel Package
symfony-bundles/event-queue-bundle
Symfony bundle for queueing and asynchronously processing application events. Decouple event producers from listeners, defer work to background workers, and build scalable event-driven workflows with straightforward Symfony integration.
Symfony Event Queue Bundle
Frequently asked questions about Event Queue Bundle
- What is symfony-bundles/event-queue-bundle?
- It is a Symfony bundle that lets you queue application events and process them asynchronously with background workers, decoupling event producers from listeners. It integrates through Symfony's bundle registration, dependency injection container, compiler passes, and service tagging. It is not a Laravel package and publishes no Laravel service provider or configuration.
- Does symfony-bundles/event-queue-bundle work with Laravel?
- No. There is no Laravel service provider, facade, config file, or evidence of any Laravel compatibility work in the repository. The bundle depends on Symfony's bundle lifecycle and container semantics that have no direct equivalent in Laravel's service-provider architecture. Making it run would require bespoke shim code that you would own and maintain indefinitely.
- How do I install symfony-bundles/event-queue-bundle in a Laravel application?
- You realistically cannot install it meaningfully. A composer require would pull Symfony components the bundle expects, but nothing would wire its services into Laravel's container or reconcile the two event dispatchers. The practical recommendation is not to attempt it and to use Laravel's native event and queue primitives instead.
- Which Laravel versions are supported by symfony-bundles/event-queue-bundle?
- None are supported explicitly. The last release was October 2017, which predates modern PHP and every current Laravel version, so assume incompatibility until proven otherwise. Check the composer PHP and Symfony constraints before spending any integration effort.
- What PHP version does symfony-bundles/event-queue-bundle require?
- The 2017 release cadence means it almost certainly pins or assumes PHP and Symfony versions you cannot run today. It may also fail on typed properties, deprecations, and PSR-11 container changes introduced after it was abandoned. Verify the composer constraints and whether the code even parses on your PHP version as a cheap kill switch.
- Is symfony-bundles/event-queue-bundle actively maintained?
- No. The package has roughly 25 stars, no meaningful community, and no maintainer activity for about eight years. The bus factor is effectively one, so any defect you encounter becomes your defect. Treat it as an abandoned reference implementation rather than a dependency.
- What are the best alternatives to symfony-bundles/event-queue-bundle for Laravel?
- Use Laravel's native queue system with database, Redis, or SQS drivers combined with events and ShouldQueue listeners, and add Laravel Horizon if you need Redis queue monitoring. If you genuinely need Symfony-style messaging, use Symfony Messenger inside a Symfony service rather than a Laravel app. Enqueue/php-enqueue is another option if queue interoperability across brokers is the actual requirement.
- Can symfony-bundles/event-queue-bundle be used in production?
- It is not recommended for production. Security posture is unknown and effectively unpatched, there is no CVE response path, and the dependency tree is a decade old. The MIT license is clean, which is the one unambiguously positive signal, but that does not offset the abandonment risk.
- How does symfony-bundles/event-queue-bundle compare to Laravel's queue and event system?
- It overlaps heavily with Laravel's event dispatcher and queue drivers, duplicating a subset of that surface using Symfony idioms. Adopting it would mean running two queue abstractions side by side or replacing Laravel's queue entirely, and the latter is not realistic. Laravel's primitives are first-class, documented, and actively maintained.
- Should I fork symfony-bundles/event-queue-bundle to add Laravel support?
- Only if you have a crisp requirement that Laravel's native queue and events genuinely cannot satisfy and an internal owner prepared to maintain the fork indefinitely. In practice, mapping the bundle's dispatch and consumption semantics onto Laravel's ShouldQueue job model usually dissolves the case for the package. If a real gap surfaces, implement that gap directly on Laravel's queue instead of importing the bundle.
Weaver
How can I help you explore Laravel packages today?