<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Mysql on gywn&#39;s tech</title>
    <link>/en/tags/mysql/</link>
    <description>Recent content in Mysql on gywn&#39;s tech</description>
    <generator>Hugo</generator>
    <language>en</language>
    <managingEditor>gywndi@gmail.com (gywndi)</managingEditor>
    <webMaster>gywndi@gmail.com (gywndi)</webMaster>
    <lastBuildDate>Sun, 23 Aug 2026 08:16:18 +0900</lastBuildDate>
    <atom:link href="/en/tags/mysql/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Understanding Vitess by Building It Yourself, Locally</title>
      <link>/en/2026/08/vitess-from-scratch-bare-metal-sharding/</link>
      <pubDate>Sun, 09 Aug 2026 23:15:14 +0900</pubDate><author>gywndi@gmail.com (gywndi)</author>
      <guid>/en/2026/08/vitess-from-scratch-bare-metal-sharding/</guid>
      <description>&lt;p&gt;There comes a point where a single MySQL instance just can&amp;rsquo;t keep up with the data anymore.&#xA;Vitess is one of the approaches YouTube, Slack, and GitHub have used to solve this problem.&#xA;I worked through what Vitess actually does, what components it&amp;rsquo;s made of, and how those&#xA;components should actually be laid out, by building it myself in a local Docker environment.&#xA;The setup shown here is posted as-is in a &lt;a href=&#34;https://github.com/gywndi/vitess-example&#34;&gt;GitHub repo&lt;/a&gt;,&#xA;and you can spin it up yourself with nothing but Docker.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
