<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Database on Chen Kai Blog</title><link>https://www.chenk.top/en/tags/database/</link><description>Recent content in Database on Chen Kai Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 02 May 2026 09:00:00 +0000</lastBuildDate><atom:link href="https://www.chenk.top/en/tags/database/index.xml" rel="self" type="application/rss+xml"/><item><title>Alibaba Cloud Full Stack (5): RDS and PolarDB — The Database Layer</title><link>https://www.chenk.top/en/aliyun-fullstack/05-rds-database/</link><pubDate>Sat, 02 May 2026 09:00:00 +0000</pubDate><guid>https://www.chenk.top/en/aliyun-fullstack/05-rds-database/</guid><description>&lt;p>My self-managed MySQL on ECS lasted exactly four months before a disk I/O spike during peak traffic brought the whole thing down. The InnoDB buffer pool was fighting the OS page cache for memory, the binary log was filling the system disk faster than my cron job could rotate it, and the single-threaded replication to my &amp;ldquo;backup&amp;rdquo; instance was nine hours behind. I fixed it at 3 AM by throwing more disk at it. Then it happened again two weeks later. That is the day I learned why managed databases exist — not because I cannot run MySQL, but because I do not want to be the person paged at 3 AM when MySQL decides the relay log is corrupted and the only fix is to rebuild the replica from a cold backup that may or may not be consistent.&lt;/p></description></item></channel></rss>