News for hackers. Stuff that matters.

A comment on Benchmarks of Cassandra, HBase, VoltDB, MySql, Voldemort and Redis. Parent comment

Re:Benchmarks of Cassandra, HBase, VoltDB, MySql, Voldemort ... by taligent on Thursday August 30, 2012 @06:08AM (#4453883)
Even though Redis is moving from being a Memcached competitor to being more of a Cassandra competitor and MySQL is used by many of the world's largest websites (often as a glorified key-value store) they are odd choices.

Would anyone really use Redis for 'big data' ?

[ Parent | on HN ]
Re:Benchmarks of Cassandra, HBase, VoltDB, MySql, Voldemort ... by rb2k_ on Thursday August 30, 2012 @06:15AM (#4453899)
None of them do auto-sharding and master-master replication. This is the domain dynamo/bigtable-like systems (elasticsearch, riak, cassandra, hbase, voldemort)
[ Parent | on HN ]
Re:Benchmarks of Cassandra, HBase, VoltDB, MySql, Voldemort ... by taligent on Thursday August 30, 2012 @07:08AM (#4453993)
Actually AFAIK MySQL supports master-master and the Cluster version supports autosharding.
[ Parent | on HN ]
Re:Benchmarks of Cassandra, HBase, VoltDB, MySql, Voldemort ... by morgo on Thursday August 30, 2012 @11:05AM (#4454969)
Supports versus recommends are two different things. To do master-master correctly, you need either some sort of conflict resolution or a locking manager. MySQL has neither.
[ Parent | on HN ]