<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Replication on Chen Kai Blog</title><link>https://www.chenk.top/en/tags/replication/</link><description>Recent content in Replication on Chen Kai Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 26 Apr 2024 09:00:00 +0000</lastBuildDate><atom:link href="https://www.chenk.top/en/tags/replication/index.xml" rel="self" type="application/rss+xml"/><item><title>Databases (6): Replication and Partitioning — Scaling Beyond One Machine</title><link>https://www.chenk.top/en/databases/06-replication-and-partitioning/</link><pubDate>Fri, 26 Apr 2024 09:00:00 +0000</pubDate><guid>https://www.chenk.top/en/databases/06-replication-and-partitioning/</guid><description>&lt;p>A single database server can handle a remarkable amount of load — a well-tuned PostgreSQL instance can serve tens of thousands of queries per second. But eventually you hit a wall. Maybe you need more read throughput than one CPU can provide. Maybe you need your data to survive a data center fire. Maybe your dataset exceeds what fits on a single disk. That is when you need replication and partitioning.&lt;/p></description></item></channel></rss>