<?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>Distributed-Systems on Murat Useinov</title>
    <link>https://useinov.com/tags/distributed-systems/</link>
    <description>Recent content in Distributed-Systems on Murat Useinov</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 04 Sep 2026 18:15:00 -0300</lastBuildDate>
    <atom:link href="https://useinov.com/tags/distributed-systems/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Nine patterns, and where the complexity goes</title>
      <link>https://useinov.com/posts/2026/nine-patterns-where-complexity-goes/</link>
      <pubDate>Fri, 04 Sep 2026 18:15:00 -0300</pubDate>
      <guid>https://useinov.com/posts/2026/nine-patterns-where-complexity-goes/</guid>
      <description>&lt;p&gt;Nine distributed systems patterns, written the way they actually get decided: what you buy, and where the complexity goes. Because none of these remove complexity. They relocate it.&lt;/p&gt;
&lt;p&gt;Replication. Multiple copies, one writer. You buy availability and read throughput. You now own replication lag, and the ticket from a user who saved something and didn&amp;rsquo;t see it on refresh.&lt;/p&gt;
&lt;p&gt;Sharding. Split the data across databases. You buy headroom. You now own a shard key that you chose at the exact moment you knew least about your traffic.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
