21 ms·

Announcing RethinkDB 2.3.6: the first release under community governance

128 points by TheMissingPiece 9y ago

deleted 9y ago
[deleted]
deleted 9y ago
[deleted]
skrebbel 9y ago
Anyone got an insight into how well this is going? Compared to when the company was active, how fast is progress? Would you bet on Rethink in this day and age?
- dis-sys 9y ago
  well, you can have a quick look at how many commits in the last 3 months vs total number of commits they had so far. not trying to judge anything as I no longer follow the project, but I think those numbers do tell the story.
  - bartvanH 9y ago
    Looking at the graphs on github you could say development has slowed down, but i'd like to argue that since there is no commercial incentive anymore the project seems to be much more focussed on stability. And when bugfixing you write less lines while spending the same amount of time. To me focus on stability is the most important thing in a database so this makes me happy as an ops person, get it stable first and then if needed add more features. though i think rethinkdb is already quite feature complete.
    - williamstein 9y ago
      In my personal opinion (based on heavily using RethinkDB for two years), many of the core issues of RethinkDB are related to performance, not bugs. I had bet on where RethinkDB would end up performance wise, had development continued with people who really understand how it works doing fulltime development.
- jwr 9y ago
  I did bet on it and so far I'm happy as long as it continues to work. Sure, I would like it to be developed further, but what I have now is great and works well. As for progress, it slowed down to non-existent during the handover period, and now seems to be picking up.
  - egeozcan 9y ago
    Great to hear that! Is there any issues close to being show-stoppers or any "it would have been immensely helpful to have this but I can work around it" features? Also, what would be the thing that RethinkDB is really good at that makes you keep using it?
    - jwr 9y ago
      I use it for two major reasons: 1. It's distributed. I can elastically add/remove nodes. I need this not so much for scalability, as for reliability, and I want to be future-proof. 2. Changefeeds. Nothing else even comes close, and my entire application is built around them. I have no show-stoppers. The thing works. Sure, I'd love to see some things done differently (ReQL looks nice at a first glance, but has many limitations in practice, causing code that ends up being quite complex), but overall even if it were to stay exactly the way it is now, I'd continue using it.
tracker1 9y ago
I'm really happy to see progress again. Hopefully we'll see more... I appreciate everyone that worked to make this possible. side note: the node driver in npm still hasn't been re-published with the license type in the package.json, so doesn't show the license. Only noting as this can cause issues in some organizations.
cupcakestand 9y ago
Just about to decide between Mongo and Rethink. I know HN is not on good terms with Mongo but I'd like to have insights on... - Setup of a replica set: is it easier/faster than with Mongo (which I find complicated)? - Sharding: Easier than with Mongo? - Rethink's query language: Is it really better than Mongo's after you used it for some time? Happy to hear more insights if you know more noteworthy stuff and please no bashing of any of them. Just try to make an educated decision.
- brimstedt 9y ago
  Depending on what your goal is: Did you consider elasticsearch? Reolication/clustering is real easy to set up. Sharding is easy. Scaling is easy. I cant comment on query language vs mongo or rethink, since my experience with them is too limited.
  - gnur 9y ago
    For one thing, it isn't really a database. You can use it as one, but where elasticsearch shines is mostly write once and read often. Correctness isn't the primary focus, so unless you are willing to lose some stuff, don't use elasticsearch as your primary database. https://www.elastic.co/blog/found-elasticsearch-as-nosql https://www.elastic.co/blog/found-elasticsearch-as-nosql
  - styfle 9y ago
    A couple more references regarding Elasticsearch as a primary datastore: https://www.quora.com/Why-shouldnt-I-use-Elasticsearch-as-my-primary-datastore https://www.quora.com/Why-shouldnt-I-use-Elasticsearch-as-my... https://stackoverflow.com/q/29841348/266535 https://stackoverflow.com/q/29841348/266535
- timmaxw 9y ago
  Former rethinkdb developer here. Sharding and replication just work out of the box. Connect the servers to each other with "rethinkdb --join otherserver", then use the web dashboard or the client APIs to specify how many shards and replicas for each table. Send queries to any server in the cluster and they get routed automatically.

deleted 9y ago

[deleted]

deleted 9y ago

[deleted]

skrebbel 9y ago

Anyone got an insight into how well this is going? Compared to when the company was active, how fast is progress? Would you bet on Rethink in this day and age?

dis-sys 9y ago
well, you can have a quick look at how many commits in the last 3 months vs total number of commits they had so far. not trying to judge anything as I no longer follow the project, but I think those numbers do tell the story.
- bartvanH 9y ago
  Looking at the graphs on github you could say development has slowed down, but i'd like to argue that since there is no commercial incentive anymore the project seems to be much more focussed on stability. And when bugfixing you write less lines while spending the same amount of time. To me focus on stability is the most important thing in a database so this makes me happy as an ops person, get it stable first and then if needed add more features. though i think rethinkdb is already quite feature complete.
  - williamstein 9y ago
    In my personal opinion (based on heavily using RethinkDB for two years), many of the core issues of RethinkDB are related to performance, not bugs. I had bet on where RethinkDB would end up performance wise, had development continued with people who really understand how it works doing fulltime development.
jwr 9y ago
I did bet on it and so far I'm happy as long as it continues to work. Sure, I would like it to be developed further, but what I have now is great and works well. As for progress, it slowed down to non-existent during the handover period, and now seems to be picking up.
- egeozcan 9y ago
  Great to hear that! Is there any issues close to being show-stoppers or any "it would have been immensely helpful to have this but I can work around it" features? Also, what would be the thing that RethinkDB is really good at that makes you keep using it?
  - jwr 9y ago
    I use it for two major reasons: 1. It's distributed. I can elastically add/remove nodes. I need this not so much for scalability, as for reliability, and I want to be future-proof. 2. Changefeeds. Nothing else even comes close, and my entire application is built around them. I have no show-stoppers. The thing works. Sure, I'd love to see some things done differently (ReQL looks nice at a first glance, but has many limitations in practice, causing code that ends up being quite complex), but overall even if it were to stay exactly the way it is now, I'd continue using it.

tracker1 9y ago

I'm really happy to see progress again. Hopefully we'll see more... I appreciate everyone that worked to make this possible. side note: the node driver in npm still hasn't been re-published with the license type in the package.json, so doesn't show the license. Only noting as this can cause issues in some organizations.

cupcakestand 9y ago

Just about to decide between Mongo and Rethink. I know HN is not on good terms with Mongo but I'd like to have insights on... - Setup of a replica set: is it easier/faster than with Mongo (which I find complicated)? - Sharding: Easier than with Mongo? - Rethink's query language: Is it really better than Mongo's after you used it for some time? Happy to hear more insights if you know more noteworthy stuff and please no bashing of any of them. Just try to make an educated decision.

brimstedt 9y ago
Depending on what your goal is: Did you consider elasticsearch? Reolication/clustering is real easy to set up. Sharding is easy. Scaling is easy. I cant comment on query language vs mongo or rethink, since my experience with them is too limited.
- gnur 9y ago
  For one thing, it isn't really a database. You can use it as one, but where elasticsearch shines is mostly write once and read often. Correctness isn't the primary focus, so unless you are willing to lose some stuff, don't use elasticsearch as your primary database. https://www.elastic.co/blog/found-elasticsearch-as-nosql https://www.elastic.co/blog/found-elasticsearch-as-nosql
- styfle 9y ago
  A couple more references regarding Elasticsearch as a primary datastore: https://www.quora.com/Why-shouldnt-I-use-Elasticsearch-as-my-primary-datastore https://www.quora.com/Why-shouldnt-I-use-Elasticsearch-as-my... https://stackoverflow.com/q/29841348/266535 https://stackoverflow.com/q/29841348/266535
timmaxw 9y ago
Former rethinkdb developer here. Sharding and replication just work out of the box. Connect the servers to each other with "rethinkdb --join otherserver", then use the web dashboard or the client APIs to specify how many shards and replicas for each table. Send queries to any server in the cluster and they get routed automatically.