3 ms·

I’ve always stuck with log shipping to a warm standby wherever possible for the same reason. Well-managed single instance databases can do 3+ nines easily; very

I’ve always stuck with log shipping to a warm standby wherever possible for the same reason. Well-managed single instance databases can do 3+ nines easily; very few applications actually require more availability than that. Especially at 5x the cost in opex for a theoretical-but-not-really-wink-wink extra 9.

jrochkind1 8y ago
In github's case, of course, they can't do a single instance db for performance reasons, even before you get to HA. If I understand it right.
- jeremyjh 8y ago
  Throughput is orthogonal to reliability. You can improve both by creating read replicas, but that doesn't imply automated fail-over.
- manquer 8y ago
  Depends on how your architecture, github as a whole likely has volume of writes greater than a single server instance, however either components could be split in separate dbs ( seems to be their approach) or shard / partition the data