<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Patterns on Rafiul Alam</title>
    <link>https://alamrafiul.com/categories/patterns/</link>
    <description>Recent content in Patterns on Rafiul Alam</description>
    <image>
      <title>Rafiul Alam</title>
      <url>https://alamrafiul.com/papermod-cover.png</url>
      <link>https://alamrafiul.com/papermod-cover.png</link>
    </image>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Fri, 30 Aug 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://alamrafiul.com/categories/patterns/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Pipeline Patterns: Streaming Data Processing with Goroutines</title>
      <link>https://alamrafiul.com/posts/go-pipeline-streaming/</link>
      <pubDate>Fri, 30 Aug 2024 00:00:00 +0000</pubDate>
      
      <guid>https://alamrafiul.com/posts/go-pipeline-streaming/</guid>
      <description>&lt;h2 id=&#34;the-power-of-streaming-pipelines&#34;&gt;The Power of Streaming Pipelines&lt;/h2&gt;
&lt;p&gt;Imagine processing a million log entries. The naive approach loads everything into memory, processes it, then outputs results. But what if you don&amp;rsquo;t have enough RAM? What if you want results streaming in real-time?&lt;/p&gt;
&lt;p&gt;Pipeline patterns break complex processing into stages connected by channels. Data flows through the pipeline, with each stage transforming it concurrently. It&amp;rsquo;s Unix pipes meets goroutines-and it&amp;rsquo;s beautiful.&lt;/p&gt;
&lt;h3 id=&#34;the-sequential-approach&#34;&gt;The Sequential Approach&lt;/h3&gt;
&lt;p&gt;Here&amp;rsquo;s what we&amp;rsquo;re moving away from:&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
