<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Worker Pattern on A Blog for the Uninitialized</title><link>https://www.nilpointer.blog/tags/worker-pattern/</link><description>Recent content in Worker Pattern on A Blog for the Uninitialized</description><generator>Hugo</generator><language>en-us</language><copyright>&lt;a href="https://www.apache.org/licenses/LICENSE-2.0" target="_blank" rel="noopener"&gt;Licensed under Apache 2.0&lt;/a&gt;</copyright><lastBuildDate>Thu, 26 Feb 2026 16:09:17 -0800</lastBuildDate><atom:link href="https://www.nilpointer.blog/tags/worker-pattern/index.xml" rel="self" type="application/rss+xml"/><item><title>The Worker Pattern</title><link>https://www.nilpointer.blog/posts/2026/02/the-worker-pattern/</link><pubDate>Thu, 26 Feb 2026 16:09:17 -0800</pubDate><guid>https://www.nilpointer.blog/posts/2026/02/the-worker-pattern/</guid><description>&lt;p&gt;I really like using a worker pattern with &lt;a href="https://www.nilpointer.blog/posts/2026/02/golangs-unbuffered-and-buffered-channels/"
 
 
&gt;unbuffered channels&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;API calls, especially when each can be handled separately and independently, are easily implemented with this pattern, and I&amp;rsquo;ve seen it help tremendously when downloading artifacts for building in CI, for example.&lt;/p&gt;
&lt;p&gt;Instead of setting up a buffered channel with a capacity of 10 in an attempt to concurrently handle 10 requests, you can create an unbuffered channel and read from it using 10 workers.&lt;/p&gt;</description></item></channel></rss>