Here are some further thoughts of comparison of Redis vs Erlang NOSQL databases: Couchbase Mnesia Ri

Here are some further thoughts of comparison of Redis vs Erlang NOSQL databases: Couchbase Mnesia Riak

These are even more confusing but helps for resolution here:

Couchbase vs Redis

Couchbase master to master replication unique and also has no locking concepts!

http://db-engines.com/en/system/Couchbase%3BRedis

SImple for Redis:

For example, if you were working on a high performance algorithmic trading and you were pulling ticker prices out of a firehose and needing to store them at an insane rate so they could be processed, Redis is exactly the kind of datastore you would want to turn to for that — definitely not Mongo, CouchDB or MySQL.

http://rick-hightower.blogspot.ca/2014/04/well-put-when-should-you-use-mongodb-vs.html

This is also outdated

Booto Couchbase:

Memcached vs. Couchbase: We compared the performance of a standard Memcached (1.4.x) server with a Couchbase server (not version 2) and saw ~40% performance degradation with Couchbase.  This is mainly because Couchbase doesn’t not serve all the items from in-memory.

Yeh to Redisl

But Memcached can also run over a multi-threaded architecture, so unless you shard your Redis dataset, Memcached should have performance advantages here. That said, Redis supports pipelining, which is ~x5 faster than without pipelining, and Memcached doesn’t support pipelining capability.

Memory is cheap for this via a local server:

The one downside of Redis is the memory overhead. You need 2X RAM to store X data. Memcached is a little more efficient & transparent with memory organization – you can examine the slabs, etc.

http://www.quora.com/Performance/Does-Redis-or-Couchbase-noSQL-have-total-higher-throughput-when-used-as-a-memcached-replacement

This article could resell you on Couchbase:

http://www.computing.co.uk/ctg/news/2330148/viber-explains-why-it-ditched-mongodb-and-redis-in-favour-of-couchbase

It sounds like a NO to Mnesia:

1. Erlang only interface

2. Tables limited to 2GB

3. Deadlock prevention scales poorly

4. Network partitions are not automatically handled, must recombine tables automatically

http://nosql.mypopescu.com/post/711855931/all-erlang-riak-and-mnesia

Confused? Maybe I should start with Couchbase for the Erlang since it SHOULD be easier to integrate. I also like the lockless capability and they do cover all the major language bindings I want.

Join my FREE newsletter to learn more about which way I got

How to install Redis into Erlang

#comparison #Mnesia #Databases #rlang #NOSQL #Couchbase #Riak #Redis