To what extent can the atomic storage of MongoDB leave your database unsafe after inserts or updates on my data?

In other words: What are the possibilities of my data not been (inserted or updated) on collection?

Imagine a big application running, many inserts/updates and other things on the same time and asynchronous, I want know if that are a problem? What the risks to my data?


1 Answer 1


Copying Joao's answer (from question comments) so this Q can have an A.

No, there is no problem with that. Single inserts/updates are atomic and reads are always consistent. However, you don't have transaction blocks in MongoDB (executing multiple inserts/updates atomically). – joao Feb 24 '14 at 13:26

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.