<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Forem: helen</title>
    <description>The latest articles on Forem by helen (@red_panda).</description>
    <link>https://forem.com/red_panda</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3093439%2Ffe00de6a-3206-4ab6-93f8-f87e3e6d3d45.png</url>
      <title>Forem: helen</title>
      <link>https://forem.com/red_panda</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/red_panda"/>
    <language>en</language>
    <item>
      <title>Handling Transactions in Go the Clean Way — Practical Tips Inside!</title>
      <dc:creator>helen</dc:creator>
      <pubDate>Sat, 26 Apr 2025 13:00:51 +0000</pubDate>
      <link>https://forem.com/red_panda/handling-transactions-in-go-the-clean-way-practical-tips-inside-504b</link>
      <guid>https://forem.com/red_panda/handling-transactions-in-go-the-clean-way-practical-tips-inside-504b</guid>
      <description>&lt;p&gt;Hey folks! 👋&lt;/p&gt;

&lt;p&gt;I wanted to share an article written by a good friend of mine about a clean and practical way to handle database transactions in Go — without cluttering your business logic or breaking Clean Architecture principles.&lt;/p&gt;

&lt;p&gt;It’s a hands-on guide based on real project experience, focusing on keeping your services modular, testable, and easy to maintain.&lt;/p&gt;

&lt;p&gt;Here’s the full article if you’re curious:&lt;br&gt;
👉 &lt;a href="https://medium.com/@metalfmmetalfm/yet-another-way-to-handle-transactions-in-go-using-clean-architecture-fe45d0ebbdd5" rel="noopener noreferrer"&gt;Yet Another Way to Handle Transactions in Go (Using Clean Architecture)&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Would love to hear your thoughts or see how others are handling transactions in their Go projects!&lt;/p&gt;

</description>
      <category>cleancode</category>
      <category>go</category>
      <category>backend</category>
    </item>
  </channel>
</rss>
