RethinkDB: An open-source distributed database built with love over three years
1–10 of 247 posts
Re: RethinkDB: An open-source distributed database built with love over three years
#2Congrats on the launch guys!
Re: RethinkDB: An open-source distributed database built with love over three years
#3How does RethinkDB perform when compared to open-source distributed databases built with hate?
Re: RethinkDB: An open-source distributed database built with love over three years
#4This took tenacity. Congrats on shipping.
Re: RethinkDB: An open-source distributed database built with love over three years
#5I'll ask the obvious question not in the FAQ: How is this different from MongoDB?
Re: RethinkDB: An open-source distributed database built with love over three years
#6Are there any performance tips or information? This looks really cool
Re: RethinkDB: An open-source distributed database built with love over three years
#7This certainly seems interesting enough to look into!
One note, there's a typo in the code in the tutorial on top
r.table('users).insert({'name': 'Slava', 'age': 29 }).run()
users needs a closing quote.
Re: RethinkDB: An open-source distributed database built with love over three years
#8Are there any performance tips or information? This looks really cool
Yeah, I'm curious too as to how it stacks up against MongoDB performance-wise and why I'd want to use one over the other.
Re: RethinkDB: An open-source distributed database built with love over three years
#9If authors are lurking here, link from github to a quick start page is broken: http://www.rethinkdb.com/docs/guides/basic_quickstart.html
GH issue https://github.com/rethinkdb/rethinkdb/issues/2
edit: fixed already!
Re: RethinkDB: An open-source distributed database built with love over three years
#10Are there any performance tips or information? This looks really cool
Yeah, I'm curious too as to how it stacks up against MongoDB performance-wise and why I'd want to use one over the other.
I'm sure they'll provide performance examples in due course but we should be conscious how difficult it is to do this in practice.
Sure they can take the shortcut and just produce some single case and claim 'faster than a.n. other db' and that will probably satisfy the 'my db is faster than your db' brigade.
However, based on the effort that appears to have gone into this product to get it to this stage, they probably wouldn't be happy with that.
More power to them!