<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Concurrency on sugar, spice, &amp;terminal? nice</title>
    <link>https://terminal.space/tag/concurrency/</link>
    <description>Recent content in Concurrency on sugar, spice, &amp;terminal? nice</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Fri, 23 Sep 2022 04:01:41 +0000</lastBuildDate>
    <atom:link href="https://terminal.space/tag/concurrency/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Go concurrency the right way (e.g. my way)</title>
      <link>https://terminal.space/tech/go-concurrency-the-right-way-e-g-my-way/</link>
      <pubDate>Fri, 23 Sep 2022 04:01:41 +0000</pubDate>
      <guid>https://terminal.space/tech/go-concurrency-the-right-way-e-g-my-way/</guid>
      <description>&lt;figure&gt;&lt;img src=&#34;https://terminal.space/tech/go-concurrency-the-right-way-e-g-my-way/images/john-cameron-kY2H30v6Bs4-unsplash.jpg&#34;&gt;&#xA;&lt;/figure&gt;&#xA;&#xA;&lt;p&gt;My take on go concurrency is that there are 3 things that matter, and we can create a robust pattern using &amp;hellip; 3 technologies to help us out. None of this is really new, but I haven&amp;rsquo;t seen the material presented from this particular viewpoint. With that, and the additional caveat that this isn&amp;rsquo;t a beginner&amp;rsquo;s guide, let&amp;rsquo;s jump straight in&lt;/p&gt;&#xA;&lt;h2 id=&#34;what-matters&#34;&gt;What matters&lt;/h2&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;Startup&lt;/li&gt;&#xA;&lt;li&gt;Shutdown&lt;/li&gt;&#xA;&lt;li&gt;Throughput&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;p&gt;Once everything is _working_ it&amp;rsquo;s not all that complicated (*) to do concurrency in golang (or any other programming language. Data comes in, it gets farmed out to wherever it needs to go, and you have some synchronization method to prevent corruption.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
