What kind of workload RethinkDB is suitable for ?
1. Transactional
2. Analytical
3. Operational
RethinkDB joins the Linux Foundation: What Happens Next
31–40 of 112 posts
Re: RethinkDB joins the Linux Foundation: What Happens Next
#32Earlier quoted context omitted.
TBH, given the option... RethinkDB is probably the best case for anything that needs distribution/HA and automatic failover. SQL is a decent option, but you either pay a lot for HA, or you need to have a lot of domain knowledge or hire dedicated DBA support. Not that RethinkDB doesn't need some knowledge, their admin interface is great. The replication model is similar to Cassandra (ring + redundancy), while the mast…
Aerospike touches most of your points at much higher speed and scale. It is next gen redis, basically, with disk, with auto-sharding scale, with cross node queries. Cassandra is not difficult once you wrap your mind around column storage, and if you need that, no other storage style will do. The 15-node thing is also a major achilles heel. Who wants to commit to a stack that incurs massive technical debt in the event…
Aerospike doesn't offer many consistency guarantees. If you run it in a cluster on the cloud you are more than likely to see silent data loss [1].
It's not a fair comparison, RethinkDB is much safer. I'm sure, if you turn down the defaults on both read and write operations on RethinkDB you could scale it well past 15 nodes and with very high read and write throughput.
Re: RethinkDB joins the Linux Foundation: What Happens Next
#33What kind of workload RethinkDB is suitable for ? 1. Transactional 2. Analytical 3. Operational
The tagline on the site describes the most obvious use case: "RethinkDB pushes JSON to your apps in realtime. When your app polls for data, it becomes slow, unscalable, and cumbersome to maintain."
In their FAQ, they call out these types of applications: Collaborative web and mobile apps, Streaming analytics apps, Multiplayer games, Realtime marketplaces, Connected devices
Re: RethinkDB joins the Linux Foundation: What Happens Next
#34Earlier quoted context omitted.
I couldn't find any documentation on change feeds for Mongo after a quick google search. Could you post a link please?
It's call the "oplog": https://docs.mongodb.com/manual/core/replica-set-oplog/
While the oplog does provide some semblance of RethinkDB's changefeed, it's not nearly as powerful. With Rethink, you say you want a query, and rethink will let you know about changes to that query. Mongo just says "hey, here are operations that were done", and leaves the reconstruction to you".
So I guess Mongo+Meteor match up with RethinkDB... sort of.
Re: RethinkDB joins the Linux Foundation: What Happens Next
#35Earlier quoted context omitted.
Only RethinkDB gets you a) working changefeeds, where you can receive real-time changefeed updates to your queries, b) a well-implemented and Jepsen-proven distributed database. 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…
Well a) is provided by Mongo and is literally the reason why Meteor can do exactly what you described: multi-user webapps which update in real-time.
The oplog replication provided by Mongo is a very different mechanism than RethinkDB's change feeds. This is a pretty good overview of the differences: https://www.compose.com/articles/rethinking-changes-how-two-...
Re: RethinkDB joins the Linux Foundation: What Happens Next
#36I wish some company (apart from compose.io) would create a RethinkDB as a service (DBaaS).
I would totally love a dynamodb or firebase kind of payment structure!
I specifically excluded compose not because their service is not great (from what I've heard - it's excellent) but more so because they charge a premium for it.
Re: RethinkDB joins the Linux Foundation: What Happens Next
#37Earlier quoted context omitted.
Only RethinkDB gets you a) working changefeeds, where you can receive real-time changefeed updates to your queries, b) a well-implemented and Jepsen-proven distributed database. 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…
Well a) is provided by Mongo and is literally the reason why Meteor can do exactly what you described: multi-user webapps which update in real-time.
Unfortunately b) is critical to some, which Mongo did not fair well on:
Re: RethinkDB joins the Linux Foundation: What Happens Next
#38Earlier quoted context omitted.
Well a) is provided by Mongo and is literally the reason why Meteor can do exactly what you described: multi-user webapps which update in real-time.
I couldn't find any documentation on change feeds for Mongo after a quick google search. Could you post a link please?
[deleted]
Re: RethinkDB joins the Linux Foundation: What Happens Next
#39Linux foundation are collecting quite a lot "failed" projects and turn them to gold these days? I sometimes feel it is acting like a software goodwill store partially. Whatever that is, hope RethinkDB will do well in the future.
What are other examples?
Re: RethinkDB joins the Linux Foundation: What Happens Next
#40Earlier quoted context omitted.
I think you mean Jepsen? It's a slight exaggeration to say that RethinkDB aced it -- but they did very well[1] and (more importantly to me, honestly) Jepsen was used to find a subtle and nasty issue that was subsequently fixed.[2] [1] https://aphyr.com/posts/329-jepsen-rethinkdb-2-1-5 [2] https://aphyr.com/posts/330-jepsen-rethinkdb-2-2-3-reconfigu...
I've been having a lot of trouble with Jenkins at work today. So when I though Jepsen, I wrote Jenkins. Still feel they aced it. No one passes Jepsen on their first try. But RethinkDB is the first to immediately fix the issue. I wouldn't go as far as to call it a nasty issue. It would only happen if you got node failures while reconfiguring your cluster. And reconfiguring the cluster must be initiated by the admin an…
Sorry, clarification: by "nasty" I just meant "subtle", not "debilitating" -- and agreed that they did really well on Jepsen.