A database that doesn't need to guarantee data integrity will always be faster.
How is the performance with the new v1 protocol? (still faster, I'm sure)
Re:MongoDB 3.4.0-rc3
by dajohnson89 on Tuesday February 07, 2017 @03:01PM
(#13592203)
Sorry if this is a stupid question. But how important is guaranteed integrity, in practice? (BTW, is what you're referring to considered transactions?) Obviously, for things like banking you need guarantees, but I'm not sure how often reads/writes to mongodb just disappear out of thin air.
>but I'm not sure how often reads/writes to mongodb just disappear out of thin air.
Which would imply you have to restore from backups continuesly. Or else any bug you run into might be the result of data corruption.
Its the fact that you cant even tell. And its not just about loosing data. If you rely upon a consistent world view (i.e. schedule payment, jobs scheduling, vms provision or shipping, account systems) the risk is unacceptable.
https://www.amon.cx/blog/rethinkdb-reviewed-by-a-mongo-fan/