4 ms·
And also get a hot spare for that big relational database. And take good snapshot backups and verify they work and verify you can access them when required. M
by akira2501 2y ago
And also get a hot spare for that big relational database. And take good snapshot backups and verify they work and verify you can access them when required. Maybe your internal IT /can/ do all of this, in production, without making you want to cry on a daily basis.
We didn't really need the scale. We just didn't want to deal with any of those problems. Often there's a little checkbox you can check that solves one or more of these problems, the cost of checking the box is dependent on the size of the data itself. This is convenient _and_ predictable. We like that.