Weave Code
Symfony Azure Service Bus Messenger Bundle Laravel Package
halloverden/symfony-azure-service-bus-messenger-bundle
This Symfony bundle integrates Azure Service Bus with Symfony Messenger, providing a transport for sending and receiving messages via Azure queues or topics so Symfony apps can use Azure-backed asynchronous messaging.
Provides a Azure Service Bus transport for Symfony Messenger
Frequently asked questions about Symfony Azure Service Bus Messenger Bundle
- Is halloverden/symfony-azure-service-bus-messenger-bundle compatible with Laravel?
- No. It is a Symfony bundle that registers a transport with Symfony Messenger, while Laravel uses its own Illuminate\Contracts\Queue\Queue system with connectors registered through Queue::extend(). The two do not share an extension point, so you cannot drop this in as a Laravel queue driver. A Laravel team can read it as a reference or run it beside Laravel as a separate Symfony service.
- Can I install this Symfony Azure Service Bus bundle inside a Laravel application?
- Technically you can install symfony/messenger and the bundle alongside Laravel, but you would end up running two parallel messaging runtimes with separate workers, retry models, and failure handling. That doubles operational surface for no product gain, and Messenger's retry and failure-transport semantics do not map cleanly to Laravel's failed_jobs and retry_after behaviour. The recommended path is a native Laravel connector or a separate consumer service at the integration boundary.
- How do I use Azure Service Bus with Laravel without this bundle?
- Port the transport logic into a native Laravel queue connector, roughly 300 to 500 lines against the same Azure SDK, so dispatch(), failed_jobs, and Horizon keep working as your team expects. The bundle is most useful as a worked reference for Azure wire semantics: entity naming, peek-lock and settlement calls, lock renewal, dead-letter conventions, and header mapping. Budget one to two weeks for a read-and-port exercise.
- What does the Symfony Azure Service Bus Messenger Bundle actually provide?
- It integrates Azure Service Bus with Symfony Messenger, providing a transport for sending and consuming messages through Azure queues or topics. It includes bundle configuration via config and environment variables, message sending, receiving, and serialization, and works with existing Messenger middleware and handlers. It is not a Laravel queue driver and does not integrate with Illuminate queue workers.
- Does this bundle use AMQP 1.0 or REST polling to talk to Azure Service Bus?
- The context does not specify which Azure SDK or wire path the bundle uses, and that is the most important unknown in the evaluation. Azure Service Bus speaks AMQP 1.0, but ext-amqp is at 0.9.1 and incompatible, so many PHP clients fall back to REST polling. Whether this bundle polls over REST or uses an AMQP-capable client changes both delivery latency and your Azure per-operation bill.
- How does the bundle renew peek-lock for long-running Symfony Messenger handlers?
- The available context does not document lock-renewal behaviour or any max-lock guard. Azure Service Bus peek-lock expires unless it is renewed, so long-running handlers need explicit renewal and a guard against exceeding the maximum lock duration. This is a spike question: read the transport code and test a handler that runs longer than the lock period.
- Does it support Azure Service Bus sessions, scheduled messages, and dead-letter replay?
- The overview only promises queues, topics, sending, receiving, serialization, and Messenger middleware integration. It does not document sessions for ordered delivery, scheduled or deferred messages, transactions, batch receive, correlation filters on subscriptions, or programmatic dead-letter replay. Treat those as unverified and test each one against your requirements before committing.
- What are the alternatives to this bundle for Azure Service Bus in Laravel?
- The preferred alternative is a native Laravel queue connector built against the Azure SDK, which preserves dispatch(), failed_jobs, and Horizon. The fallback is to keep Laravel queues internal and run a small dedicated Symfony or PHP consumer and publisher service at the integration boundary. Installing this bundle directly inside Laravel is the option to reject because it adds a second messaging runtime.
- Is this package production-ready and actively maintained?
- The evaluation flags high risk: roughly 2 stars, 0 dependents, a score around 0.17, and effectively a single maintainer with no downstream projects to inherit fixes from. MIT licensing gives legal freedom but not continuity, and there is no production validation signal. If you adopt it, you are effectively underwriting the code yourself.
- How should I evaluate this bundle before using it in a Laravel project?
- Run a time-boxed spike: identify the Azure SDK and whether the wire path is AMQP or REST, measure p50 and p99 latency and messages per second per worker, and test lock renewal with a long-running handler. Also confirm the tested compatibility matrix for Symfony Messenger, PHP, and Azure SDK versions, and check whether dead-letter and poison-message paths can be observed in your existing dashboards. Do not commit until the cost model at target volume is clear.
Weaver
How can I help you explore Laravel packages today?