Live data from Hacker News

RethinkDB 2.0 is now production ready

rethinkdb.com

111–120 of 156 posts

Re: RethinkDB 2.0 is now production ready

#111

Earlier quoted context omitted.

We'll be publishing a performance report soon (we didn't manage to get it out today). Rough numbers you can expect for 1KB size documents, 25M document database: 40K reads/sec/server, 5K writes/sec/server, roughly linear scalability across nodes. We should be able to get the report out in a couple of days.

Can you give a ballpark on how many nodes Rethink can scale up to, and any future roadmap in that direction? Thank you for the fantastic product, by the way! :)

We often run tests scaling up to ~40 nodes without problems. You could probably push Rethink quite further than that, but I think over 100 nodes would be hard. The goal is to keep pushing the boundary indefinitely.

Re: RethinkDB 2.0 is now production ready

#112

Earlier quoted context omitted.

My understanding is that Couchbase is just a key-value store, while RethinkDB has much more features including complex queries, sorting, joins, indices...

Couchbase has indexing, map reduce, and full text. Also a mobile sync connector.

Couchbase conflict resolution is really basic, assuming you mean distributed in a wan context (eg xdcr). Riak would represent the state of the art in this respect (random internet endorsement, I'm not affiliated with anything, just a user who has worked with both systems).

Re: RethinkDB 2.0 is now production ready

#113

Well done guys! Have been wanting to use rethinkdb for my project but it didn't have the "production ready" tag, so Mongodb was chosen instead. Now I can confidently switch! It's a pity the Go driver isn't quite there yet though.

I hope to have a "production ready" version of the driver ready in about a month. I know its slow but currently I am the only dev working on maintaining this project and all work is done in my free time. If you have any further questions I would be more than happy to answer them on https://gitter.im/dancannon/gorethink . Thanks!

Hey no worries I absolutely understand. Apologies for lamenting on the pace/state of your contribution and thanks for your time and effort.

Re: RethinkDB 2.0 is now production ready

#114
post #35

Earlier quoted context omitted.

+1 RethinkDB's realtime capabilities would fit perfectly with Meteor.

How? Meteor's server-side architecture is still oriented around polling the DB, and I believe that's because many apps are still explicit request-response oriented.

No, Meteor's server-side architecture uses MongoDB's replication log that is analyzed to get updates.

Re: RethinkDB 2.0 is now production ready

#115

Earlier quoted context omitted.

Do you have any project on github that works like that?

Not that's open source, but I can do a little write up article and share a sample app that shows how to do it.

I'd personally love to see this. Think it would be very valuable to the community.

Re: RethinkDB 2.0 is now production ready

#116

Earlier quoted context omitted.

Not that's open source, but I can do a little write up article and share a sample app that shows how to do it.

I'd personally love to see this. Think it would be very valuable to the community.

I second this. I am getting happier by the day with my react client side architecture and am now casting an eye to my server side (currently a Django-rest-framework api) to determine what the best fit there would be.

Re: RethinkDB 2.0 is now production ready

#117

Earlier quoted context omitted.

Do you have any project on github that works like that?

Not that's open source, but I can do a little write up article and share a sample app that shows how to do it.

Would love to see this as well. I'm the creator of the Scala driver and always looking for ways to improve the api.I know you may not be using Scala but having insight on how other devs would use it always helps. Plus I'm still trying to figure out the best way to do change feeds hehe.

Re: RethinkDB 2.0 is now production ready

#118

Earlier quoted context omitted.

Can you give a ballpark on how many nodes Rethink can scale up to, and any future roadmap in that direction? Thank you for the fantastic product, by the way! :)

We often run tests scaling up to ~40 nodes without problems. You could probably push Rethink quite further than that, but I think over 100 nodes would be hard. The goal is to keep pushing the boundary indefinitely.

Thank you Slava. Put all these numbers on the front of your webpage :)

Re: RethinkDB 2.0 is now production ready

#119
post #35

Earlier quoted context omitted.

+1 RethinkDB's realtime capabilities would fit perfectly with Meteor.

How? Meteor's server-side architecture is still oriented around polling the DB, and I believe that's because many apps are still explicit request-response oriented.

As @imslavko said, when using Meteor with MongoDB (which I believe is the only production ready DB driver) it observes the oplog [1] for changes. You can use the polling observer too though.

You can find out more about the LiveUpdate core project of Meteor on their site [2] - it basically says the implementation of Live Updates for each db driver is independent to what the db is capable of. Specific mention of RethinkDB and Firebase is made as DBs that are built with making realtime data something that you get for relatively little work.

[1] https://github.com/meteor/meteor/blob/devel/packages/mongo/o...

[2] https://www.meteor.com/livequery

Post reply on HN