Live data from Hacker News

RethinkDB 2.1 is out: high availability

rethinkdb.com

71–80 of 108 posts

Re: RethinkDB 2.1 is out: high availability

#71
I've said before how I really appreciate the approach the guys at RethinkDB have taken... With the automatic failover support baked in, this would definitely be one of my go to solutions. The management/admin interface is much nicer than any other NoSQL database out there, while offering a lot of the things that a traditional RDBMS offers.

I'd probably reach for RethinkDB before Postgres or others simply for the better administrative experience. Especially for small teams or start-ups that don't have a dedicated DBA role.

For anyone curious, the databases I would most likely reach for, depending on the situation would be RethinkDB, ElasticSearch and Cassandra. I really do like MongoDB a lot as well, but RethinkDB offers the features with far less friction, though the query interface takes a bit of getting used to.

That said, I also like more traditional RDBMS options as well. I REALLY like what PostreSQL offers, but have no desire to administer such a beast, failover isn't really baked in, and the best options are only commercially available, at a significant cost. There are also hosted options for AWS and Azure for various SQL RDBMS. That said, I find being able to have data structure hierarchies in collections tends to be a better fit for MANY data needs.

Congratulations to Slava and everyone else at RethinkDB.

Re: RethinkDB 2.1 is out: high availability

#72

RethinkDB is great and has a lot of great features, however the thing that has impressed me the most is the way they communicate with the community. They are incredibly responsive and friendly on GitHub and IRC. It's not uncommon to get a response to a bug report within an hour or two (not that they have any obligation to this). They're incredibly nice. It looks like they try to follow http://www.defmacro.org/2013/04…

I could not agree with this more.. the development teams are definitely active with the community via github and irc... I followed along with the support for geolocation indexes, and was really happy to see that come into play.

It's taken a while to get to this point, but the development to get here has been methodical and incredibly well managed in terms of getting appropriate groundwork in place for a feature (like automatic fail-over) instead of just trying to hack at it or bolt it on the side. For that matter baking solutions for data streaming into the box, as opposed to less thoughtful options.

Re: RethinkDB 2.1 is out: high availability

#74
Great documentation with some useful examples and tutorials to get you started. I just tried it and very impressed with the performance and ease of use , especially the admin section is very handy. Need to try it with cluster , any docs/videos on creating the cluster with different machines across the globe?

Re: RethinkDB 2.1 is out: high availability

#75
post #47

This looks awesome .. great job guys .. Just a question on licenses . Server is "GNU Affero General Public License v3.0" and drivers are "Apache License v2.0." , so in simple english does it means that can i use make commercial products with backend as RethinkDB? these things always confuses me so apologies if i ask something stupid here ..

The AGPL confuses a lot of people on a lot of projects. It's actually really simple: If you modify the package (RethinkDB itself, in this case), you have to release your changes. That's it.

Re: RethinkDB 2.1 is out: high availability

#76

Earlier quoted context omitted.

RethinkDB can definitely act as a distributed key-value store (and a pretty good one). But I think the choice is highly dependent on your use-case and requirements. Could you go into a little more depth wrt your workload? (e.g. number of records, average record size, read/write ratio, expected ops/second, etc.)

Yea of course. We're basically talking about 10/90 write/read on JSON documents ~100kb in size with very low load, probably no more than 10-20 ops/second at peak. Records now are at 200,000 projected to grow 250k/year.

RethinkDB could definitely handle your load.. the advantage over CouchDB being you can do a bit more than just your value, and get indexing on other fields in your data structures. At your data load and growth, I'd be surprised if a small cluster couldn't handle your load for 8-10 years without issue... Since you're using JSON structures being able to query your data beyond keys is really nice... A document database is probably a more flexible option than a straight kv store.

If you wanted to stay closer to key/value with nice clustering and scaling options, I might suggest cassandra. To be honest, that would be overkill as a relatively small RethinkDB cluster would likely handle your load for several years without issue.

Re: RethinkDB 2.1 is out: high availability

#77
post #47

This looks awesome .. great job guys .. Just a question on licenses . Server is "GNU Affero General Public License v3.0" and drivers are "Apache License v2.0." , so in simple english does it means that can i use make commercial products with backend as RethinkDB? these things always confuses me so apologies if i ask something stupid here ..

AGPL is outright scaring. Patch it and suddenly you get in the business of releasing code, checking dependencies licenses, exposing the server code to anybody, etc. Deal breaker.

Re: RethinkDB 2.1 is out: high availability

#78
post #33

Earlier quoted context omitted.

I'm a cofounder of Couchbase. Almost all our code is Apache 2.0, and we make the Community builds available for everyone. Enterprise builds are free to use for a small test cluster. Unless you are a business where $5k/node looks reasonable to pay for peace of mind, you are probably fine with the Community Edition. A lot of the customers paying for Enterprise Edition are moving to Couchbase from Oracle, so they are pa…

As far as I can tell the Community Edition lags far behind the Enterprise Edition in stability and improvements. The latest available Community Edition is v3.0.1, released in October 2014. Since then, there has been a v3.0.2 edition released in December 2014, and a v3.0.3 released in March 2015, both of which had "critical bug fixes" according to the release notes, plus a new version, 3.1.0, released in July 2015. No…

Thanks for pointing this out... I don't have any experience with CouchBase/CouchDB. But I do appreciate open-source database options, especially those where the open version closely matches the commercially supported options.

Re: RethinkDB 2.1 is out: high availability

#79

Slava @ RethinkDB here. I'll be around all day to answer questions about the release (along with a few other engineers on our team). We're very excited about this release -- it makes the lives of RethinkDB users dramatically better because they won't have to wake up anymore in the middle of the night in case of most hardware failures :) It also took over a year to build and test, and has been one of the most challeng…

Would RethinkDB be a good choice for an invoicing web application? where you can't afford loss of data.

Re: RethinkDB 2.1 is out: high availability

#80

official JDBC drivers please :)

I know it's kind of a mixed bag. I'm also slightly, but not completely surprised that .Net and Java aren't officially supported.. I wouldn't expect JDBC support, but would expect to see a Java library for use with RethinkDB. Given the flexible nature of RethinkDB and other document databases, dynamic language environments tend to be much easier to support over static environments like .Net and Java.

Honestly, if you want to use RethinkDB with Java, it may be worthwhile to write a domain centered service with Node or Python and have that as an intermediary for Java. I've actually used Node on several occasions as a translation service for requests to foreign systems as sometimes there's a lot of disconnect in specific implementations of SOAP/WS-* services from Java/PHP/.Net etc. It tends to work very well for this use case.

I've actually been looking at GraphQL with some interest, and thinking this could be a pretty awesome option in front of RethinkDB, which would open up to pretty much any client that supports graph, which is limited right now...

Post reply on HN