Multi-single-tenant actually makes it easier to do transactional schema upgrades because these operations only impact one customer at a time. No fiddling with middle-of-the-migration state.
It becomes a non-issue if you're able to go down for a few moments.
Not necessarily viable for some software though, it just depends on what you're running.
(Especially because you can apply the migration on slave and subsequently switch master, making this downtime as quick as the time your system needs to do a database switch.)
This doesn't apply to big services with millions of users, however.
It becomes a non-issue if you're able to go down for a few moments. Not necessarily viable for some software though, it just depends on what you're running.
(Especially because you can apply the migration on slave and subsequently switch master, making this downtime as quick as the time your system needs to do a database switch.)
This doesn't apply to big services with millions of users, however.