🔗 My Laravel Horizon preferences after 5 years of using it

When working with Laravel Horizon, it’s easy to get started, run php artisan horizon, dispatch some jobs, monitor them in the dashboard, and you’re good to go. But as your application scales and the amount of jobs grow more complex, subtle issues begin to surface. The design of your jobs and configuration of Horizon and Redis must be correct in order to run Horizon without issues.

I've been working with Laravel Horizon for the past five years on Laravel applications that do 1M+ jobs per day. In this article, I’ll share what I’ve learned from working with Laravel Horizon for five years. Including how I prefer to design jobs; how I isolate queues to prevent bottlenecks; and most importantly, the hidden pitfalls of Horizon's configuration and how to avoid them. If you’ve ever had a job mysteriously fail to dispatch or vanish without explanation, read this article.

I've added a few code examples from my open source project, Vigilant. An all-in-one website monitoring application.