Re:Cassandra vs MongoDB vs CouchDB vs Redis vs Riak comparison
by roder on Thursday December 30, 2010 @02:02PM
(#2053224)
Riak also supports, in addition to HTTP, Protocol Buffers - a binary encoding protocol introduced by Google.
A few other notable Riak features include a JS or Erlang MapReduce API and full-text search.
Re:Cassandra vs MongoDB vs CouchDB vs Redis vs Riak comparison
by kkovacs on Thursday December 30, 2010 @02:12PM
(#2053262)
Thanks, amended RIAK with Erlang map/reduce and full-text search! (I need to read up on Protocol Buffers, but it sounds useful, too).
(Updated: typo)
Re:Cassandra vs MongoDB vs CouchDB vs Redis vs Riak comparison
by kkovacs on Thursday December 30, 2010 @02:02PM
(#2053223)
Protocols: great idea, thanks man, amended it!
Blazing fast: I mean compared to the other four.
Re:Cassandra vs MongoDB vs CouchDB vs Redis vs Riak comparison
by schmichael on Thursday December 30, 2010 @03:04PM
(#2053422)
I've had both MongoDB and Cassandra perform nearly as well as Memcache when getting a single document/row when the document was in memory in MongoDB and the row was cached (row cache, not just key cache, so again: fully in memory) in Cassandra.
In memory operations are fast in many databases. Redis's default configuration (vm-enabled no) just only does operations in memory (with an occasional sync to disk). That's terrible durability but fantastic performance. Most databases, including Redis, can be configured for either that sort of high-performance/low-durability or the opposite. It's just that their default settings/behaviors vary widely.
Updated:
Also Redis's main selling point is it's extensive data structure/operations support. "Blazingly fast" really depends on what your workload is and what you're comparing it against.