Re:Spanner vs. Calvin: distributed consistency at scale
by fdsfsafasfdas on Thursday April 06, 2017 @05:12PM
(#14054671)
> This makes it difficult to open source without open sourcing a bunch of hardware.
That's simply not true; there are many consumer-grade GPS clocks out there well within the bounds that spanner operates (iirc skew bounded at +- 5ms).
Not only that, but you can bet that if spanner were open-sourced, you'd see additional pressure to lower the cost of that hardware.
Not that the answer is any more nefarious: They don't open source it because it extensively uses google-only code, and open sourcing spanner would entail open sourcing many, many other parts of code, which is expensive. It'd be much easier to have something like the dynamo db local front to sqlite3 like amazon offers.
Re:Spanner vs. Calvin: distributed consistency at scale
by vgt on Thursday April 06, 2017 @05:19PM
(#14054726)
A critical design feature of Spanner is owning the packets end-to-end (as in, between data centers and across oceans). This lets Google minimize the "A" in "CAP", and would be quite difficult to replicate outside of a network like Google's SDN.
Spanner is the software, plus the network, plus the hardware.
(work on Google Cloud)
Re:Spanner vs. Calvin: distributed consistency at scale
by hendzen on Friday April 07, 2017 @02:52AM
(#14057684)
+ The army of SREs monitoring it...
Re:Spanner vs. Calvin: distributed consistency at scale
by fdsfsafasfdas on Thursday April 06, 2017 @05:26PM
(#14054784)
A very good point.
You can't run a full spanner cluster unless you have the Google Hardware. Spanner needs to have an accurate clock with a known error bound. This makes it difficult to open source without open sourcing a bunch of hardware.