Exactly it's a bit more of work does make you prone to mistakes. This is what happens when you rewrite transaction on your application. See what happens with to

Exactly it's a bit more of work does make you prone to mistakes. This is what happens when you rewrite transaction on your application. See what happens with to a btc exchange using mongo who got hacked. https://dzone.com/articles/mongodb-bitcoin-how-nosql https://dzone.com/articles/mongodb-bitcoin-how-nosql (article is 2014) I'm a bit outdated with mongo since 2.4-2.6 . It's a bit traumatic and i'm never coming back to it. If in case I'll need a high atomicity and consistency for financial transaction i'll just use postgres with SERIALIZABLE transaction isolation. This solves everything. Checkout the redbook.io it's a bit outdated but you can see from stonebreaker's discussion that nosql + sql will merge, which is what happening or happened right now. Mongo having transaction, and SQL having json datatypes.