Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

RethinkDB 2.1 is out: high availability

rethinkdb.com

Post reply on HN
Print view View original

91–100 of 108 posts

Re: RethinkDB 2.1 is out: high availability

#91

Post by [deleted] »

lobster_johnson wrote: post #88
coffeemug wrote: post #2

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…

Are there plans (heh) to write an optimizing planner that can automatically evaluate which indexes to use?

[deleted]

Re: RethinkDB 2.1 is out: high availability

#92

Post by coffeemug »

tom9729 wrote: post #87
uberneo wrote: 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 ..

I'm also curious about this. It seems like the ASL drivers are a bit of a loophole. What happens if later Rethink decides to relicense their drivers as AGPL with a commercial option for businesses? Can 3rdparty drivers be ASL or is that a violation of the AGPL?

We guarantee that we'll grant anyone who wants to release a driver a more permissive license. We're also happy to do it in writing, both for driver developers and users.

Theoretically we can stop doing that in the future and keep changing the protocol, but that would alienate all of our users. That would be an insane decision, and we'll never ever do it.

Re: RethinkDB 2.1 is out: high availability

#93

Post by reactor »

gauravphoenix wrote: post #73

official JDBC drivers please :)

It's a shame that they don't have Java support. Although rethinkdb was a better fit, lack of official Java driver is what prompted the company I work for to go with another doc db. I could see they are working on it, but it is too late for us unfortunatley.

Re: RethinkDB 2.1 is out: high availability

#94

Post by barosl »

> Always on – you can add and remove nodes from a live cluster without experiencing downtime.

This has been a long-awaited feature for me. While I loved nearly every aspect of RethinkDB, it was the reason that made me hold back from using RethinkDB. Good to see RethinkDB keep improving!

Re: RethinkDB 2.1 is out: high availability

#95

Post by d_luaz »

williamstein wrote: post #21

This is soooo awesome. I started rewriting SageMathCloud to use RethinkDB when I learned in May about your plans to support high availability. I've been rewriting everything, doing tests (building from sources, then using the beta you kindly provided), and finally after months of work, I'm ready to release the new version of SageMathCloud last night, but RethinkDB 2.1 isn't out yet. So I'm torn about whether to go wi…

I would like to encourage more people to share on StackBus (FYI, I built it) on why they use RethinkDB and what they use it for, to provide more insights to those who are evaluating RethinkDB

http://www.stackbus.com/

Re: RethinkDB 2.1 is out: high availability

#96

Post by hendzen »

mikegioia wrote: post #20
coffeemug wrote: post #15

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.

For traffic that low, you could use basically anything.

Re: RethinkDB 2.1 is out: high availability

#98

Post by jchrisa »

WaltPurvis wrote: post #61
jchrisa wrote: 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…

If you want to use the latest features without waiting for a CE build, it's getting easier to build Couchbase Server all the time. This readme is where our new hires start: https://github.com/couchbase/manifest

Re: RethinkDB 2.1 is out: high availability

#99

Post by cihangirb »

WaltPurvis wrote: post #61
jchrisa wrote: 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…

Hi, it seems we missed correcting this page. It takes months not weeks to release updates to CE. The releases after 3.0.1 (3.0.2 and others) are maintenance releases with bug fixes. 3.1 is a recent release and it does contain features. We would normally push a community edition version or 3.1 in several months after the release but we are close to pushing out 4.0 and that incorporates 3.1 enhancements and more. I am expecting that we will get a 4.0 community edition out that will supersede the 3.1 release and will deliver these features to you soon.
Post reply on HN