symfony/doctrine-messenger
Doctrine integration for Symfony Messenger. Store, dispatch, and consume messages using Doctrine-backed transports and tooling. Part of the Symfony ecosystem; issues and contributions go through the main Symfony repository.
This package is not designed for Laravel and should never be considered for Laravel-based products. As a Symfony-specific bridge, it conflicts with Laravel's architecture, service container, and native queue system. Product decisions around queueing in Laravel should prioritize Laravel's built-in database driver or Redis solutions, which are purpose-built for the framework and have full ecosystem support. Adopting this package would introduce significant technical debt, require rewriting core queue logic, and create unresolvable dependency conflicts between Symfony and Laravel components.
Only for Symfony applications where Doctrine is already in use and a database-backed message transport is required (e.g., avoiding external dependencies like RabbitMQ). Avoid entirely for Laravel projects due to:
Illuminate\Queue with database or redis drivers unless there is a specific, validated need for Symfony Messenger features (which is extremely rare in Laravel ecosystems)."This package is exclusively for Symfony applications and has zero compatibility with Laravel. For our current Laravel projects, using it would force us to abandon Laravel's native queue system, introduce dependency conflicts, and create unsustainable maintenance overhead. Our built-in database queue driver is optimized for Laravel, fully supported by the community, and requires no external dependencies. If we ever move to Symfony, this bridge would be a strong candidate—but for now, adopting it would be a high-risk distraction. Let's focus on leveraging Laravel's proven solutions to deliver features faster and with lower risk."
How can I help you explore Laravel packages today?