The situation
The databases competed for the same CPU, memory and disk I/O. A noisy neighbour is not a figure of speech here: one query plan going wrong on one database showed up as latency on all of them.
Capacity could only be bought for the whole machine. One database under load meant upgrading a server that every other database also sat on — paying for headroom that only one of them needed.
And maintenance was shared whether or not the work was. A restart, a minor-version upgrade or an unplanned fault on that host reached every database at once, which turned routine work into something that had to be scheduled like an incident.
Solution
01Group by what contends, not by what is biggest
The grouping came from what actually competed: which databases, and which of the heaviest tables, were driving CPU, memory and I/O in the same hours. A split by storage footprint produces neat numbers and leaves the contention exactly where it was.
That gave three dedicated RDS instances rather than one per database. Isolation is bought per instance, and an instance per database would have been paying for separation nobody had asked for.
02Stand each environment up before moving anything into it
Each target instance was configured as an independent environment first — parameters, backup schedule and monitoring belonging to that database rather than inherited from a shared host.
The data then moved into the environment it was going to live in, instead of into a copy of the old one that would be adjusted afterwards. Adjusting afterwards is how a shared configuration quietly reappears on three machines.
03Treat the blast radius as the thing being bought
The purpose was not performance in the abstract. It was that a fault, a tuning change or a backup on one database stops being an event for the others — which is a reliability property, and it is what the three instances were chosen to buy.
Outcome
- 3
- dedicated instances, from one shared server
- 0
- maintenance windows shared between databases
- Shape before
- Several production databases on one server
- Shape after
- Three dedicated RDS instances
- Split decided by
- What contended in the same hours, not by size
- Scaling after
- One instance at a time, where the load is
Response times became predictable, because they stopped depending on what a neighbouring database was doing. That is the outcome the client asked for, and it is as far as we will put it: there was no controlled before-and-after benchmark across the move, so there is no percentage in this paragraph.
Scaling became granular. The instance carrying the load can be scaled up on its own, rather than upgrading a machine that every other database also sits on and paying for headroom none of them use.
The single point of failure is reduced, not removed. Three instances is three blast radii instead of one; it is not high availability, and the case for that is a separate conversation with a separate price.