<?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 Compile My Mind</title>
		<link>https://www.compilemymind.com/tags/message-queues/</link>
		<description>Recent content in Message-Queues on Compile My Mind</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Wed, 07 Oct 2026 22:28:22 +0300</lastBuildDate>
		
			<atom:link href="https://www.compilemymind.com/tags/message-queues/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Message Queues Explained: How Asynchronous Systems Work</title>
				<link>https://www.compilemymind.com/posts/message-queues-explained/</link>
				<pubDate>Wed, 07 Oct 2026 22:28:22 +0300</pubDate>
				<guid>https://www.compilemymind.com/posts/message-queues-explained/</guid>
				<description>&lt;p&gt;A customer clicks &lt;strong&gt;Place order&lt;/strong&gt;. The payment succeeds, but generating the invoice takes 12 seconds and the email provider is having a bad afternoon. Should the browser wait for both jobs? Should checkout fail because a PDF or an email is late?&lt;/p&gt;&#xA;&lt;p&gt;Probably not.&lt;/p&gt;&#xA;&lt;p&gt;The checkout service can record the order, place an &lt;code&gt;invoice.requested&lt;/code&gt; message in a queue, and return a useful response. An invoice worker handles the slow task later. If that worker is busy or briefly offline, the message waits instead of taking checkout down with it.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
