<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Capacity Planning on Chen Kai Blog</title><link>https://www.chenk.top/en/tags/capacity-planning/</link><description>Recent content in Capacity Planning on Chen Kai Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 10 Jul 2025 09:00:00 +0000</lastBuildDate><atom:link href="https://www.chenk.top/en/tags/capacity-planning/index.xml" rel="self" type="application/rss+xml"/><item><title>System Design (1): Thinking in Systems — Load, Latency, and the Art of Estimation</title><link>https://www.chenk.top/en/system-design/01-thinking-in-systems/</link><pubDate>Thu, 10 Jul 2025 09:00:00 +0000</pubDate><guid>https://www.chenk.top/en/system-design/01-thinking-in-systems/</guid><description>&lt;p>A friend once asked me to help debug a performance problem. Their photo-sharing app worked fine in development but collapsed under production traffic. The database was melting, the API gateway was timing out, and users were seeing 504 errors. When I asked how many requests per second the system was handling, the answer was &amp;ldquo;I don&amp;rsquo;t know.&amp;rdquo; When I asked what the expected load was, the answer was &amp;ldquo;I didn&amp;rsquo;t think about that.&amp;rdquo;&lt;/p></description></item></channel></rss>