RethinkDB 2.2: atomic changefeeds, parallel scans, improved runtime | Hacker News Reader

RethinkDB 2.2: atomic changefeeds, parallel scans, improved runtime

rethinkdb.com

78 pointscoffeemug16 comments

In case anyone is interested, they're going to do a live stream on youtube about this release in a couple of hours: https://www.youtube.com/watch?v=jt9EnhX24HU

Looks like a great release! Can't wait to get this installed and going on our system. We use getAll almost everywhere, so that's going to be a very, very welcome improvement.

Awesome to see Rethink continue to mature quickly and nicely.

This is a really exciting release! Atomic changefeeds make it much more consistent and robust to subscribe to realtime data in the client, and the performance improvements look incredible.

Join our webcast in 10 min :) https://youtu.be/jt9EnhX24HU

From the FAQ:

We recommend RethinkDB servers have at least 2GB of RAM

Why does it needs so much memory?

Because it's 2015.

And it’s a database with indexes and caches.

Makes sense to reduce disk accesses but maybe there are fixed data structures allocated? Since otherwise they should advice a given percentage of memory compared to dataset size instead of a fixed amount.

You may find this article helpful: http://rethinkdb.com/docs/memory-usage/

The article describes how RethinkDB uses memory to reduce disk access and process queries, as well as how to reduce its memory usage with `--cache-size`.

I really like Rethink, but are there easy to use hosting services for it? Like ElephantSQL or Mongolabs.

Check out compose.io

https://www.rethinkdb.com/blog/compose/

https://www.compose.io/rethinkdb/

There's a fairly major breaking change for a minor version bump.

I don't think there are actually any breaking changes. The release notes say "includeInitial" is breaking, but I think all of your existing application code will continue to run the same if you upgrade RethinkDB. It's just that new code using includeInitial will fail on old versions of RethinkDB.

In 2.1 some changes commands included an initial value. Now none do unless you add the flag. If you depended on that behavior, your app could break.

Thanks, I stand corrected! I always ignored initial values so I forgot about that case.

We maintain a stable LTS release (v2.0) for those who cannot tolerate breaking changes.

Feature releases (e.g. 2.1, 2.2) include new features and do break compatibility on occasion (so we can quickly introduce new behavior). Any breaking changes are well-documented in the release notes[1], so you can have a smooth upgrade path.

Minor releases (e.g. 2.1.1, 2.1.2) do not have breaking changes, only bugfixes and minor improvements.

I just opened an issue so we can document this more clearly: https://github.com/rethinkdb/docs/issues/948

[1] https://github.com/rethinkdb/rethinkdb/releases

Reply on news.ycombinator.com