“As it invites the world to play in a mysterious sandbox it likes to call ‘Caffeine’, Google is testing more than just a ‘next-generation’ search infrastructure. It’s testing at least a portion of a revamped software architecture that will likely underpin all of its online applications for years to come. Speaking with The Reg, ueber-Googler Matt Cutts confirms that the company’s new Caffeine search infrastructure is built atop a complete overhaul of the company’s custom-built Google File System, a project two years in the making. At least informally, Google refers to this file system redux as GFS2.”
Google Caffeine: What it Really Is
2009-08-15 Google 3 Comments
Of course, this is strongly related to Google’s previous talking on “instantaneous” loading and making the Web faster, also through collaboration:
But could it be a coincidence that the focus on “ultra-low latency” with GFS2 happens simultaneously with Google Waves (see wave.google.com and fast-forward to 10:30 and 35:45) and a possible upcoming (highly necessary) improvement to simultaneously edit in Google Docs?
(Current simultaneous editing in Google Docs results too frequently in a rather aggressive system-invoked undo of the work you’ve done when someone else has done editing in a nearby section of the Doc. Sometimes this erases up to 15 minutes of writing.)
All in all, I’m continuing to be amazed with both Google’s productivity and Google’s reasoning, which somehow never seems to go astray. What I am curious about is how Google manage to move everything to GFS2 without having to temporally shut down some of their services (most notably Search).