<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Chaitanya Akula — Blog</title>
    <link>https://www.buildwithchai.dev/blog</link>
    <description>Writing on Golang, distributed systems, and payment infrastructure by Chaitanya Akula.</description>
    <language>en-us</language>
    <atom:link href="https://www.buildwithchai.dev/rss.xml" rel="self" type="application/rss+xml" />
    <lastBuildDate>Sat, 12 Sep 2026 00:06:26 GMT</lastBuildDate>
    <item>
      <title>Designing a Payment Transfer System for High Throughput</title>
      <link>https://www.buildwithchai.dev/blog/designing-a-payment-transfer-system-for-high-throughput</link>
      <guid isPermaLink="true">https://www.buildwithchai.dev/blog/designing-a-payment-transfer-system-for-high-throughput</guid>
      <description>What it actually takes to move money across 130+ banks reliably: idempotency, reconciliation, per-integration failure domains, and keeping tail latency predictable when downstream banks misbehave.</description>
      <pubDate>Tue, 08 Sep 2026 20:54:28 GMT</pubDate>
      <category>Golang</category><category>Distributed Systems</category><category>Payment Systems</category>
    </item>
    <item>
      <title>Taming Tail Latency in Go Services</title>
      <link>https://www.buildwithchai.dev/blog/taming-tail-latency-in-go-services</link>
      <guid isPermaLink="true">https://www.buildwithchai.dev/blog/taming-tail-latency-in-go-services</guid>
      <description>p99 is where your users actually live. A practical tour of the Go-specific causes of latency spikes — GC pauses, goroutine scheduling, connection pool starvation — and how to measure and fix them.</description>
      <pubDate>Sun, 30 Aug 2026 20:55:10 GMT</pubDate>
      <category>Golang</category><category>Performance</category><category>Observability</category>
    </item>
    <item>
      <title>Idempotency Keys Are Not Optional</title>
      <link>https://www.buildwithchai.dev/blog/idempotency-keys-are-not-optional</link>
      <guid isPermaLink="true">https://www.buildwithchai.dev/blog/idempotency-keys-are-not-optional</guid>
      <description>If a client can retry a request — and it always can — your write endpoints need idempotency keys. Here is how to design them so retries are safe without turning your database into a bottleneck.</description>
      <pubDate>Sat, 22 Aug 2026 20:55:03 GMT</pubDate>
      <category>Distributed Systems</category><category>API Design</category><category>Reliability</category>
    </item>
  </channel>
</rss>