3 ms·
RethinkDB is utterly defunct as a project, has not had a substantive release in years, and in my experience just flat out doesn't work. And let's don't even dis
by jeffbee 4y ago
RethinkDB is utterly defunct as a project, has not had a substantive release in years, and in my experience just flat out doesn't work. And let's don't even discuss Mongo. Asking yourself to choose between these is like selecting your favorite brand of thumbtack to step on.
- NetOpWibby 4y agoRethinkDB still works well for me /shrug
- gqewogpdqa 4y agoLol. When did you last use MongoDB and why is it a thumbtack?
- jeffbee 4y agoThe last time I used MongoDB was when it was necessary for me to demonstrate to decision makers that it silently loses data in trivial, common failure scenarios. Then I put it away and never used it again.
- eatonphil 4y agoI was about to defend it as having come far along but actually seems like it's still having some big issues as discussed in 2020 [0]. > Yeah, there's no workaround that I can find for 3.4 (duplicate effects), 3.5 (read skew), 3.6 (cyclic information flow), or 3.7 (read own future writes). I've arranged those in "increasingly worrying order"--duplicating writes doesn't feel as bad as allowing transactions to mutually observe each other's effects, for example. The fact that you can't even rely on a single transactions' operations taking place (or, more precisely, appearing to take place) in the order they're written is especially worrying. All of these behaviors occurred with read and write concerns set to snapshot/majority. [0] https://news.ycombinator.com/item?id=23290844 https://news.ycombinator.com/item?id=23290844