3 ms·

I've heard about RethinkDB for the first time in 2013[1] and at the time it was described as "MongoDB with joins and auto-sharding". I also heard that one of t

I've heard about RethinkDB for the first time in 2013[1] and at the time it was described as "MongoDB with joins and auto-sharding". I also heard that one of the initial "killer-features" of RethinkDB was supposed to be a stored history, just like a big persistent data structure (in my understanding, similar to Datomic). In the video[2] a lot of time was spent describing the benefits of an append-only structure. [1]: https://www.youtube.com/watch?v=H9G1dCMTWps https://www.youtube.com/watch?v=H9G1dCMTWps [2]: https://www.youtube.com/watch?v=uDHc3lkr3Ns https://www.youtube.com/watch?v=uDHc3lkr3Ns

SamReidHughes 11y ago
> "MongoDB with joins and auto-sharding" It still is that. And (now) more. I don't think it was ever supposed to be a history-saving data structure -- that log-structured stuff is (I haven't watched the video, I'm assuming) about talking nice to SSD's. It was at one point, after that video, a single-machine memcache-compatible persistent key/value store, before the pivot to being clustered and having its own query API.