- Can I use hautelook/gearman-bundle in a Laravel application?
- No, not directly. hautelook/gearman-bundle is a Symfony2 bundle that registers a dependency injection service for submitting Gearman jobs; Laravel consumes Symfony components, not Symfony bundles. Making it work would require extracting or reimplementing its service and wrapping it in a Laravel service provider, which leaves little value from the bundle itself.
- Is hautelook/gearman-bundle compatible with Laravel 10 or Laravel 11?
- No. The bundle targets Symfony2-era APIs and PHP versions that predate modern Laravel, which requires PHP 8.1 or newer on Laravel 10 and 11. Its DI container conventions and Symfony bundle structure do not map onto Laravel's service container, and you should expect conflicts with the Symfony components Laravel already ships. Pinning or vendoring the package would not make it a supported Laravel integration.
- How do I install hautelook/gearman-bundle with Composer in Laravel?
- You can run composer require hautelook/gearman-bundle, but Composer installation alone will not make it usable in Laravel. The package expects Symfony bundle registration and configuration, and Laravel has no equivalent bundle bootstrapping. You would still need to install and run gearmand, install the pecl gearman extension, and write a Laravel service provider around the underlying client classes.
- What does hautelook/gearman-bundle actually do?
- It is a Symfony2 bundle that provides a DI service for submitting jobs to a Gearman job server. The blurb describes background workers, asynchronous job dispatch, and queue management through Symfony services and configuration. In practice it is a thin configuration and service wrapper around Gearman's PHP client, and it assumes a running gearmand daemon plus the pecl gearman extension.
- What are the best Gearman alternatives for Laravel queues?
- Laravel's built-in queue system supports Redis, Amazon SQS, the database, and Beanstalkd, with retries, backoff, failed-job storage, and Horizon observability for Redis. For most Laravel workloads these drivers replace Gearman entirely and avoid running a separate job server. If you need synchronous RPC-style calls, consider HTTP or a dedicated RPC layer rather than adding Gearman alongside Laravel queues.
- Do I need the pecl gearman extension to use this package?
- Yes. The bundle depends on Gearman's PHP client, which is provided by the pecl gearman C extension, and it also expects a running gearmand server. That means build tooling in your runtime images and platform-specific extension builds, which is painful on Fargate, serverless, and other minimal PHP images. Without the extension the bundle's service cannot submit jobs.
- Is Gearman still maintained and safe for Laravel production use?
- Gearman is effectively unmaintained, with its last meaningful release around 2017, and the pecl extension has a history of instability and build issues on modern PHP. Running it in production means owning gearmand operations, extension builds, and monitoring outside Laravel's queue tooling. For a new Laravel project, use Redis, SQS, or database queues instead of introducing Gearman.
- Does hautelook/gearman-bundle support Laravel Horizon or failed job handling?
- No. Horizon, failed_jobs, queue:work, and Laravel's retry and backoff semantics are part of Illuminate\Queue, and Gearman sits outside that ecosystem. The bundle has no native Laravel queue driver, no Horizon integration, and no failed-jobs table integration. Adopting it means running a second, parallel job system with separate monitoring and failure handling.
- Is hautelook/gearman-bundle actively maintained and used in production?
- There is no meaningful community validation: the package has 0 stars, 0 dependents, and no active maintainer signal. Symfony2 reached end of life with its last 2.x release in 2018, so the bundle's conventions and PHP assumptions are outdated. Treat it as unmaintained and unsuitable for new Laravel production work.
- How would I migrate from Gearman to Laravel queues?
- Map each Gearman job type to a Laravel job class and dispatch it with the Redis, SQS, or database queue driver, preserving retries, backoff, and failed-job handling through Laravel's queue system. If Gearman is a hard short-term constraint, write a small Laravel service provider that exposes a GearmanClient singleton and wrap submissions, then swap that wrapper for Queue::push during the port. Doing the mapping during the initial migration is cheaper than adapting the EOL Symfony2 bundle and later unwinding it.