Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Why RethinkDB? #71

Closed
lucasjinreal opened this issue Mar 13, 2018 · 1 comment
Closed

Why RethinkDB? #71

lucasjinreal opened this issue Mar 13, 2018 · 1 comment

Comments

@lucasjinreal
Copy link

lucasjinreal commented Mar 13, 2018 •
edited

As I further known that RethinkDB company were disbanded. Does RethinkDB is a long term choice to be used in such as a good library? (Just my confusion, not about library bugs or other issues).
@or-else
Copy link
Contributor

or-else commented Mar 13, 2018

When I selected the DB backend at the start of the project in 2014, RethinkDB looked like a good choice: it had clustering out of the box, it scaled really well, its NoSQL had joins. Yes, in 2018 it does not look as good - the company is gone. On the other hand it's still supported as a part of Apache Foundation, commits are still flowing, bugs being fixed: https://github.com/rethinkdb/rethinkdb.

MySQL is also supported.

@or-else or-else closed this as completed Mar 17, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@or-else @lucasjinreal