Explain write concern and read concern in MongoDB.
Assesses fundamental understanding of MongoDB conventions, runtime behavior, and memory/performance considerations.
Hiring managers look for precision, avoidance of ambiguous jargon, and ability to explain trade-offs under real production conditions.
Write concern controls how many nodes must acknowledge a write before it counts as successful. w:1 means the primary acknowledged it; w:"majority" means a majority of replica set members did. Adding j:true ensures it is journaled to disk. Higher write concern is safer but slower.
Read concern controls the consistency guarantee of a read:
- local returns the node's latest data and can expose writes later rolled back.
- majority returns data acknowledged by a majority.
- linearizable guarantees the read reflects all prior majority-acknowledged writes.
- snapshot reads a consistent point in time, often used with transactions.
Combine them for the guarantee you need. For example, w:"majority" with readConcern:"majority" prevents reading data that might be rolled back. Financial writes often use majority, while high-throughput logging may accept w:1.
Candidate Response Strategy & Interview Tips
- Start with a concise one-sentence summary: Deliver a direct, confident answer first before expanding into nuances.
- Demonstrate real-world trade-offs: Discuss where this approach excels and when you would avoid it in production systems.
- Discuss complexity & edge cases: Proactively explain time/space complexity or boundary conditions (null values, scale limits).
- Prepare for interviewer follow-ups: Technical hiring panels frequently probe deeper into concurrency, backward compatibility, or alternative libraries.