<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Publish-Subscribe on Compile My Mind</title>
		<link>https://www.compilemymind.com/tags/publish-subscribe/</link>
		<description>Recent content in Publish-Subscribe on Compile My Mind</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Thu, 15 Oct 2026 13:01:41 +0300</lastBuildDate>
		
			<atom:link href="https://www.compilemymind.com/tags/publish-subscribe/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Message Queue vs Publish-Subscribe: What Is the Difference?</title>
				<link>https://www.compilemymind.com/posts/message-queue-vs-publish-subscribe/</link>
				<pubDate>Thu, 15 Oct 2026 13:01:41 +0300</pubDate>
				<guid>https://www.compilemymind.com/posts/message-queue-vs-publish-subscribe/</guid>
				<description>&lt;p&gt;An order is placed. Inventory must reserve stock, billing must create an invoice, analytics must record the sale, and an email must reach the customer.&lt;/p&gt;&#xA;&lt;p&gt;It is tempting to put that order into one queue and start four consumers. The diagram looks asynchronous and scalable. The behavior, however, is wrong: if those consumers compete for messages, one may reserve stock while another sends the email, but no single order triggers all four actions.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
