<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Orchestration on Chen Kai Blog</title><link>https://www.chenk.top/en/tags/orchestration/</link><description>Recent content in Orchestration on Chen Kai Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 23 Jun 2023 09:00:00 +0000</lastBuildDate><atom:link href="https://www.chenk.top/en/tags/orchestration/index.xml" rel="self" type="application/rss+xml"/><item><title>Docker and Containers (8): Beyond Docker — Kubernetes, Swarm, and What Comes Next</title><link>https://www.chenk.top/en/docker-containers/08-orchestration-preview/</link><pubDate>Fri, 23 Jun 2023 09:00:00 +0000</pubDate><guid>https://www.chenk.top/en/docker-containers/08-orchestration-preview/</guid><description>&lt;p>So far, this series has focused on single-host Docker: one machine running containers. This setup works well for development, small projects, and applications with modest traffic. However, when you need your service to survive server failures, handle traffic spikes, or deploy updates without downtime, single-host Docker falls short. Container orchestration addresses these issues, and Kubernetes has become the go-to solution.&lt;/p>
&lt;hr>
&lt;h2 id="why-single-host-docker-isnt-enough" class="heading-anchor">Why Single-Host Docker Isn&amp;rsquo;t Enough&lt;a href="#why-single-host-docker-isnt-enough" class="heading-link" aria-label="Permalink to this section" title="Copy link to this section">#&lt;/a>
&lt;/h2>&lt;p>Consider what happens when your Docker host fails:&lt;/p></description></item></channel></rss>