4 ms·
There is a very recent Jepsen report on MongoDB. http://jepsen.io/analyses/mongodb-4.2.6 http://jepsen.io/analyses/mongodb-4.2.6 > Jepsen evaluated MongoDB ver
by dreur 6y ago
There is a very recent Jepsen report on MongoDB. http://jepsen.io/analyses/mongodb-4.2.6 http://jepsen.io/analyses/mongodb-4.2.6
> Jepsen evaluated MongoDB version 4.2.6, and found that even at the strongest levels of read and write concern, it failed to preserve snapshot isolation. Instead, Jepsen observed read skew, cyclic information flow, duplicate writes, and internal consistency violations. Weak defaults meant that transactions could lose writes and allow dirty reads, even downgrading requested safety levels at the database and collection level.
- scarface74 6y agoThen don’t use the defaults? Sql Server use to have an empty password as a default for the Sa user and it was trivial to find servers exposed on the internet with the default password. While part of the blame was MS’s, it’s always on the person who does the installation to know what they are doing.
- pritambaral 6y ago> Then don’t use the defaults? >> ... even at the strongest levels of read and write concern, it failed to ...
- wlll 6y agoYou should take a look at the Jepsen post. Kyle tested MongoDB at the highest integrity levels and still found problems.
- LittlePeter 6y agoI don't understand half of what this means. Does it rule out MongoDB if you care about your data?
- whalesalad 6y agoYes.
- jFriedensreich 6y agoyes, caring about your data and mongodb used to be even more opposites than now, but even with the improvements it's not a good fit.
- bborud 6y agoYes. Absolutely.
- bmm6o 6y agoThat's a great read, Kyle seems to really enjoy taking apart their claims.