Re:Announcing RethinkDB 2.3.6: the first release under commu...
by cupcakestand on Tuesday July 18, 2017 @10:39AM
(#14796851)
> but Mongo looks terrible if you ask about losing data or leaking memory
Sorry, but this is just not true for many years now. Mongo has its warts but reading old stuff again and again feels strange and like pure hate. If your claims have some recent sources I am happy to hear them.
Re:Announcing RethinkDB 2.3.6: the first release under commu...
by nieve on Wednesday July 19, 2017 @05:24AM
(#14802964)
The list of problems goes on, but if you want really current at a local presentation a few weeks ago a user who's actually pretty positive about MongoDB reported data loss without hardware failure with what is supposedly a safe configuration. If even experienced people who like Mongo are still losing data eight years after publich release there's a problem. The claim that it's "not true for many years now" is the result of buying into PR and fanboyism.
Re:Announcing RethinkDB 2.3.6: the first release under commu...
by cupcakestand on Wednesday July 19, 2017 @09:13AM
(#14804013)
Again the same old accusations without a single source ('local presentation', of course!).
Re:Announcing RethinkDB 2.3.6: the first release under commu...
by kerkeslager on Wednesday July 19, 2017 @01:51PM
(#14806313)
February 2017: https://jepsen.io/analyses/mongodb-3-4-0-rc3
I would expect these bugs to keep occurring, because they're still approaching the development of the consensus algorithm incorrectly. Instead of formally proving correctness, they're doing something that seems right and then patching bugs when they are discovered.
Think of this like Maslowe's hierarchy of needs. Sharding and replication are up at the top with self-actualization stuff like job satisfaction and feeling love toward animals. Meanwhile Mongo is missing the real basic stuff, like actually keeping your data, which is down with food, water, and shelter. You might think you care about replication, but you don't care about replication when both your database servers run out of memory at the same time.