Re:RethinkDB 1.7: hot backup, atomic set/get, 10x insert per...
by apendleton on Wednesday July 03, 2013 @02:36PM
(#5986592)
Are there any plans for Couch-style incrementally-computed aggregates/views in RethinkDB?
Re:RethinkDB 1.7: hot backup, atomic set/get, 10x insert per...
by alexpopescu on Wednesday July 03, 2013 @03:09PM
(#5986839)
Considering RethinkDB's secondary indexes can be defined around pretty complex ReQL expressions [1] you could already get some of it already.
[1] http://rethinkdb.com/docs/pragmatic-faq/#how-do-i-take-advan...
Re:RethinkDB 1.7: hot backup, atomic set/get, 10x insert per...
by apendleton on Wednesday July 03, 2013 @03:29PM
(#5986975)
Yeah, I thought about that, but it seems like you can only use them to get the "map" part of map/reduce... no aggregation. Unless I'm missing something.
Re:RethinkDB 1.7: hot backup, atomic set/get, 10x insert per...
by alexpopescu on Wednesday July 03, 2013 @03:32PM
(#5986991)
> Yeah, I thought about that, but it seems like you can only use them to get the "map" part of map/reduce... no aggregation. Unless I'm missing something.
I think that's correct.
Re:RethinkDB 1.7: hot backup, atomic set/get, 10x insert per...
by coffeemug on Wednesday July 03, 2013 @03:02PM
(#5986788)
Yes. RethinkDB is really well set up to do this due to the underlying parallelized map/reduce infrastructure. This feature is a matter of scheduling priorities. I don't have an ETA yet, but it will almost certainly get done in the medium-term.
Re:RethinkDB 1.7: hot backup, atomic set/get, 10x insert per...
by apendleton on Wednesday July 03, 2013 @03:05PM
(#5986812)
Awesome. If there's a Github issue about it I'd be interested to follow it.
Re:RethinkDB 1.7: hot backup, atomic set/get, 10x insert per...
by coffeemug on Wednesday July 03, 2013 @03:19PM
(#5986910)
I just added one -- see https://github.com/rethinkdb/rethinkdb/issues/1118.
Please keep in mind that this is not an authoritative comparison and it may contain mistakes. Plus as for many such systems, the aspects covered are in reality not that easy to be described in just a few words.
Platforms:
- RethinkDB: Linux, OS X
- CouchDB: where Erlang VM is supported
Data model: - both JSON
Data access:
- RethinkDB: Unified chainable dynamic query language
- CouchDB: key-value, incremental map/reduce
Javascript integration:
- RethinkDB: V8 engine; JS expressions are allowed pretty much anywhere in the RQL
- CouchDB: Spindermonkey (?); incremental map/reduce, views are JS-based
Access languages:
- RethinkDB: Protocol Buffers
- CouchDB: HTTP
Indexing:
- RethinkDB: Multiple types of indexes (primary key, compound, secondary, arbitrarily computed)
- CouchDB: incremental indexes based on view functions
Sharding:
- RethinkDB: Guided range-based sharding (supervised/guided/advised/trained)
- CouchDB: -
Replication:
- RethinkDB - sync and async replication
- CouchDB - bi-directional replication can be set between multiple CouchDB servers
Multi-datancenter:
- RethinkDB - Multiple DC support with per-datacenter replication and write acknowledgements
- CouchDB - (?)
MapReduce:
- RethinkDB: Multiple MapReduce functions executing ReQL or Javascript operations
- CouchDB: views are map/reduce but they need to be pre-defined
Consistency model:
- RethinkDB: Immediate/strong consistency with support for out of date reads
- CouchDB: http://guide.couchdb.org/draft/consistency.html
Atomicity:
- both document level
Durability:
- both durable
Storage engine:
- RethinkDB: Log-structured B-tree serialization with incremental, fully concurrent garbage compactor
- CouchDB: B-tree
Query distribution engine:
- RethinkDB: Transparent routing, distributed and parallelized
- CouchDB: none
Caching engine:
- RethinkDB: Custom per-table configurable B-tree aware caching
- CouchDB: none (?)