ALL COVERED TOPICS

NoSQL Benchmarks NoSQL use cases NoSQL Videos NoSQL Hybrid Solutions NoSQL Presentations Big Data Hadoop MapReduce Pig Hive Flume Oozie Sqoop HDFS ZooKeeper Cascading Cascalog BigTable Cassandra HBase Hypertable Couchbase CouchDB MongoDB OrientDB RavenDB Jackrabbit Terrastore Amazon DynamoDB Redis Riak Project Voldemort Tokyo Cabinet Kyoto Cabinet memcached Amazon SimpleDB Datomic MemcacheDB M/DB GT.M Amazon Dynamo Dynomite Mnesia Yahoo! PNUTS/Sherpa Neo4j InfoGrid Sones GraphDB InfiniteGraph AllegroGraph MarkLogic Clustrix CouchDB Case Studies MongoDB Case Studies NoSQL at Adobe NoSQL at Facebook NoSQL at Twitter

NAVIGATE MAIN CATEGORIES

Close
Thursday, 18 November 2010
‹ Back

HBase at Facebook and Why Not MySQL or Cassandra

About:
,
,
,
,

Jeremiah Peschka on:

What makes this decision interesting is not just the reasons that Apache HBase was chosen, but also the reasons that MySQL and Cassandra were not chosen.

Briefly:

  • not MySQL: because sharding can be very difficult at the scale of Facebook messages system
  • not Cassandra: because of replication behavior
Credit Jeremiah Peschka

Update: There were a few pointing out that the original article is inaccurate. Todd Lipcon’s comment is providing some corrections pretty much demoting all technical arguments in the post. Todd concludes:

That said, the point about existing operational experience with Hadoop and HDFS is absolutely correct. There is a large Hadoop team at Facebook and they are truly experts in the technology. The HBase team there is also growing quickly and have been great contributors in the last several months.

Original title and link: HBase at Facebook and Why Not MySQL or Cassandra (NoSQL databases © myNoSQL)

via: http://facility9.com/2010/11/18/facebook-messaging-hbase-comes-of-age