Hi Laravel. Meet Go.
laravel-queue-go
> work your Laravel queues from Go
Your app keeps dispatching jobs the way it always has. A Go worker picks them up off the same Redis queue, with the same retries, backoff and failed-jobs table. No bridge service, no second queue.
// add it to your module
$ go get github.com/rjp2525/laravel-queue-go
// works alongside php artisan queue:work
const laravel = "10 | 11 | 12 | 13"
// app/Jobs/ResizeImage.php, dispatched like any other job
ResizeImage::dispatch($photo->id, 1600)
->onQueue('images');
// worker/main.go
mgr.Register(`App\Jobs\ResizeImage`, resizeImage)
func resizeImage(ctx context.Context, job *queue.Job) error {
photoID := job.GetInt("photoId")
width := job.GetInt("width")
// return an error and it retries with backoff
return resize(ctx, photoID, width)
}
worker := mgr.Worker(queue.WorkerOptions{
Queue: "images",
Concurrency: 8,
})
worker.Run(ctx)
Speaks Laravel's protocol exactly
Same Redis keys, same Lua scripts, same payload. Go and PHP workers can share one queue and neither can tell the other is there.
02 · retriesRetries behave like you expect
$tries, $backoff, retryUntil, $timeout and failOnTimeout mean the same thing in a Go handler as they do in handle().
Reads your job classes
PHP-serialized commands are decoded for you: scalars, arrays, enums and Eloquent model identifiers, behind typed accessors.
04 · versionsLaravel 10 through 13
Pin the version or let it be detected from the jobs already on the queue. Prefixes, payload keys and cluster key layout follow.
05 · workersBuilt for long-running workers
Bounded concurrency, graceful drain on shutdown, panic recovery, and jobs that are never silently dropped.
06 · both waysDispatch from Go too
Push jobs, delayed jobs and chains that queue:work runs as if Laravel had dispatched them itself.
// requirements
go 1.26+ · redis 6+ · laravel 10, 11, 12, 13 · queue driver redis