Spanner
product on 4 shows · 7 statements across 5 episodes · said 4 times in 1 episodes
Top Founders 
the MAD Podcast 
the a16z Podcast 
20VC
7 statements about Spanner, every show
Vahdat: Google estimated Bigtable to Spanner migration required 7,000 staff-years
“The estimate for doing that migration for Google was seven staffed millennia.”
Kimball: Most database problems at Square were solvable with Spanner
“If you looked at all the problems Square was having, and they had something like 70 externally facing use cases when we joined them, most of the problems that they were struggling with could have been solved with the use of something like Spanner.”
Kimball: Google ran over 1,000 MySQL shards for a decade before Spanner
“Google didn't replace that system with Spanner, I think for almost 10 years. So by that time it had gotten to a thousand plus shards of MySQL.”
Chia: Google Spanner eliminates operational differences between and within shards
“And in Spanner, it's a little bit nicer in that every shard behaves the same, and because we have technologies like, ah, two-phase commit, We are, you don't really have any difference between operating within a shard or across shards, but it's not always true …”
Chia: All Spanner RPCs address specific data rather than machine names
“All RPCs in Spanner are addressed to specific pieces of data rather than the machine name.”
Kimball: Google replaced all sharded MySQL with Spanner and Bigtable
“Spanner is the database technology that Google has used to consolidate all of their various applications on top of. So they no longer use Sharded MySQL. Everything's on Spanner or on Bigtable.”