<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Aurora on cloudplz</title><link>https://cloudplz.cc/tags/aurora/</link><description>Recent content in Aurora on cloudplz</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 01 Jan 0001 00:00:00 +0000</lastBuildDate><atom:link href="https://cloudplz.cc/tags/aurora/index.xml" rel="self" type="application/rss+xml"/><item><title>Aurora Migration Toolkit</title><link>https://cloudplz.cc/projects/aurora-migration-toolkit/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://cloudplz.cc/projects/aurora-migration-toolkit/</guid><description>&lt;p&gt;Migrating a single database to Aurora is a project. Migrating fifty —&#10;including multi-terabyte, tier-0 systems with 24/7 write traffic — is a&#10;platform. This is the toolkit and methodology that made it repeatable.&lt;/p&gt;&#10;&lt;h2 id="challenge"&gt;Challenge&#10;&lt;/h2&gt;&#10;&lt;p&gt;Each team&amp;rsquo;s database had different constraints: replication lag budgets,&#10;change-freeze windows, version skew between on-premises MySQL and Aurora,&#10;and applications that had grown assumptions about their database over a&#10;decade. One-off migration plans did not scale to fifty of them.&lt;/p&gt;</description></item></channel></rss>