<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>System Design on Gürkan UÇAR</title>
    <link>https://gurkanucar.com/tags/system-design/</link>
    <description>Recent content in System Design on Gürkan UÇAR</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <lastBuildDate>Sat, 08 Aug 2026 10:00:00 +0300</lastBuildDate>
    <atom:link href="https://gurkanucar.com/tags/system-design/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>An Async Email Sending System: A Stack-Independent Design</title>
      <link>https://gurkanucar.com/posts/async-email-sending-system-design/</link>
      <pubDate>Sat, 08 Aug 2026 10:00:00 +0300</pubDate>
      <guid>https://gurkanucar.com/posts/async-email-sending-system-design/</guid>
      <description>How to design an async email system that does not tie your workflow to the provider, while handling duplicate sends and silent losses: atomic enqueue, idempotent claim, stuck-job recovery, retry and retention.</description>
    </item>
  </channel>
</rss>
