<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Networking on Chen Kai Blog</title><link>https://www.chenk.top/en/tags/networking/</link><description>Recent content in Networking on Chen Kai Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 30 Apr 2026 09:00:00 +0000</lastBuildDate><atom:link href="https://www.chenk.top/en/tags/networking/index.xml" rel="self" type="application/rss+xml"/><item><title>Alibaba Cloud Full Stack (3): VPC, SLB, and the Network Layer</title><link>https://www.chenk.top/en/aliyun-fullstack/03-vpc-networking/</link><pubDate>Thu, 30 Apr 2026 09:00:00 +0000</pubDate><guid>https://www.chenk.top/en/aliyun-fullstack/03-vpc-networking/</guid><description>&lt;p>Every outage I have debugged in the cloud ultimately traced back to networking. Bad CIDR planning that ran out of IPs six months in. Missing routes that silently dropped traffic between tiers. Security groups that were either wide open (hello, port 22 to &lt;code>0.0.0.0/0&lt;/code>) or so locked down that health checks failed and the load balancer kept draining healthy instances. Getting the network layer right is the single most important thing you can do before deploying anything else, and it is the single most painful thing to fix retroactively because changing a VPC CIDR means recreating everything inside it.&lt;/p></description></item><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>Docker and Containers (4): Networking and Volumes — How Containers Talk and Persist</title><link>https://www.chenk.top/en/docker-containers/04-networking-and-volumes/</link><pubDate>Mon, 19 Jun 2023 09:00:00 +0000</pubDate><guid>https://www.chenk.top/en/docker-containers/04-networking-and-volumes/</guid><description>&lt;p>Containers are deliberately isolated. That&amp;rsquo;s the point. But useful applications need to accept connections from the outside world, talk to databases, and store data that survives container restarts. Docker provides two mechanisms for this: networks (for communication) and volumes (for persistent storage). Getting these right makes the difference between a demo and a deployment.&lt;/p>
&lt;hr>
&lt;h2 id="docker-networking" class="heading-anchor">Docker Networking&lt;a href="#docker-networking" class="heading-link" aria-label="Permalink to this section" title="Copy link to this section">#&lt;/a>
&lt;/h2>&lt;p>When Docker starts, it creates a virtual network infrastructure on the host. Each container gets its own network namespace (with its own IP address, routing table, and network interfaces), and Docker manages the traffic flow between containers and the outside world.&lt;/p></description></item></channel></rss>