<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Go on App Coding</title>
    <link>https://appcoding.com/tags/go/</link>
    <description>Recent content in Go on App Coding</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 09 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://appcoding.com/tags/go/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>20 Primitive Project Ideas: Tiny Go Engines That Do the Essential 10% of Redis, Kafka and Etcd</title>
      <link>https://appcoding.com/20-primitive-project-ideas-tiny-go-engines-that-do-the-essential-10-of-redis-kafka-and-etcd/</link>
      <pubDate>Fri, 09 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://appcoding.com/20-primitive-project-ideas-tiny-go-engines-that-do-the-essential-10-of-redis-kafka-and-etcd/</guid>
      <description>&lt;p&gt;Given the direction of &lt;a href=&#34;https://altsql.com/&#34;&gt;AltSql&lt;/a&gt;, &lt;a href=&#34;https://bareproxy.com/&#34;&gt;BareProxy&lt;/a&gt;, &lt;a href=&#34;https://precomputing.com/&#34;&gt;Precomputing&lt;/a&gt; and the &lt;a href=&#34;https://vpnw.com/&#34;&gt;VPN primitives&lt;/a&gt; work, there is still a surprisingly large design space for projects that are smaller than platforms but more fundamental than ordinary applications. The best candidates have a very simple sentence behind them: &amp;ldquo;X currently requires a framework, service or stack; this does the essential 10% in one tiny binary, library or file.&amp;rdquo;&lt;/p&gt;&#xA;&lt;p&gt;Look for primitives that can begin as a credible 2,000–10,000-line Go project, have an immediately understandable demo, and later sit underneath commercial products rather than needing to become a SaaS business immediately. Here are twenty directions that fit that model.&lt;/p&gt;</description>
    </item>
    <item>
      <title>BareProxy: A Small Go Web Server and Reverse Proxy That Explains Every Routing Decision</title>
      <link>https://appcoding.com/bareproxy-a-small-go-web-server-and-reverse-proxy-that-explains-every-routing-decision/</link>
      <pubDate>Fri, 02 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://appcoding.com/bareproxy-a-small-go-web-server-and-reverse-proxy-that-explains-every-routing-decision/</guid>
      <description>&lt;p&gt;Most sites run a thin slice of nginx in front of their application: TLS termination, serving static files from a folder, a couple of routes to a backend service, health checks, and the occasional reload. The configuration grows anyway, one regular expression at a time, until nobody is quite sure which block handles a given URL, and a change that looks safe to one person breaks something in production that another person didn&amp;rsquo;t know existed.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
