- Is etrias/async-bundle a Laravel package?
- No. It is a Symfony bundle for asynchronous task processing, not a Laravel package. Symfony bundles rely on the Symfony kernel, dependency injection container, and bundle registration, which do not map cleanly onto Laravel service providers and queues. For a Laravel application, this package is out of scope.
- Can I use etrias/async-bundle with Laravel queues?
- There is no clean integration with Laravel queues. Laravel has its own job, queue worker, Horizon, and scheduler abstractions, while this bundle assumes Symfony bundle conventions. Bridging the two async models would require custom glue code and would add high maintenance risk. Use Laravel's native queue and scheduler features instead.
- How do I install and configure etrias/async-bundle?
- It can technically be installed with Composer and registered in a Symfony kernel, but the repository is deprecated and archived. There is no supported Laravel configuration because it is not a Laravel package. For new development, do not install it; adopt Symfony Messenger and Scheduler directly on Symfony, or Laravel queues and the scheduler on Laravel.
- Why is etrias/async-bundle deprecated?
- Its own README marks it as deprecated and points to symfony/messenger and symfony/scheduler as replacements. Those first-party Symfony components now cover message handling, transports, retries, and recurring tasks with ongoing maintenance. Adopting this bundle means building on a component its author explicitly says not to use.
- What Laravel versions does etrias/async-bundle support?
- None. This is a Symfony bundle, so there is no Laravel version support matrix and no Laravel integration. If you are evaluating it for a Laravel application, the correct choice is Laravel's queue system, Horizon, and scheduler rather than this package.
- What Symfony versions does etrias/async-bundle support?
- There is no supported PHP or Symfony version matrix going forward. The last release was in November 2022, which corresponds roughly to the Symfony 5.4 and 6.1 era, and the repository is archived. Any compatibility claim you make today will become stale at the next framework minor release.
- What are the best alternatives to etrias/async-bundle for Laravel?
- For Laravel, use native queues with Redis, database, or SQS transports, plus Laravel Horizon for monitoring and Laravel's scheduler for recurring tasks. Jobs, events, listeners, and queue workers cover most asynchronous processing needs. If the target stack is Symfony, use symfony/messenger for messages and symfony/scheduler for recurring tasks.
- Is etrias/async-bundle maintained and safe for production?
- No. The repository is archived, has zero stars and dependents, and has had no releases since November 2022. There is no maintainer, no issue triage, no security response process, and no PHP or Symfony compatibility updates. The permissive Apache-2.0 license is the only favorable signal, but it does not offset the maintenance and security risk.
- How do I migrate off etrias/async-bundle?
- Inventory the message and handler classes the bundle backs, then map each to a Symfony Messenger message and handler. Move recurring tasks to Scheduler's RecurringMessage and cut over transport by transport behind feature flags. Treat removal as planned technical debt rather than layering new features on top of the deprecated bundle.
- How do I test code that depends on etrias/async-bundle?
- There are no maintained test utilities or documented testing support for this archived bundle. Isolate legacy usage behind your own adapter or interface and write integration tests around message dispatch, handling, retries, and scheduling behavior. After migration, test directly against Symfony Messenger and Scheduler or Laravel's queue and scheduler APIs.