Slashdot Mirror
Google File System Evolves, Hadoop To Follow
Christophe Bisciglia, Google's former infrastructure guru and current member of the Cloudera start-up team, has commented on Google's latest iteration on their GFS file system and deemed its features well within the evolutionary capabilities of open-source competitor Hadoop. "Details on Google's GFS2 are slim. After all, it's Google. But based on what he's read, Bisciglia calls the update 'the next logical iteration' of the original GFS, and he sees Hadoop eventually following in the (rather sketchy) footsteps left by his former employer. 'A lot of the things Google is talking about are very logical directions for Hadoop to go,' Bisciglia tells The Reg. 'One of the things I've been very happy to see repeatedly demonstrated is that Hadoop has been able to implement [new Google GFS and MapReduce] features in approximately the same order. This shows that the fundamentals of Hadoop are solid, that the fundamentals are based on the same principles that allowed Google's systems to scale over the years.'"
But would you really rather talk about companies with names like that? Google knows their audience. There's the normal people who will use anything that's set as the default, and the nerds who are the ones setting the defaults. Google can't convince normal people to switch (because telling someone to click on the search box and choose Google is "too complicated"), so it makes sense for them to target very specifically at nerds, who will then do their work for them.
Score: 1, Informative
WTF?
No sig for the moment.
Hadoop is not really a file system or rather as you found out it doesn't make a good one. It's a framework for doing a certain type of parallel computing (map reduce) on very large amounts of data. There's a filesystem (hdfs) in there but it's pretty much designed for running such parallel jobs rather than being a clustered NAS. The filesystem is in some ways even irrelevant as there's actually support for various filesystems (Amazon S3, etc.).