RethinkDB joins the Linux Foundation: What Happens Next
11–20 of 112 posts
Re: RethinkDB joins the Linux Foundation: What Happens Next
#12Sorry if this should be obvious but what is/are the killer feature/s of RethinkDB, what differentiates it from something like Redis or even CockroachDB?
RethinkDB has passed jepsen testing. *Fixed typo
Re: RethinkDB joins the Linux Foundation: What Happens Next
#13Re: RethinkDB joins the Linux Foundation: What Happens Next
#14Re: RethinkDB joins the Linux Foundation: What Happens Next
#15Honestly what needs to happen next is a serious effort to explain why or when rethink is better than mongo, cassandra, arango, aerospike, memsql, mysql, riak, or postgres, ++, not to mention all the TSDBs. On the event pushes I am unconvinced that message queues/computation graphs arent superior and that's another crowded space. When I last looked at it the advantages struck me as mostly incremental on the query lang…
Mongo has failed every jenkins test it's been put through, dunno about the status now though. Last I checked Mongo's default durability level was "data loss on power outage". Aerospike failed jenkins too, and not on small edge cases like Mongo, but with major dataloss.
Going by the problems Gitlab has recently with Postgres I wouldn't use that for a distributed database. Likely true for MySQL too.
* Yep. I meant to write Jepsen :)
Re: RethinkDB joins the Linux Foundation: What Happens Next
#16Sorry if this should be obvious but what is/are the killer feature/s of RethinkDB, what differentiates it from something like Redis or even CockroachDB?
As far as I know, there is no other solution which gets both things right.
I use it in PartsBox (https://partsbox.io/), a solution for keeping track of electronic components.
I am surprised more people aren't interested in changefeeds — the way I see it, it's the only way to implement multi-user webapps which update in real-time (as in: a change is made in one session and all other open sessions get the update immediately).
Re: RethinkDB joins the Linux Foundation: What Happens Next
#17Honestly what needs to happen next is a serious effort to explain why or when rethink is better than mongo, cassandra, arango, aerospike, memsql, mysql, riak, or postgres, ++, not to mention all the TSDBs. On the event pushes I am unconvinced that message queues/computation graphs arent superior and that's another crowded space. When I last looked at it the advantages struck me as mostly incremental on the query lang…
Comes down to jenkins for me. RethinkDB aced the jenkins tests. Mongo has failed every jenkins test it's been put through, dunno about the status now though. Last I checked Mongo's default durability level was "data loss on power outage". Aerospike failed jenkins too, and not on small edge cases like Mongo, but with major dataloss. Going by the problems Gitlab has recently with Postgres I wouldn't use that for a dist…
[1] https://aphyr.com/posts/329-jepsen-rethinkdb-2-1-5
[2] https://aphyr.com/posts/330-jepsen-rethinkdb-2-2-3-reconfigu...
Re: RethinkDB joins the Linux Foundation: What Happens Next
#18Sorry if this should be obvious but what is/are the killer feature/s of RethinkDB, what differentiates it from something like Redis or even CockroachDB?
I like to think of it as MongoDB done right. Above and beyond better consistency models and a broader, more well thought out API, they have an admin interface that is second to none (well SQL Management Studio might be slightly better). It's definitely better than any other "NoSQL" database.
A couple years ago, I had been considering it for a project, at the time it was missing a required feature for the project (geolocation indexes), so I wasn't able to use it then... but I followed the development of the feature, and prerequisites for that and the automatic master failover and the engineering discipline and planning was far better than pretty much any project I'd been exposed to ... The team(s) and their energies were not wasted, and I really appreciate what they have done.
I was sad to see the company shutter, but very happy to see the project under LF, and hope that it really takes off from here. It would be a pretty natural fit as an RDS service under Amazon and there are a few hosted options. Horizon also looks interesting compared to firebase.
This is another feature over competitors is that streaming updates is in the box, and not bolted on to oplog processing like competitors.
Re: RethinkDB joins the Linux Foundation: What Happens Next
#19Honestly what needs to happen next is a serious effort to explain why or when rethink is better than mongo, cassandra, arango, aerospike, memsql, mysql, riak, or postgres, ++, not to mention all the TSDBs. On the event pushes I am unconvinced that message queues/computation graphs arent superior and that's another crowded space. When I last looked at it the advantages struck me as mostly incremental on the query lang…
Comes down to jenkins for me. RethinkDB aced the jenkins tests. Mongo has failed every jenkins test it's been put through, dunno about the status now though. Last I checked Mongo's default durability level was "data loss on power outage". Aerospike failed jenkins too, and not on small edge cases like Mongo, but with major dataloss. Going by the problems Gitlab has recently with Postgres I wouldn't use that for a dist…
Re: RethinkDB joins the Linux Foundation: What Happens Next
#20I stayed away from Rethink in the past few years due to its uncertain future. Now I'm seriously interested. Looking forward to the next chapter of RethinkDB.