- Does micro-module/enqueue-bundle work with Laravel?
- No. It is a Symfony bundle, and its value sits in the Symfony integration layer: a DI extension, a configuration tree, console commands, event-dispatcher hooks, and a profiler panel. Laravel has no bundle registration mechanism and boots ServiceProvider classes instead, so none of that code ever loads in a Laravel application. The only reusable part is the framework-agnostic Enqueue transport layer underneath.
- Can I install a Symfony bundle in a Laravel project with Composer?
- You can require it with Composer, but Composer will not boot anything in Laravel. Without a bundle registration hook the container extension and services are never compiled, so producers, consumers, and processors stay unwired. Attempting to boot it inside Laravel's container produces a fragile adapter that fights both frameworks' lifecycles. Depend on the underlying transport clients instead.
- What does micro-module/enqueue-bundle actually do?
- It integrates php-enqueue messaging into modular Symfony applications, letting each micro-module define its own transport, producers, consumers, and processors through the Symfony DI container. Supported backends include AMQP, Redis, and other php-enqueue transports, with convention-based routing between modules and extensible service definitions for custom processors. The goal is to keep business logic decoupled from any specific broker.
- Which PHP and Symfony versions does micro-module/enqueue-bundle support?
- The package states no Laravel compatibility at all, and its supported PHP and Symfony matrix is whatever the upstream Enqueue Symfony bundle declares in composer.json. Inspect that file and the upstream CI configuration before assuming anything, and note that this release is a 2025-04-16 re-publication. There is no Laravel test matrix to inspect.
- How do I use Enqueue messaging in a Laravel app without this bundle?
- Require the specific transport client you need directly, such as the AMQP or SQS client from the enqueue family, and wire it into a thin Laravel service provider. Keep the abstraction narrow: instantiate the transport, expose a small publish method, and register a queued job or console command for consumption. Avoid importing the full Enqueue API surface, including RPC over MQ and async events, unless a concrete use case demands it.
- Is micro-module/enqueue-bundle safe to use in production?
- Treat it with caution. It has zero stars, zero dependents, a READ-ONLY prefix in its description, and a recent release date, all of which point to an automated mirror or re-publication pipeline rather than an independently maintained project. The READ-ONLY marker also means issues and pull requests are not accepted here, so there is no upstream-of-record for fixes. Message queues sit on the critical path for order processing and notifications, so a supply-chain question mark there is a serious finding.
- What are the alternatives to micro-module/enqueue-bundle for Laravel queues?
- Laravel's native queue abstraction with Redis, database, or SQS drivers covers most needs and is first-party maintained. If you specifically need a broker-agnostic abstraction, use the upstream php-enqueue transport packages or the Laravel-oriented integration from the same ecosystem, and leave this Symfony bundle out of the picture. Horizon adds monitoring and metrics on top of the native Redis queue driver.
- Can a Symfony producer and a Laravel consumer share the same queue?
- Yes in principle, provided both sides agree on the message envelope, headers, and serialization format. Enqueue wraps payloads in its own envelope, so a Laravel consumer must decode that structure rather than assuming a plain JSON body. Verify interoperability with an integration test against the real broker before committing to a hybrid architecture.
- Do I need the bundle if I only use AMQP or SQS?
- No. If you only need a single transport, the transport client alone is sufficient and considerably simpler. The bundle's added value is per-module configuration and DI wiring across many micro-modules in a Symfony application, which is exactly the part Laravel cannot use. Pull in the client, not the bundle.
- Is micro-module/enqueue-bundle a faithful mirror of the upstream Enqueue Symfony bundle?
- Unknown until you diff it. Compare this tagged release against the corresponding upstream Enqueue Symfony bundle tag to see whether it is byte-identical or carries patches. Check whether the release cadence tracks upstream tags or lags behind, and confirm which PHP and Symfony versions upstream CI actually tests. If it is a mirror, the trust boundary shifts to whoever operates the publishing pipeline, so ask for their compromise and rollback story before depending on it.