I am new to MongoDB, but last week I read a lot of new things on the net. What I get is that MongoDB does not follow ACID principles in the true sense, or we can say that MongoDB corresponds to ACID at the document level.
Now my question is why MongoDB should not have an acid property in documents / collections such as relational ones. I mean, this does not intentionally follow them or there is some technical limitation. If this is intentional, then why and what additional MonngoDb is achieved at the expense of the ACID victim?
Atomicity: - . Why Mongo can support atomicity in documents. If this is a deliberate sacrifice, then what additionally does MongoDB achieve here with a sacrifice of atomicity?
Consistency: - I don’t care, because I can achieve this at the application level and without much effort.
Isolation: The Mongo isolation model is similar to the auto commits transaction for relational databases. This internally means that a transaction can contain one DML statement that will be automatically committed. Why can't it support a mutiple statement in a transaction that is committed alone, and then gets visible for another transaction
Durable: - In a relational database, if the commit is completed and, unfortunately, the system crashes. Oracle can recover as soon as it returns, but why Mongo cannot, as I believe, both implement forward log entries.