Home > slashdot > How Twitter Is Moving To the Cassandra Database

How Twitter Is Moving To the Cassandra Database

February 23rd, 2010 02:55 admin Leave a comment Go to comments

MyNoSQL has up an interview with Ryan King on how Twitter is transitioning to the Cassandra database. Here’s some detailed background on Cassandra, which aims to “bring together Dynamo’s fully distributed design and Bigtable’s ColumnFamily-based data model.” Before settling on Cassandra, the Twitter team looked into: “…HBase, Voldemort, MongoDB, MemcacheDB, Redis, Cassandra, HyperTable, and probably some others I’m forgetting. … We’re currently moving our largest (and most painful to maintain) table — the statuses table, which contains all tweets and retweets. … Some side notes here about importing. We were originally trying to use the BinaryMemtable interface, but we actually found it to be too fast — it would saturate the backplane of our network. We’ve switched back to using the Thrift interface for bulk loading (and we still have to throttle it). The whole process takes about a week now. With infinite network bandwidth we could do it in about 7 hours on our current cluster.” Relatedly, an anonymous reader notes that the upcoming NoSQL Live conference, which will take place in Boston March 11th, has announced their lineup of speakers and panelists including Ryan King and folks from LinkedIn, StumbleUpon, and Rackspace.

Source: How Twitter Is Moving To the Cassandra Database

Related Articles:

  1. Cassandra NoSQL Database 1.2 Released
  2. Digg Says Yes To NoSQL Cassandra DB, Bye To MySQL
  3. Cassandra 0.7 Can Pack 2 Billion Columns Into a Row
  4. Video: How SimpleGeo Built a Scalable Geospatial Database with Apache Cassandra
  5. Cassandra 1.1 Brings Cache Tuning, Mixed Storage Support
blog comments powered by Disqus