<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Message Queues on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/message-queues/</link><description>Recent content in Message Queues on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 15 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/message-queues/index.xml" rel="self" type="application/rss+xml"/><item><title>Decoupling Services with Message Queues and Asynchronous Workflows</title><link>https://ai-blog.noorshomelab.dev/systems-engineering-2026/message-queues-async-workflows/</link><pubDate>Fri, 15 May 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/systems-engineering-2026/message-queues-async-workflows/</guid><description>&lt;h2 id="introduction-breaking-free-from-tight-coupling"&gt;Introduction: Breaking Free from Tight Coupling&lt;/h2&gt;
&lt;p&gt;Imagine a bustling restaurant where every customer order is taken by a chef directly, cooked immediately, and then the chef waits for the customer to finish before taking the next order. This is what synchronous, tightly coupled services often feel like in a software system. If one chef is busy or sick, the whole kitchen grinds to a halt. Not very efficient or resilient, right?&lt;/p&gt;</description></item></channel></rss>