Weave Code
Symfony Messenger Queue Notifications Bundle Laravel Package
halloverden/symfony-messenger-queue-notifications-bundle
Symfony bundle for sending notifications through Messenger queues. Dispatch notification messages asynchronously and process them with workers via your configured transports, keeping your application responsive. Simple integration with Symfony Messenger for queued notification delivery.
Symfony messenger queue notifications
Frequently asked questions about Symfony Messenger Queue Notifications Bundle
- What is halloverden/symfony-messenger-queue-notifications-bundle?
- It is a Symfony bundle that dispatches notification messages through Symfony Messenger queues so workers can process them asynchronously. It integrates with Symfony's bundle registration and DI config rather than Laravel's service providers. The goal is to keep the request cycle responsive by moving notification delivery to a Messenger transport and worker.
- Can I use this Symfony Messenger notifications bundle in Laravel?
- No, not directly. It is a Symfony bundle and will not boot in a Laravel application because Laravel has no bundle concept and uses service providers, config files, and Illuminate Queue instead. You could install symfony/messenger standalone, but you would run two queue systems with separate retry and failure semantics. The practical option is to port the pattern to Laravel's native queued notifications.
- How do I install halloverden/symfony-messenger-queue-notifications-bundle?
- Install it with Composer using composer require halloverden/symfony-messenger-queue-notifications-bundle. Then register the bundle in your Symfony Kernel or bundles.php depending on your Symfony version. You also need symfony/messenger installed and a transport configured for the notification messages. Verify PHP and Symfony version constraints before installing because they are not clearly documented.
- Which Symfony and PHP versions does this bundle support?
- The provided repository details do not state PHP or Symfony version constraints, so compatibility is unknown. Before adopting it, check composer.json for require entries and test against Symfony 6.4 LTS or 7.x if that is your target. A missing or loose constraint makes dependency resolution against an existing Symfony application unpredictable.
- Does this bundle support Laravel's ShouldQueue notifications?
- No. Laravel's ShouldQueue interface and Notification::route are part of Illuminate Notifications, while this bundle targets Symfony Messenger message routing and handlers. The concepts are similar but the implementations are separate. In Laravel, implement ShouldQueue on your notification class and let Laravel's queue worker handle delivery.
- Which Messenger transports can I use for queued notifications?
- The bundle delegates transport handling to Symfony Messenger, so it should work with whatever transports Messenger supports, such as AMQP, Redis, Doctrine, or the synchronous transport for local testing. The repository does not document a preferred transport. For production, choose a durable transport and run dedicated workers.
- Does it handle retries and failed notification messages?
- The bundle does not document retry or failure-transport behavior in the provided details. Symfony Messenger provides retry configuration and a failure transport at the Messenger level, so you would configure those in messenger.yaml. Confirm whether the bundle adds any custom failure handling before relying on it in production.
- How do I test queued notifications with this bundle?
- For Symfony, use Messenger's in-memory transport or the sync transport in the test environment and assert that the expected message was dispatched. You can also inspect the message bus with a test transport. For Laravel, the equivalent is Notification::fake and assertQueued or assertSent.
- Is this bundle safe for production use?
- Treat it with caution. It has zero stars, zero dependents, no documented CI or test coverage, and no clear release cadence, so there is little ecosystem validation. The bus factor appears to be one. If you use it, pin the version, review the source, and have a fork or replacement plan.
- What is the Laravel alternative to this Symfony bundle?
- Use Laravel's native queued notifications: create a notification class that implements ShouldQueue, define via channels, and dispatch it with Notification::route or notify. Laravel's queue workers, retries, and failed_jobs table give you the same asynchronous delivery pattern without a Symfony dependency. This is the recommended approach for Laravel applications.
Weaver
How can I help you explore Laravel packages today?