<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Percona on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/percona/</link>
    <description>Recent content in Percona on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 11 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/percona/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted MySQL High Availability: InnoDB Cluster vs Percona XtraDB Cluster vs Orchestrator (2026)</title>
      <link>https://www.pistack.xyz/posts/2026-05-11-self-hosted-mysql-high-availability-innodb-cluster-percona-xtradb-orchestrator-guide/</link>
      <pubDate>Mon, 11 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-11-self-hosted-mysql-high-availability-innodb-cluster-percona-xtradb-orchestrator-guide/</guid>
      <description>&lt;p&gt;MySQL remains the world&amp;rsquo;s most popular open-source relational database, but running it in production without a high availability (HA) strategy is a recipe for downtime and data loss. Whether you&amp;rsquo;re managing an e-commerce platform, a SaaS application, or an internal tool, ensuring your MySQL database stays online through hardware failures, network partitions, and planned maintenance is non-negotiable.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
