Before migrating a distributed database to the cloud, do not start with node count or capacity sizing. Start with the failure model. Decide replication strategy first, then consistency level, then network topology, and only then capacity. A safe migration also needs clear acceptance criteria, a quantitative replication-lag cutover gate, and a tested rollback plan before the maintenance window begins. Capacity is the consequence of architecture, not the starting point.

Read the original article