https://klee1611.github.io/tags/system-design.htmlRecent content in System Design on Kourtney's PortfolioHugo -- gohugo.ioenkourtneylee1611@gmail.com (Kuo-Hsiu (Kourtney) Lee)kourtneylee1611@gmail.com (Kuo-Hsiu (Kourtney) Lee)© 2026 Kuo-Hsiu (Kourtney) LeeSat, 13 Jun 2026 14:05:33 -0400https://klee1611.github.io/posts/common-components-system-design.htmlSat, 13 Jun 2026 14:05:33 -0400kourtneylee1611@gmail.com (Kuo-Hsiu (Kourtney) Lee)https://klee1611.github.io/posts/common-components-system-design.html<p>Designing scalable and reliable systems requires understanding a core set of reusable building blocks. This article covers the most common components — from load balancers and databases to caches and CDNs — and the key trade-offs to consider when using them.</p> <h3 class="relative group">Load Balancer with Multiple Web Servers and Auto Scaling <div id="load-balancer-with-multiple-web-servers-and-auto-scaling" class="anchor"></div> <span class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"> <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#load-balancer-with-multiple-web-servers-and-auto-scaling" aria-label="Anchor">#</a> </span> </h3> <p>A load balancer distributes incoming traffic across multiple web servers, providing a single public entry point to the system.</p>https://klee1611.github.io/posts/rdbms-acid-nosql-cap.htmlMon, 06 Jan 2020 04:06:00 +0800kourtneylee1611@gmail.com (Kuo-Hsiu (Kourtney) Lee)https://klee1611.github.io/posts/rdbms-acid-nosql-cap.html<h2 class="relative group">RDBMS <div id="rdbms" class="anchor"></div> <span class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"> <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#rdbms" aria-label="Anchor">#</a> </span> </h2> <p><strong>Relational Database Management System</strong></p> <ul> <li>Used when there are strong <strong>Relations</strong> between data: <ul> <li>Design a schema that is unlikely to change, relating tables to each other, then you can retrieve the desired data through SQL.</li> </ul> </li> <li>Used when <strong>data correctness</strong> is very important: <ul> <li>Usually provides <strong>ACID</strong> properties.</li> </ul> </li> <li>Changing the schema is a huge undertaking: <ul> <li>Requires updating the table schema and migrating data.</li> <li>All programs that use the table with the changed schema need to be modified.</li> </ul> </li> <li><code>join</code> operations can be performed across different tables.</li> </ul>