<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Pipelining on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/pipelining/</link><description>Recent content in Pipelining on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 07 Nov 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/pipelining/index.xml" rel="self" type="application/rss+xml"/><item><title>Intermediate Topics: Transactions and Pipelining</title><link>https://ai-blog.noorshomelab.dev/redis-guide/transactions-and-pipelining/</link><pubDate>Fri, 07 Nov 2025 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/redis-guide/transactions-and-pipelining/</guid><description>&lt;p&gt;As you build more complex applications with Redis, you&amp;rsquo;ll encounter scenarios where you need to execute multiple commands as a single, atomic operation or send a batch of commands to the server efficiently. This is where &lt;strong&gt;Transactions&lt;/strong&gt; and &lt;strong&gt;Pipelining&lt;/strong&gt; become invaluable. While they both involve sending multiple commands, they serve different primary purposes:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Transactions (MULTI/EXEC)&lt;/strong&gt; ensure that a group of commands is executed atomically and in isolation, preventing other clients from interfering with the intermediate state.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Pipelining&lt;/strong&gt; optimizes network round-trip time by sending multiple commands at once without waiting for a reply to each, significantly boosting performance for high-throughput scenarios.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;In this chapter, we&amp;rsquo;ll cover:&lt;/p&gt;</description></item></channel></rss>