How do you handle Mongoose transactions for multi-document atomic operations in NestJS?
Inject the Mongoose Connection with @InjectConnection() and call startSession() to create a session. Start a transaction on the session and pass { session } to every query that must participate. Commit on success, abort on error, and always end the session in a finally block.
- 1
Mongoose transactions require a MongoDB replica set — single-node standalone instances do not support them.
- 2
Use @InjectConnection() to get the Mongoose Connection for creating sessions.
- 3
Pass { session } to every query inside the transaction or the operation runs outside it.
- 4
Model.create() with a session requires the array form: create([data], { session }).
- 5
Always call session.endSession() in finally — not releasing it leaks the session from the pool.
Scenario Questions
0-2 years experience
- 1Suppose you need to create an order document and decrement the stock count in a separate products collection. How would you implement that using a Mongoose transaction inside a NestJS service?
- 2If you forget to call session.endSession() after completing a transaction, what could the NestJS application experience over time?
2-5 years experience
- 1You added a transaction to a checkout flow, but the request sometimes hangs and never returns. Walk me through how you'd debug the problem.
- 2After introducing a new repository that uses the same Mongoose model but doesn't accept a session argument, your existing transaction started failing. Why does that happen and how would you fix it?
5-8 years experience
- 1Design a reusable transaction wrapper for NestJS that can be applied across multiple services and includes automatic retries for transient errors. What trade‑offs do you need to consider?
- 2At high traffic, how would you monitor the health of long‑running Mongoose transactions and prevent them from exhausting the connection pool?
8+ years experience
- 1Your team is moving from a monolithic NestJS app to a set of microservices, each with its own MongoDB instance. How would you redesign multi‑document atomic operations that currently rely on Mongoose transactions?
- 2Discuss the long‑term maintenance implications of embedding transaction logic directly in services versus using a dedicated transaction manager or library. Which approach would you recommend for a large, cross‑team codebase and why?
Follow-up Questions
- What happens if one of the writes inside the transaction throws an exception?
- How do you make sure every repository method participates in the same session?
- Can you talk about the performance impact of using transactions in MongoDB?