<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Queues on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/queues/</link>
    <description>Recent content in Queues on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 20 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/queues/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>PHP Job Queues in 2026: Laravel Horizon vs Symfony Messenger vs Enqueue — Which One Should You Actually Use?</title>
      <link>https://www.pistack.xyz/posts/2026-09-20-php-job-queues-laravel-horizon-symfony-messenger-enqueue-comparison/</link>
      <pubDate>Sun, 20 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-09-20-php-job-queues-laravel-horizon-symfony-messenger-enqueue-comparison/</guid>
      <description>&lt;p&gt;Your queue works fine until the day a job silently fails three thousand times in a row and nobody notices, because your only monitoring is a &lt;code&gt;jobs&lt;/code&gt; table with a growing count. The three real options in the PHP ecosystem take fundamentally different positions: Laravel Horizon bets you already chose Redis and Laravel, Symfony Messenger bets you want a framework-agnostic message bus with pluggable transports, and Enqueue bets you want to talk to seven different brokers through one interface.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
