3 ms·
Under protocols you may want to specify MongoDB's as BSON and Cassandra's as Thrift. That would be more helpful than "binary/custom". Updated: Also Redis's ma
by schmichael 16y ago
Under protocols you may want to specify MongoDB's as BSON and Cassandra's as Thrift. That would be more helpful than "binary/custom".
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.
- kkovacs 16y agoProtocols: great idea, thanks man, amended it! Blazing fast: I mean compared to the other four.
- schmichael 16y agoI'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.
- jfb 16y agoSorted sets. I mean, c'mon. That's worth the price of admission right there.
- roder 16y agoRiak 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.
- kkovacs 16y agoThanks, 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)