<?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>Pipeline on Bits, Trades &amp; Systems</title>
    <link>https://blog.turboawesome.win/tags/pipeline/</link>
    <description>Recent content in Pipeline on Bits, Trades &amp; Systems</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 01 Jul 2020 14:30:00 +0000</lastBuildDate>
    <atom:link href="https://blog.turboawesome.win/tags/pipeline/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Building a High-Throughput Event Pipeline in Go Without Losing Your Mind</title>
      <link>https://blog.turboawesome.win/2020/07/building-a-high-throughput-event-pipeline-in-go-without-losing-your-mind/</link>
      <pubDate>Wed, 01 Jul 2020 14:30:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2020/07/building-a-high-throughput-event-pipeline-in-go-without-losing-your-mind/</guid>
      <description>Channels are Go&amp;#39;s concurrency primitive, but a naive pipeline of goroutines and channels won&amp;#39;t survive high throughput. The patterns that scale: batching, backpressure, worker pools, and knowing when to abandon channels entirely.</description>
    </item>
  </channel>
</rss>
