<?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 Murat Useinov</title>
    <link>https://useinov.com/tags/system-design/</link>
    <description>Recent content in System-Design on Murat Useinov</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 01 Sep 2026 19:40:00 +0300</lastBuildDate>
    <atom:link href="https://useinov.com/tags/system-design/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>A single server and a database is enough here</title>
      <link>https://useinov.com/posts/2026/single-server-is-enough/</link>
      <pubDate>Tue, 01 Sep 2026 19:40:00 +0300</pubDate>
      <guid>https://useinov.com/posts/2026/single-server-is-enough/</guid>
      <description>&lt;p&gt;Ten years ago a system design conversation was short. A server, a monolith, Postgres, maybe a load balancer in front. For most products that was the entire architecture, and it held.&lt;/p&gt;
&lt;p&gt;Now the same conversation opens with API gateways and doesn&amp;rsquo;t stop: Kubernetes, service meshes, Kafka, Redis, three databases because each one is good at one thing, gRPC, GraphQL, Elasticsearch, Terraform, Prometheus, tracing, sharding, replication, autoscaling.&lt;/p&gt;
&lt;p&gt;The awkward part is that none of it is junk. Every one of those tools exists because someone hit a real wall: more users, more data, more teams, more regions, more nines of uptime.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
