Weave Code
Symfony Messenger Laravel Package
bref/symfony-messenger
Bridge for running Symfony Messenger on AWS Lambda with Bref. Dispatch messages to SQS, SNS, or EventBridge and let Lambda workers consume them, with setup documented on the Bref website.
Bridge to use Symfony Messenger on AWS Lambda with Bref
Frequently asked questions about Symfony Messenger
- What is bref/symfony-messenger used for?
- It is a Bref bridge that lets Symfony Messenger dispatch messages to SQS, SNS, or EventBridge and run Lambda workers that consume those messages. The package wires Messenger transports to AWS Lambda event sources and provides the consumer-side runtime for Lambda invocations. It is not a general Laravel queue package; it is specifically for Symfony Messenger on AWS Lambda.
- Does bref/symfony-messenger work with Laravel?
- Not as a natural fit. Laravel uses Illuminate\Queue rather than Symfony Messenger, and bref/laravel-bridge already covers the Lambda queue-worker case for Laravel's own queue system. Adopting this package in a Laravel app means adding a second messaging abstraction alongside Laravel's dispatcher, which is a real architectural cost rather than a drop-in.
- How do I install bref/symfony-messenger?
- Install it with composer require bref/symfony-messenger, then configure Symfony Messenger transports and Bref/Serverless event-source mappings. You also need Bref v2, a PHP 8.1 runtime layer, and the IAM roles and DLQ policies for your SQS, SNS, or EventBridge sources. The setup documentation lives on the Bref website rather than in the repository.
- Which AWS services can I use with Symfony Messenger on Lambda?
- The bridge supports dispatching messages to SQS, SNS, and EventBridge, with Lambda workers consuming them. That makes it relevant when you need SNS or EventBridge fan-out semantics rather than a single queue. For simple Laravel queue jobs, native SQS via Laravel's queue driver plus bref/laravel-bridge is usually simpler.
- What are the requirements for bref/symfony-messenger?
- You need Bref v2, a PHP 8.1 runtime layer, Symfony Messenger with transport configuration, and serverless.yml event-source mappings. The package itself is thin; most operational weight sits in the Serverless/Bref configuration, IAM roles, and DLQ policies. Plan for that configuration work as part of adoption.
- Is bref/symfony-messenger production ready and maintained?
- Treat adoption signal carefully: the package has around 72 stars, zero dependents, and a composite score of 26.79, which suggests an internal extraction published for the Bref documentation path rather than a battle-tested community library. Bref is effectively a single-maintainer project, so this bridge inherits that bus factor and documentation drift risk because docs live on bref.sh. The last release date is recent, but a single release cadence is not a support guarantee; assess whether you can vendor or fork the small bridge.
- How does bref/symfony-messenger compare to bref/laravel-bridge?
- bref/laravel-bridge is the recommended default for Laravel because it supports Laravel's native queue abstraction and SQS driver on Lambda. bref/symfony-messenger is for Symfony Messenger transports and consumer runtime, so it fits Symfony services or a Laravel app that deliberately adopted Messenger as an event bus. The second abstraction is only justified by a specific Messenger capability such as middleware, routing, SNS/EventBridge fan-out, or shared message contracts.
- How do I configure serverless.yml for Symfony Messenger on Lambda?
- You map Lambda event sources to your Messenger transports in serverless.yml and attach the required IAM roles and DLQ policies. The exact Bref configuration is documented on bref.sh, alongside Symfony Messenger transport setup. Keep the Serverless/IAM/DLQ ownership explicit, because that is where most operational risk sits.
- What serialization risks should I check with Symfony Messenger on Lambda?
- Messenger's default PhpSerializer is a deserialization attack surface if any transport boundary is untrusted. Make the serializer an explicit decision, for example a JSON or Symfony Serializer setup via Symfony\Component\Messenger\Transport\Serialization\Serializer. Review every SQS, SNS, and EventBridge boundary to decide who can publish messages and what contract is accepted.
- How do I test or verify Symfony Messenger compatibility before deploying?
- Verify the Symfony Messenger major you pin against the bridge, because Messenger has a fast major cadence and the compatibility matrix must be rechecked at every major. Test handlers and transport configuration locally with Symfony's Messenger tooling, then validate the Bref/Lambda integration, serialization, IAM, and DLQ behavior in a deployed environment. Also pin the PHP runtime layer and assign ownership for upgrades.
Weaver
How can I help you explore Laravel packages today?