- Can I use mcfedr/sqs-queue-driver-bundle in Laravel?
- No. mcfedr/sqs-queue-driver-bundle is a Symfony bundle that registers through Symfony's bundles.php and DependencyInjection extension mechanism, and it exposes a Symfony Console worker command. Laravel has no bundle registration path, no ContainerBuilder compiler passes, and no Illuminate Contracts Queue implementation for this package. Wiring it in would require running a Symfony kernel inside Laravel or porting the worker and SQS logic into a Laravel-native connector.
- How do I install mcfedr/sqs-queue-driver-bundle?
- In a Symfony application you install it with Composer, enable the bundle in your kernel or bundles.php, then configure AWS credentials and the SQS queue it should consume. Do not expect it to install cleanly into a Laravel composer.json, because Symfony component version pins often collide with Laravel's own symfony transitive requirements. Check the package composer.json for declared Symfony and PHP constraints before attempting adoption.
- Which Symfony and PHP versions does this SQS bundle support?
- The repository metadata provided does not state the exact Symfony and PHP constraints, so inspect composer.json and the latest compatible release before adopting it. Because this is a Symfony bundle, its version lines will track Symfony rather than Laravel. Expect constraint conflicts if you try to force it into a Laravel project that already pins symfony console, http-foundation, finder, and related components.
- Does mcfedr/sqs-queue-driver-bundle support FIFO queues, deduplication IDs, and message groups?
- The package description only says it is an Amazon SQS queue driver, and the available metadata does not document FIFO, deduplication ID, or message group support. Those are production-critical semantics, so verify them with the maintainer or a spike before relying on this bundle. Laravel's first-party SQS driver already supports FIFO queues, deduplication IDs, deduplication groups, delayed dispatch, and queue prefixes.
- How does this bundle handle retries, visibility timeouts, and dead-letter queues?
- Those semantics are not answerable from the repository metadata provided, and each one maps directly to a production incident class. You need to confirm whether it long-polls with WaitTimeSeconds, deletes only on success, relies on SQS redelivery or its own retry counter, and whether poison messages go to a dead-letter queue or cycle indefinitely. Ask the maintainer or run a spike before putting it on the critical path of every background job.
- Is mcfedr/sqs-queue-driver-bundle production-ready for background jobs?
- The maturity signals are weak: 4 stars, 0 dependents, a score of 0.24, a single maintainer, and no visible release cadence or security process. A queue driver sits on the critical path for webhooks, order emails, and other money-impacting jobs, so no downstream production validation is disqualifying. For Laravel production workloads, use the native SQS driver unless you have a specific, verified gap.
- What is the difference between this bundle and Laravel's built-in SQS queue driver?
- Laravel ships Illuminate Queue SqsQueue backed by aws/aws-sdk-php, with FIFO support, deduplication IDs, delayed dispatch, visibility timeouts, and queue prefixes. This package is a Symfony DI and Console bundle with no ServiceProvider, no config queue connector contract, and no Laravel Queue implementation. On inspection, the marginal capability it offers over Laravel's first-party driver is close to zero, while the integration cost is high.
- How do I configure SQS as QUEUE_CONNECTION in Laravel?
- Install aws/aws-sdk-php, set QUEUE_CONNECTION=sqs in your environment, and configure the sqs connection in config/queue.php with your AWS key, secret, region, queue name, and optional prefix. Laravel's native driver then handles polling, visibility timeouts, job deletion, and failed-job behavior. mcfedr/sqs-queue-driver-bundle does not provide a Laravel connector, so it is not the package to use for this setup.
- Does this bundle implement Symfony Messenger transport contracts or its own worker loop?
- That is a key unresolved question: the repo metadata does not say whether it implements Symfony Messenger transport contracts or uses a bespoke worker loop. It does expose a Symfony Console worker command, but the internal retry, backoff, and failure semantics depend on which model it follows. Resolve this in a spike or with the maintainer before assuming Messenger-compatible behavior.
- What are the alternatives to mcfedr/sqs-queue-driver-bundle for SQS in PHP?
- For Laravel, the default recommendation is the native SQS driver with aws/aws-sdk-php, which is days of effort and low risk. For Symfony, evaluate Symfony Messenger's SQS transport or a maintained Symfony-specific bundle rather than forcing this package into Laravel. If you only need specific patterns, port them into a thin internal connector or JobMiddleware after verifying the retry, DLQ, and visibility-timeout behavior.