- Is genhoi/humus-amqp-bundle compatible with Laravel?
- No. It is a Symfony bundle built around a Symfony DI extension, configuration tree, compiler passes, and console commands, so a Laravel application cannot consume its main value. In Laravel you would be integrating the underlying humus-amqp library yourself and writing your own service provider and worker command. For Laravel RabbitMQ work, use a Laravel-native connector or package instead.
- How do I install genhoi/humus-amqp-bundle?
- Install it with Composer and enable the bundle in your Symfony kernel, then configure brokers, exchanges, queues, producers, and consumers in YAML or XML. You must also install and enable the ext-amqp PECL extension, because the bundle wraps humus-amqp, which depends on it. Check the package composer.json for PHP and Symfony version constraints before installing. It is not installed as a Laravel package.
- What PHP extension does humus-amqp-bundle require?
- It requires ext-amqp, the PECL C extension that binds to librabbitmq. That extension must be compiled or installed in every runtime image, including local, CI, staging, and production. Alpine, Lambda, and some managed runtimes make this difficult or impossible without custom builds. Extension release cadence can also limit your PHP upgrade path.
- Can I use genhoi/humus-amqp-bundle with Symfony Messenger?
- They are separate approaches rather than complementary layers. Symfony Messenger ships a first-party AMQP transport using php-amqplib, and for most Symfony applications that is the maintained path with documented retry and failure handling. HumusAmqpBundle is an alternative that trades first-party support for raw throughput via ext-amqp. Running both would create two parallel messaging stacks with duplicated supervision and retry semantics.
- What are the best alternatives to humus-amqp-bundle for Laravel?
- For Laravel, use a Laravel-native RabbitMQ queue connector such as vladimir-yuldashev/laravel-queue-rabbitmq, or write a custom connector over php-amqplib. That keeps jobs inside Laravel's queue abstraction, queue:work lifecycle, failed-job table, and Horizon observability. On Symfony, Symfony Messenger's AMQP transport is the first-party alternative. Avoid adopting a Symfony bundle into a Laravel stack.
- How do I configure exchanges and queues in genhoi/humus-amqp-bundle?
- You define brokers, exchanges, queues, producers, and consumers declaratively in YAML or XML bundle configuration. Symfony's DI container wires the configured services together, so no boilerplate connection code is needed. Producers publish messages and consumers process them, with pluggable serializers and message conversion. Exact configuration keys depend on your installed bundle version, so check its documentation.
- How do I run long-lived consumers with humus-amqp-bundle?
- The bundle integrates with Symfony console commands to run consumers as long-lived worker processes. You supervise those processes with your normal process manager, such as Supervisor or systemd. Because they are Symfony commands, they live outside Laravel's queue:work lifecycle, retry semantics, and Horizon coverage. That duplication is a key reason not to mix it into a Laravel application.
- Does genhoi/humus-amqp-bundle support RPC over AMQP?
- Yes, the bundle includes built-in RPC client and server helpers over AMQP. It also supports declarative producers and consumers with annotation support, plus pluggable serializers and message conversion. These features are exposed through Symfony configuration and DI services. In Laravel you would not get that wiring without bypassing the bundle entirely.
- Is genhoi/humus-amqp-bundle actively maintained?
- Adoption is very low: roughly 3 GitHub stars, no dependents, and a single maintainer. A March 2024 release suggests some activity, but there is no upstream SLA or large community. Read composer.json for PHP, Symfony, and ext-amqp constraints rather than assuming compatibility. Treat bus factor and abandonment risk as high.
- Can I run humus-amqp-bundle in Docker, Alpine, or serverless?
- It depends on ext-amqp, which must be compiled against librabbitmq in each image. Alpine and serverless platforms often make that painful or impossible without a custom build. If you cannot guarantee the extension reproducibly across local, CI, staging, and production, do not adopt it. That extension gate applies even before Symfony or Laravel compatibility.