- What is sammyjo20/laravel-chunkable-jobs used for in Laravel?
- It is an orchestration layer over Laravel's native queue that splits a large queued job into smaller per-chunk child jobs. Each chunk is dispatched separately, and the package tracks completion so a finished hook can fire once all chunks are done. It reuses your existing queue workers and failed-job infrastructure rather than adding a new execution engine.
- How do I install Laravel Chunkable Jobs with Composer?
- Install it with Composer using composer require sammyjo20/laravel-chunkable-jobs. Adoption is composer-only plus a trait and a chunk-size property on the job class. The assessment notes there is no database migration, no required config publish, and no new infrastructure.
- Does laravel-chunkable-jobs require database migrations or config publishing?
- No. The package is described as composer-only with no database migration and no config publish requirement. You add the chunkable trait and chunk-size declaration to the job class, and the dispatch site is largely unchanged. That makes migration additive rather than a schema or infrastructure rewrite.
- How do I convert an existing Laravel job into a chunkable job?
- Add the chunkable trait and declare a chunk size on the existing job class, then extract the loop from the monolithic job into a chunk handler. The dispatch site is largely unchanged, but that extraction is the real migration work. There is no data migration or schema change.
- Which Laravel and PHP versions does laravel-chunkable-jobs support?
- Version 1.1.0 adds Laravel 11 and PHP 8.3 support, which removes the compatibility exception that would otherwise block adoption on newer services. Laravel 10 services should adopt with low friction. Services on Laravel 8 or 9 should verify the package's lower Composer constraint before assuming v1.1.0 is a drop-in upgrade, because the release note only advertises the upper bound being raised.
- Is Laravel Chunkable Jobs safe to use in production?
- It can fit production use because it reuses Laravel's queue, worker pool, and failed-job infrastructure, but the dominant risk is that it is a single-maintainer dependency. Chunk-level idempotency is your responsibility, and partial completion is a normal state, so chunk handlers must be safe to run twice. The assessment also says chunk progress state and its durability across restarts, including a Redis or cache flush, must be confirmed against the package source. It recommends a staging spike on one low-risk slow batch job, measuring chunk overhead and confirming state durability before pinning it on a non-critical service.
- What happens when a chunk fails or a chunked job is cancelled?
- The assessment flags failure and cancellation semantics as untested edge behaviour and the area most likely to surprise you. It does not establish whether remaining chunks continue after a permanent chunk failure, how that failure is surfaced, or whether there is a supported cancellation path for an in-flight chunked job. Test these cases explicitly in staging and inspect the package source and CI coverage before relying on them.
- Are chunk jobs idempotent and safe to retry?
- The package cannot guarantee chunk-level idempotency for you. Chunked execution means partial completion is normal, and queue retries can re-run a chunk, so any chunk handler must be safe to run twice. Design your handler around idempotent operations rather than assuming exactly-once execution.
- How does laravel-chunkable-jobs compare to Laravel job batching?
- It sits between plain dispatch, which has no parallelism or resumability, and full Laravel job batching, which requires constructing batches explicitly at the call site. Choose Chunkable Jobs when you want to reuse the existing queue and split a workload into per-chunk child jobs with completion tracking, without building batches yourself. If your requirements center on explicit batch construction and batch-level APIs, native Laravel batching may be a better fit.
- Is laravel-chunkable-jobs actively maintained and what are the risks?
- The package is authored and released by one individual, with two releases, v1.0.0 and v1.1.0, so bus factor is the dominant risk rather than code quality. The v1.1.0 headline change is framework and runtime compatibility, which suggests a stable feature surface but also maintenance mode rather than active development. The assessment also raises whether CI coverage against Laravel 11 and PHP 8.3 exists or support is merely declared. Confirm the maintainer's support policy, expected issue response time, and CI coverage before adopting it broadly.