<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Software-Design on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/software-design/</link>
    <description>Recent content in Software-Design on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 19 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/software-design/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Dependency Injection Containers in Go: Google Wire vs Uber FX vs samber/do</title>
      <link>https://www.pistack.xyz/posts/2026-06-19-self-hosted-go-dependency-injection-containers-wire-fx-do/</link>
      <pubDate>Fri, 19 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-19-self-hosted-go-dependency-injection-containers-wire-fx-do/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;As Go services grow beyond simple CRUD handlers, managing dependencies — database connections, configuration, loggers, HTTP clients — becomes increasingly complex. Passing everything through constructor parameters works for small projects but becomes unwieldy at scale. Dependency injection (DI) containers solve this by automating the wiring between components, reducing boilerplate and making your codebase more testable.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
