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



Column vs Row Stores: How do they compare?

Yesterday I’ve asked on Twitter about technical papers looking at column-stores vs row-stores. Most of the answers I’ve got are pointing to the research done by Daniel Abadi: Papers and Technical Reports. I’ll start with:

There’s also a discussion on this topic on Hacker News. Summarizing the points in that thread:

  • data for columns is stored together requiring less disk seeks when reading
  • this makes them good for aggregation on a few columns
  • when complete rows are needed this might make them worse
  • inserts, update, deletes could be slower in column-stores
  • more effective compression (same data types per column); this leads to less storage space

Justin Sheehy, Benjamin Darfler, Nicolae Claudius

Original title and link: Column vs Row Stores: How do they compare? (NoSQL database©myNoSQL)