Laravel:queues And Horizon

Queues and Horizon

Run workers safely, verify execution, and test job behavior.

Commands

# Start worker
sail artisan queue:work --queue=high,default --tries=3 --backoff=5   # or: php artisan queue:work --queue=high,default --tries=3 --backoff=5

# Horizon (if installed)
sail artisan horizon                                               # or: php artisan horizon

# Failed jobs
sail artisan queue:failed                                          # or: php artisan queue:failed
sail artisan queue:retry all                                       # or: php artisan queue:retry all

Patterns

• Use named queues for prioritization; keep defaults sane
• Add actionable Log::warning/::error with context in jobs
• Idempotency: make jobs safe to retry
• Emit metrics where possible; observe in Horizon or your APM

Laravel 13+

# Centralized queue routing (e.g., in AppServiceProvider)
Queue::route(ProcessPodcast::class, connection: 'redis', queue: 'podcasts');

# Declarative job controls via attributes
use Illuminate\Queue\Attributes\{Tries, Backoff, Timeout, FailOnTimeout};

#[Tries(3)]
#[Backoff([10, 30, 60])]
#[Timeout(120)]
#[FailOnTimeout]
class ProcessPodcast implements ShouldQueue { /* ... */ }

# Graceful shutdown for long-running jobs
class ProcessPodcast implements ShouldQueue, Interruptible {
    public function onInterrupt(): void { /* release locks, save state */ }
}

# Auto-scaling friendly worker exit
sail artisan queue:work --stop-when-empty-for=60   # or: php artisan queue:work --stop-when-empty-for=60

• Prefer Queue::route() over per-dispatch onQueue() when routing is a policy, not a caller decision
• See laravel:php-attributes for the attribute-first style trade-offs

Testing Jobs

• Use Bus::fake() to assert dispatching in unit tests
• Use integration tests to verify side-effects (DB/IO)