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

Why keep the same instance count strategy (nearly tripling Aurora instances) if the goal was cost efficiency?

More instances at a smaller size, combined with Aurora's ability to use both writer and reader instances simultaneously (unlike their prior RDS setup) and auto-scale reader count with demand, meant total available compute could match or exceed the old setup during peak load while automatically scaling down — and costing less — during off-peak hours. Instance count alone was the wrong metric; total cost against actual demand curve was the real optimization target.

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.