Re:Answers to common questions about RethinkDB
by coffeemug on Friday November 16, 2012 @06:19PM
(#4796379)
slava@rethink here. RethinkDB is new software and still has bugs (see: https://github.com/rethinkdb/rethinkdb/issues) We're working very hard to iron out all reported and known issues, and improve the testing infrastructure to find new ones. There is nothing critical that's wrong with the server that we know of, but I still prefer to wait until the test infrastructure is much more comprehensive before I can comfortably recommend people to put it in production. I suspect this process will take about three months.
That being said, if you choose to build analytics on top of RethinkDB, we'll support you all the way.
Re:Answers to common questions about RethinkDB
by StavrosK on Friday November 16, 2012 @09:52PM
(#4796964)
I'm building exactly that (it's on postgres now, but I'm considering moving to RethinkDB when it's more stable). It's good to know you have my back.
By the way, for the benefit of the commenters here, I checked RethinkDB two days ago for http://www.instahero.com (the analytics app I'm building), and I ran into a bug where RethinkDB's count() would only return half my data.
The team was very responsive and fixed the bug in a few hours (and pushed the fix so I could test it), so I'm very impressed by the response time. I can't hold the bug against them, because they do say it's not production-ready.
Also, I pointed out that the DB listening to interfaces other than localhost by default was a potential security risk and that, too, was fixed in around a day. Kudos.
I have to build an analytics db for commercial launch in February, it'll be a single machine cluster for the first few months. Would rethink be a risky choice?