RethinkDB: All content tagged as RethinkDB in NoSQL databases and polyglot persistence
Some interesting changes and new features in RethinkDB 1.13 announced yesterday. Namely:
replacing the protocol buffers-based protocol for a JSON-protocol
- how does the JSON protocol manage the non-JSON data types?
- how fast is a text-based protocol?
notifications about document changes
I’ve always said this was the coolest feature in CouchDB and that every database should support it.
a weird1 new
httpcommand to pull JSON data from the web
I’ve checked again the RethinkDB stability report and I’m not sure that reads as “yep, RethinkDB is finally production ready”.
Knowing the team there, I’m pretty sure this is coming from a use case I’m not seeing. ↩
Original title and link: RethinkDB 1.13: new protocol and push-pull APIs ( ©myNoSQL)
RethinkDB has just launched its 1.0 release to the public, and it’s offering a product geared toward NoSQL installations — and it will work on SSDs, traditional drives, and cloud-based services like AWS. The startup has also moved away from MySQL and now fully supports Memcached.
But RethinkDB is not the first product providing a Memcached compatible (disk) persistent storage engine. One year ago Membase was launched promising not only a persistent Memcached compatible solution, but also elastic scalability.
RethinkDB has also published a performance report (PDF) demonstrating RethinkDB speed compared to Membase and MySQL. But if I’m reading those numbers correctly, while RethinkDB leads the majority of query-per-second (QPS) benchmarks, MySQL is consistently showing better latency numbers (which is kind of weird). For a strong durability scenario, the benchmark shows MySQL delivering 2x QPS compared to RethinkDB.
Another interesting aspect of the RethinkDB 1.0 release is the licensing model —which I don’t fully get:
RethinkDB Basic is currently identical in feature-set to RethinkDB Premium and Enterprise. However, the paid versions of RethinkDB include phone and email support, access to all future updates, and volume licensing options.
Or spelled out on the TechCrunch post :
Akhmechet says that the free version will get security updates, but that it won’t necessarily receive new features in the future, whereas the premium version will.
Original title and link: RethinkDB Launches 1.0 Version With Memcached Compatibility Only (NoSQL databases © myNoSQL)
I didn’t know too much about RethinkDB until watching Tim Anglade’s interview with Slava Akhmechet and Mike Glukhovsky. There were mainly three things that caught my attention:
RethinkDB is firstly building a persistent memcached compatible solution to work with SSD. The reason for starting with a memcached-compatible system is that building it is much simpler than implementing a MySQL storage engine. On the other hand I think that having a persistent memcached might bring RethinkDB some customers to validate the technology.
Even if announced in 8-10 weeks at the time of the interview, I don’t think this implementation has been launched yet. Update: according to Tim, RethinkDB technology has been available to private beta users for a while now. But I still couldn’t find any reference to it on either the website or blog.
Next will come a MySQL engine optimized for SSD
- Replacing rotational disks with SSD shows an immediate bump in performance. But shortly after (months) performance seriously degrades.
It is this last point that I haven’t heard before. And I’d really be interested to understand:
- if it applies to all scenarios or if it is related to databases in general
- are there specific database scenarios (access patterns, read/write ratios) that lead to this behavior or will it manifest in general cases too
My current assumption is that this behavior occurs for write intensive databases only. But I’d really like to hear some better documented answers.
Update: First answer I got to the above questions comes from Travis Truman: The SSD Anthology: Understanding SSDs and New Drives from OCZ.
Update: RethinkDB guys have published a follow up: On TRIM, NCQ, and write amplification.