intermediateMongoDB Transactions — Single & Multi-Document ACID

Why should multi-document transactions be the exception rather than the default way of working in MongoDB?

They carry real overhead — they hold locks and resources across every operation until commit, and hold onto oplog entries longer than a normal write. The idiomatic MongoDB approach is modeling data so related things that must change together live in one document, atomic for free, reaching for a transaction only when that modeling genuinely isn't possible.

This is a Pro chapter

Sign in, then upgrade to Pro or Power to unlock this and the full Databases Mastery library.

Why should multi-document transactions be the exception rather than the default way of working in MongoDB?

Next Step

Continue to What should your application do when it receives a TransientTransactionError from MongoDB?← Back to all NoSQL questions