<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Case Studies on Chen Kai Blog</title><link>https://www.chenk.top/en/tags/case-studies/</link><description>Recent content in Case Studies on Chen Kai Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 27 Jul 2025 09:00:00 +0000</lastBuildDate><atom:link href="https://www.chenk.top/en/tags/case-studies/index.xml" rel="self" type="application/rss+xml"/><item><title>System Design (8): Case Studies — URL Shortener, Chat System, News Feed</title><link>https://www.chenk.top/en/system-design/08-case-studies/</link><pubDate>Sun, 27 Jul 2025 09:00:00 +0000</pubDate><guid>https://www.chenk.top/en/system-design/08-case-studies/</guid><description>&lt;p>The best way to learn system design is to practice it. Reading about individual components — caching, queues, load balancers — builds your vocabulary, but designing a complete system is where you learn to compose those components into something that actually works.&lt;/p>
&lt;p>This article walks through three classic system design problems end to end. Each follows the framework from the first article in this series: clarify requirements, estimate scale, design the architecture, deep dive into critical components, and identify bottlenecks.&lt;/p></description></item></channel></rss>