3 ms·
A reasonable thought, but wrong. The existing datastore has basically the 99.9% of the benefits you describe. Unfortunately, 99.9% availability (especially wh
by powera 16y ago
A reasonable thought, but wrong. The existing datastore has basically the 99.9% of the benefits you describe. Unfortunately, 99.9% availability (especially when a single datastore request may touch 10 things and thus be at 99% availability) isn't good enough.
One of the major problems with having a single bigtable is partial outages. These can either be the major events like there were today, with 10% or more of the cell having issues, or it can be just one server in the bigtable having performance issues. The key to having higher availability with the High Replication datastore is that if certain entities are slow or unavailable in one datacenter, we can rely on the performance of other datacenters to limit the latency.
- strlen 16y agoIs this the first production use of Spanner? (No worries if you're not allowed to comment on this, sorry to be nosy, but this is something I'm curious about)
- rbranson 16y agoThanks for the clarification, but I'm not sure I follow what I was wrong about. I wasn't saying that it should have 99.9% availability, I was just stating that in most situations, using Paxos to elect a master provides very nearly all the benefits (99.9% was just a vague figure to indicate this) of doing a Paxos commit each time.