- Is psyllium/amqp a Laravel package or a Symfony bundle?
- The marketing description promises a Laravel-friendly AMQP wrapper, but the available technical evidence points to a Symfony bundle using Symfony dependency injection, config/bundles.php registration, and YAML config under config/packages/. That distinction is unverified and matters because it changes installation, configuration, and integration work. Treat the Laravel framing as a claim to validate, not a confirmed feature.
- How do I install psyllium/amqp in a Laravel app?
- If the package is available on Packagist, the usual composer require psyllium/amqp would apply, but the assessment flags that Composer resolution may require private Bitbucket VCS access instead. Check Packagist first; if it is not listed, configure a Composer VCS repository and plan for CI and production credentials. Also confirm that ext-amqp and librabbitmq-dev are available in your build and runtime images before installing.
- Does psyllium/amqp require the ext-amqp PHP extension?
- The technical assessment states the implementation is built on Psyllium and ext-amqp, which requires a PECL extension and librabbitmq-dev. There is no pure-PHP fallback indicated. If your platform images are managed, this becomes a platform-team request with lead time.
- Can psyllium/amqp integrate with Laravel queues, events, and workers?
- The description claims Laravel-friendly container bindings, but the evidence points to a Symfony bundle built on Psyllium and ext-amqp rather than a first-class Laravel queue driver. It does not appear to slot into Queue, Event, Broadcast, or the standard worker lifecycle without custom glue. Treat Laravel integration as unverified until a short technical spike confirms it.
- How do I configure RabbitMQ connections, vhosts, exchanges, and queues with psyllium/amqp?
- The overview describes connection and channel management with configurable credentials and vhosts, plus exchange and queue helpers for declaration, binding, and routing. However, the implementation evidence suggests Symfony-style service definitions and YAML configuration, not Laravel config files. Verify the actual configuration format before wiring it into a Laravel application.
- Does psyllium/amqp support publishing, consuming, acknowledgements, retries, and dead-letter queues?
- The overview lists publisher and consumer abstractions and extensible handling for serializers, acknowledgements, and retries. The assessment warns that reconnect, retry/backoff, dead-lettering, poison-message handling, prefetch, and graceful shutdown may be implemented, delegated, or absent. Confirm these behaviors with tests before relying on them in production.
- Which Laravel and PHP versions does psyllium/amqp support?
- The provided description does not include a support matrix for PHP, Laravel, Symfony, or Psyllium versions. The assessment explicitly flags this as a key question. Check composer.json constraints and test against your target Laravel version before committing.
- Is psyllium/amqp production-ready and actively maintained?
- There is no strong external signal: the assessment notes zero stars, zero dependents, and a composite score of 0, with a single Bitbucket vendor. Due diligence on license, security posture, test coverage, release cadence, and named maintainer should happen before a spike. Production readiness is high risk without that evidence.
- What are the alternatives to psyllium/amqp for RabbitMQ in Laravel?
- For Laravel applications, the default alternative is Laravel's first-class queue system, with Redis and Horizon for observability and failed-job handling. For RabbitMQ specifically, evaluate mature PHP AMQP clients and Laravel queue drivers rather than adopting an unverified thin wrapper. If Psyllium is already an approved internal standard, a narrow transport adapter may be acceptable.
- Can I install psyllium/amqp from Packagist, or do I need Bitbucket repository access?
- The repository is on Bitbucket under a single vendor, and the assessment warns that Packagist availability is unconfirmed. If Composer cannot resolve psyllium/amqp from Packagist, CI and production will need private VCS access and secrets management. Confirm license and internal-fork permissions before relying on that path.