<?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>Sd on Yutong Jin</title><link>https://yutongjin.com/tags/sd/</link><description>Recent content in Sd on Yutong Jin</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 08 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://yutongjin.com/tags/sd/index.xml" rel="self" type="application/rss+xml"/><item><title>10 tips for SD</title><link>https://yutongjin.com/posts/sd_learning_48/</link><pubDate>Wed, 08 Apr 2026 00:00:00 +0000</pubDate><guid>https://yutongjin.com/posts/sd_learning_48/</guid><description>&lt;h1 id="10-system-design-tips-senior-level"&gt;10 System Design Tips (Senior-Level)&lt;/h1&gt;
&lt;p&gt;April 8, 2026&lt;br&gt;
Yutong Jin&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="-system-design-key-principles"&gt;🧠 System Design Key Principles&lt;/h2&gt;
&lt;h3 id="1-start-with-functional-requirements"&gt;1. Start with Functional Requirements&lt;/h3&gt;
&lt;p&gt;Clearly define what the system needs to do:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Core APIs (read/write flows)&lt;/li&gt;
&lt;li&gt;User interactions&lt;/li&gt;
&lt;li&gt;Edge cases&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;💡 Tip:
Do NOT spend too long here — 2–3 minutes is enough in interviews.&lt;/p&gt;
&lt;hr&gt;
&lt;h3 id="2-identify-the-core-bottleneck-early"&gt;2. Identify the Core Bottleneck Early&lt;/h3&gt;
&lt;p&gt;Before designing, ask:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;What is the expected QPS?&lt;/li&gt;
&lt;li&gt;Where will the system break first?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Common bottlenecks:&lt;/p&gt;</description></item></channel></rss>