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

Redis and HBase for Mozilla Grouperfish Storage

About Mozilla Grouperfish architecture and choosing a scalable storage solution:

Given our access patterns (insert documents, update clusters, re-process entire collections, fetch lists of clusters), efficient sequential access to selected parts of the data is very important. Sorted, column oriented storage seems to be the way to go. There are other pros and cons (single point of failure, write throughput, hardware requirements), but if we don’t cater to our use case, those won’t ever matter.

And this is what the planned solution is going to look:

  • service layer: node.js
  • data layer: Redis + HBase
  • processing layer: RabbitMQ, Mahout, Jetty
  • batching layer: Hadoop

Grouperfish Architecture: HBase, Redis

Original title and link: Redis and HBase for Mozilla Grouperfish Storage (NoSQL databases © myNoSQL)

via: http://blog.mozilla.com/data/2011/03/08/scalable-text-clustering-for-the-web/