<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Load Balancing on Chen Kai Blog</title><link>https://www.chenk.top/en/tags/load-balancing/</link><description>Recent content in Load Balancing on Chen Kai Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 12 Jul 2025 09:00:00 +0000</lastBuildDate><atom:link href="https://www.chenk.top/en/tags/load-balancing/index.xml" rel="self" type="application/rss+xml"/><item><title>System Design (2): DNS, CDN, and Load Balancing — The First Three Hops</title><link>https://www.chenk.top/en/system-design/02-dns-cdn-load-balancing/</link><pubDate>Sat, 12 Jul 2025 09:00:00 +0000</pubDate><guid>https://www.chenk.top/en/system-design/02-dns-cdn-load-balancing/</guid><description>&lt;p>In 2017, a single misconfigured DNS record at a major cloud provider took down a significant portion of the internet for several hours. Thousands of websites became unreachable — not because their servers were down, but because the system that translates domain names into IP addresses stopped working correctly. The incident was a stark reminder that the infrastructure we take for granted — DNS, CDN, load balancers — is the foundation everything else rests on.&lt;/p></description></item><item><title>Cloud Computing (5): Cloud Network Architecture and SDN</title><link>https://www.chenk.top/en/cloud-computing/networking-sdn/</link><pubDate>Tue, 18 Apr 2023 09:00:00 +0000</pubDate><guid>https://www.chenk.top/en/cloud-computing/networking-sdn/</guid><description>&lt;p>&lt;figure class="article-figure">
 &lt;img src="https://blog-pic-ck.oss-cn-beijing.aliyuncs.com/posts/en/cloud-computing/networking-sdn/illustration_1.png" alt="Cloud Computing (5): Cloud Network Architecture and SDN — Chapter overview" loading="lazy" decoding="async" class="content-image">
 
&lt;/figure>
&lt;/p>
&lt;p>A cloud platform is essentially a network with attached computers. The compute layer scales by adding servers; the storage layer scales by adding disks; the &lt;em>network&lt;/em> layer integrates these into a single, coherent system. Get the network right, and the rest of the stack feels effortless. Get it wrong — a missing route, a 5-tuple mismatch in a security group, or an under-provisioned load balancer — and the whole platform goes dark.&lt;/p></description></item></channel></rss>