30 July 2010

The Ruby Reflector

Topic

Hypertable

  Source Favicon
By Todd Hoff of High Scalability 4 months ago.
Email

…by Daniel Abadi. I have noticed that Bigtable, HBase, Hypertable, and Cassandra are being called column-stores with increasing frequency, due to their ability to store and access column families separately. This makes them appear to be in the same category as column-stores such as Sybase IQ, C-Store, Vertica, VectorWise, MonetDB, ParAccel, and Infobright, which also are able to access columns separately.

Cloud Economics, By The Square Foot by Rich Miller…

highscalability.com Read
  Source Favicon
By Todd Hoff of High Scalability 5 months ago.
Email

Record stores: BigTable, HBase, HyperTable, and Cassandra.

Scalable RDBMSs: MySQL Cluster, ScaleDB, Drizzle, and VoltDB.

The paper describes each system and then compares them on the dimensions of Concurrency Control, Data Storage Replication, Transaction Model, General Comments, Maturity, K-hits, License Language.

And the winner is: there are no winners. Yet. Rick concludes by pointing to a great convergence:

I believe that a few of these systems will …

highscalability.com Read
  Source Favicon
Email

HyperTable

CouchDb

MongoDb

Riak

Voldemort

On one end of the spectrum is Scalaris which is entirely memory-driven, and Redis which is primarily memory oriented (you can do background snapshots). Cassandra, BigTable, Hypertable, Hbase allow configuring how large the Memtable can get, so that provides a lot of control. The document stores - CouchDb, MongoDb and Riak - all seem to be using on-disk B+ trees, and Voldemort uses BDB and MySQL. Having …

vineetgupta.com Read