Laravel Queue Backpressure & Dead-Letter Patterns | Mohamed Said [ ![Mohamed Said](https://cdn.msaied.com/01KT78WE565VEMM3PSNQAAB0MH.png) Mohamed Said Laravel Backend Engineer ](https://msaied.com) [ Home ](https://msaied.com) [ Projects ](https://msaied.com/projects) [ Articles ](https://msaied.com/articles) [ Certificates ](https://msaied.com/certificates) [ Contact ](https://msaied.com#contact-section) [ ](https://github.com/EG-Mohamed) [ Home ](https://msaied.com) [ Projects ](https://msaied.com/projects) [ Articles ](https://msaied.com/articles) [ Certificates ](https://msaied.com/certificates) [ Contact ](https://msaied.com#contact-section) [ home ](https://msaied.com) [ articles ](https://msaied.com/articles) Laravel Queues at Scale: Backpressure, Dead-Letter Patterns, and Job Observability On this page 1. [ The Problem Nobody Talks About ](#the-problem-nobody-talks-about) 2. [ Backpressure: Slowing the Producer ](#backpressure-slowing-the-producer) 3. [ Dead-Letter Queues Without a Broker ](#dead-letter-queues-without-a-broker) 4. [ Structured Job Observability ](#structured-job-observability) 5. [ Key Takeaways ](#key-takeaways) ![Laravel Queues at Scale: Backpressure, Dead-Letter Patterns, and Job Observability](https://cdn.msaied.com/484/7ee0710bfc61c6ff7667dd4f60a8c5bd.png) #laravel #queues #observability #production Laravel Queues at Scale: Backpressure, Dead-Letter Patterns, and Job Observability ==================================================================================== 29 Jul 2026 3 min read ![Mohamed Said](https://cdn.msaied.com/01M22N44A70A5MC2S599JP0MPH.webp) Mohamed Said Table of contents 1. [ 01 The Problem Nobody Talks About ](#the-problem-nobody-talks-about) 2. [ 02 Backpressure: Slowing the Producer ](#backpressure-slowing-the-producer) 3. [ 03 Dead-Letter Queues Without a Broker ](#dead-letter-queues-without-a-broker) 4. [ 04 Structured Job Observability ](#structured-job-observability) 5. [ 05 Key Takeaways ](#key-takeaways) The Problem Nobody Talks About ------------------------------ Most Laravel queue tutorials stop at `dispatch()` and `php artisan queue:work`. In production, the real challenges are: what happens when consumers fall behind producers, how do you safely handle poison-pill jobs, and how do you get meaningful signals out of your workers without drowning in noise? This article addresses all three. --- Backpressure: Slowing the Producer ---------------------------------- Backpressure means the consumer signals the producer to slow down when it cannot keep up. Laravel has no built-in backpressure primitive, but you can build one cheaply with Redis and a rate-aware dispatcher. ```php // app/Queue/BackpressureDispatcher.php final class BackpressureDispatcher { private const THRESHOLD = 5_000; public function __construct( private readonly Redis $redis, private readonly string $queue = 'default', ) {} public function dispatch(ShouldQueue $job): void { $depth = (int) $this->redis->llen('queues:' . $this->queue); if ($depth >= self::THRESHOLD) { throw new QueueSaturatedException( "Queue [{$this->queue}] depth {$depth} exceeds threshold." ); } dispatch($job)->onQueue($this->queue); } } ``` The caller catches `QueueSaturatedException` and either retries with exponential back-off or returns a `202 Accepted` with a `Retry-After` header. This keeps your queue depth bounded without dropping work. --- Dead-Letter Queues Without a Broker ----------------------------------- Laravel's `failed_jobs` table is a dead-letter store, but it lacks routing. A better pattern is a dedicated `dead-letter` queue that jobs are explicitly moved to after exhausting retries, preserving the original payload and failure context. ```php // app/Jobs/Concerns/RoutesToDeadLetter.php trait RoutesToDeadLetter { public function failed(Throwable $e): void { DeadLetterJob::dispatch( originalJob: static::class, payload: serialize($this), reason: $e->getMessage(), failedAt: now(), )->onQueue('dead-letter'); } } ``` ```php // app/Jobs/DeadLetterJob.php final class DeadLetterJob implements ShouldQueue { public int $tries = 1; public function __construct( public readonly string $originalJob, public readonly string $payload, public readonly string $reason, public readonly Carbon $failedAt, ) {} public function handle(): void { // Persist to dead_letter_events table for audit + replay UI DeadLetterEvent::create([ 'job' => $this->originalJob, 'payload' => $this->payload, 'reason' => $this->reason, 'failed_at' => $this->failedAt, ]); } } ``` A Filament resource over `dead_letter_events` gives ops teams a replay button without touching `artisan queue:retry`. --- Structured Job Observability ---------------------------- Log lines are noise. Structured spans are signal. Use Laravel's `Queue::before` and `Queue::after` hooks to emit consistent telemetry. ```php // app/Providers/QueueServiceProvider.php public function boot(): void { Queue::before(function (JobProcessing $event) { $this->startTimer($event->job->getJobId()); }); Queue::after(function (JobProcessed $event) { $elapsed = $this->stopTimer($event->job->getJobId()); Log::channel('structured')->info('job.processed', [ 'job' => $event->job->resolveName(), 'queue' => $event->job->getQueue(), 'duration_ms' => $elapsed, 'attempts' => $event->job->attempts(), 'connection' => $event->connectionName, ]); }); Queue::failing(function (JobFailed $event) { Log::channel('structured')->error('job.failed', [ 'job' => $event->job->resolveName(), 'error' => $event->exception->getMessage(), 'attempts' => $event->job->attempts(), ]); }); } ``` Pipe the `structured` channel to a JSON log driver and ingest into your observability stack (Grafana Loki, Datadog, etc.). You now have p95 job latency per class without a paid APM agent. --- Key Takeaways ------------- - **Backpressure** is a producer responsibility — check queue depth before dispatching and surface `Retry-After` to callers. - **Dead-letter queues** should be first-class entities with a replay UI, not a graveyard in `failed_jobs`. - **Structured telemetry** from `Queue::before/after` hooks gives you latency histograms and failure rates per job class for free. - Keep `$tries` low (2–3) and `$backoff` exponential; long retry chains mask systemic failures. - A dedicated `dead-letter` queue worker with a single process prevents replay storms from starving production queues. Found this useful? [ ](https://twitter.com/intent/tweet?url=https%3A%2F%2Fmsaied.com%2Farticles%2Flaravel-queues-at-scale-backpressure-dead-letter-patterns-and-job-observability&text=Laravel+Queues+at+Scale%3A+Backpressure%2C+Dead-Letter+Patterns%2C+and+Job+Observability) [ ](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fmsaied.com%2Farticles%2Flaravel-queues-at-scale-backpressure-dead-letter-patterns-and-job-observability) Frequently Asked Questions ---------------------------- 3 questions Q01 Should I use a real message broker like RabbitMQ instead of building these patterns in Laravel? For most SaaS workloads, Redis-backed Laravel queues with explicit backpressure and dead-letter routing are sufficient and far simpler to operate. Reach for a broker when you need multi-consumer fan-out, cross-service routing, or guaranteed ordering across partitions — not just because your queue is busy. Q02 How do I replay jobs from the dead-letter table without re-queuing poison pills? Deserialize the stored payload, inspect it, optionally patch it, then dispatch a fresh instance. Add a `replayed_from` metadata field so you can detect replay loops and halt after a configurable number of replay attempts per original job ID. Q03 Does checking queue depth on every dispatch add meaningful latency? An Redis LLEN call is a single O(1) command, typically sub-millisecond on a local or same-datacenter Redis. Cache the result for 500ms with an in-memory static property if you dispatch in tight loops. Continue reading More Articles --------------- [ View all ](https://msaied.com/articles) [ ![Partial Indexes and Covering Indexes in PostgreSQL: A Laravel Developer's Guide](https://cdn.msaied.com/665/ced6904aad758906b6047d70ea25e267.png) postgresql laravel performance ### Partial Indexes and Covering Indexes in PostgreSQL: A Laravel Developer's Guide Learn how partial and covering indexes eliminate wasted index space and redundant heap fetches in Laravel apps... ![Mohamed Said](https://cdn.msaied.com/01M22N44A70A5MC2S599JP0MPH.webp) Mohamed Said 13 Sep 2026 4 min read Read ](https://msaied.com/articles/partial-indexes-and-covering-indexes-in-postgresql-a-laravel-developers-guide-1) [ ![Filament v4 at Scale: Multi-Panel Auth, Custom Panels, and Table Query Tuning](https://cdn.msaied.com/664/be327447c5231a3cb27a5df9597890dd.png) filament laravel multi-panel ### Filament v4 at Scale: Multi-Panel Auth, Custom Panels, and Table Query Tuning Running Filament v4 across multiple panels with distinct auth guards and thousands of rows? This guide covers... ![Mohamed Said](https://cdn.msaied.com/01M22N44A70A5MC2S599JP0MPH.webp) Mohamed Said 13 Sep 2026 3 min read Read ](https://msaied.com/articles/filament-v4-at-scale-multi-panel-auth-custom-panels-and-table-query-tuning) [ ![Macros, Mixins, and Custom Collection Methods in Laravel](https://cdn.msaied.com/663/b8e39b17d427358aa43b5c3e8c1be908.png) laravel collections macros ### Macros, Mixins, and Custom Collection Methods in Laravel Learn how to extend Laravel's core classes with macros, mixins, and custom Collection methods — keeping your c... ![Mohamed Said](https://cdn.msaied.com/01M22N44A70A5MC2S599JP0MPH.webp) Mohamed Said 13 Sep 2026 4 min read Read ](https://msaied.com/articles/macros-mixins-and-custom-collection-methods-in-laravel-2) [ ![Mohamed Said](https://cdn.msaied.com/01KT78WE565VEMM3PSNQAAB0MH.png) Mohamed Said Laravel Backend Engineer ](https://msaied.com)Senior Backend Engineer specializing in Laravel, scalable SaaS platforms, APIs, and cloud infrastructure. I build secure, high-performance web applications that help businesses grow. Explore - [Home](https://msaied.com) - [Projects](https://msaied.com/projects) - [Articles](https://msaied.com/articles) - [Certificates](https://msaied.com/certificates) - [Contact](https://msaied.com#contact-section) Connect - [ hello@msaied.com ](mailto:hello@msaied.com) - [ +20 109 461 9204 ](tel:+201094619204) © 2026 Mohamed Said. All rights reserved. [ ](https://github.com/EG-Mohamed) [ ](https://www.linkedin.com/in/msaiedm/) [ ](https://wa.me/201094619204) [ ](mailto:hello@msaied.com) [ ](https://drive.google.com/file/u/0/d/1MF20IPRJyzfy32mhEutjL5EpSls0w2Q8/view)