---
answer: direct
beat: system-design
source: 1 article · updated: November 17, 2026
---

How does the 'daisy chain' approach avoid needing a large pool of spare infrastructure?

Instead of draining tenants into newly provisioned temporary capacity, each converted Aurora cluster immediately becomes the refill target for the next instance being drained. Instance A converts and receives tenants from Instance B being drained; B then converts and receives tenants from C; and so on. Each completed conversion becomes capacity for the next one, so only enough spare capacity for one or two instances mid-conversion is ever needed, not enough to hold the whole fleet.

Answered in

The Migration Trick That Moved 4 Million Databases Without a Bigger Fleet

Atlassian couldn't provision enough spare capacity to migrate 4M Jira databases at once. So they made the migration feed itself — a daisy chain, not a fleet.

Crashtech Editorial November 17, 2026 System Design & Architecture

Read the full analysis

Other questions this article answers

More system design & architecture questions

Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the System Design & Architecture beat.