MongoDB Production Checklist

Application writes use w: majority; the actual connection string has been checked, not assumed.

Operations that must survive a crash use j: true.

Reads that inform irreversible decisions use readConcern majority.

Secondary reads either use a causally consistent session or are limited to operations that tolerate staleness.

maxStalenessSeconds is set wherever secondary reads are used.

Retry logic treats wtimeout as 'unknown outcome' and is idempotent.