<?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 Imran Khan</title>
    <link>https://imran-khan.com/tags/system-design/</link>
    <description>Recent content in System Design on Imran Khan</description>
    <generator>Hugo -- 0.127.0</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 09 Aug 2026 06:51:15 +0000</lastBuildDate>
    <atom:link href="https://imran-khan.com/tags/system-design/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>System Design Terms, Explained the Way I&#39;d Explain Them to a Friend</title>
      <link>https://imran-khan.com/posts/50-system-design-terms-explained-the-way-id-explain-them-to-a-friend/</link>
      <pubDate>Sun, 09 Aug 2026 06:51:15 +0000</pubDate>
      <guid>https://imran-khan.com/posts/50-system-design-terms-explained-the-way-id-explain-them-to-a-friend/</guid>
      <description>Early in my career I&amp;rsquo;d hear a term in a design review, nod, and Google it under the table. Plenty of us do this. The vocabulary sounds scarier than the ideas behind it.
So here&amp;rsquo;s my plain-English version of 49 terms. I&amp;rsquo;ve grouped them by the kind of problem each one solves, not alphabetically, because I find that&amp;rsquo;s easier to remember.
Part 1: Handling Growth and Traffic 1. Scalability. Can your system survive getting popular?</description>
    </item>
  </channel>
</rss>
