2 ms·
it's already been published. Google used Perforce for at least a decade and then cloned the perforce wire protocol when it was clear perforce wouldn't keep sca
by dekhn 8y ago
it's already been published. Google used Perforce for at least a decade and then cloned the perforce wire protocol when it was clear perforce wouldn't keep scaling (there's a great presentation online about google using RAMSANs to store the perforce index), but backed the repo in something like bigtable or spanner.
I'll give google credit for one thing: it can change backends a lot without too much user visible pain.
- joshuamorton 8y ago>I'll give google credit for one thing: it can change backends a lot without too much user visible pain. Amusingly, this comment may explain how someone in this thread can be incredulous about the idea that things get rewritten every 2-3 years (which yes is an exaggeration). Google is very good at making sweeping infrastructural changes (generally improvements, I might add) without significant user pain.