Questions
12 of 25
1How do you define a TypeORM entity and register it in a NestJS feature module?
2How do you handle TypeORM migrations in a NestJS project?
3How do you run a transaction with Prisma in NestJS?
4How do you perform CRUD operations and add query methods to a Mongoose model in NestJS?
5How do you use Prisma with multiple databases in a single NestJS application?
6What is the difference between find(), findOne(), findOneOrFail(), and the Query Builder in TypeORM?
7What are the two main ways to run a database transaction in TypeORM with NestJS?
8How do you handle Prisma migrations in a CI/CD pipeline?
9How do you add schema middleware (hooks) and instance methods in NestJS Mongoose?
10How do you mock a repository in a NestJS unit test?
11How do you seed a database in a NestJS application?
12How do you implement a Unit of Work pattern to group database operations across repositories in NestJS?
13How do you implement optimistic locking with TypeORM to prevent lost updates in NestJS?
14How do you integrate Prisma into a NestJS application?
15How do you implement soft deletes in NestJS with TypeORM?
16How do you implement multi-tenancy with a shared database in NestJS TypeORM?
17How do you set up TypeORM in a NestJS application?
18How do you implement a custom TypeORM repository in NestJS?
19How do you propagate a TypeORM transaction across multiple services in NestJS?
20What are Prisma middleware and how do you use them for audit logging in NestJS?
21How do you set up Mongoose in a NestJS application and define a schema?
22How do you handle Mongoose transactions for multi-document atomic operations in NestJS?
23What is the repository pattern and why use it in NestJS?
24How do you handle database connection pooling and health checks in NestJS?
25How do you implement database read replicas in NestJS for read/write splitting with TypeORM?
12 / 25

How do you implement a Unit of Work pattern to group database operations across repositories in NestJS?

Create a UnitOfWork service that wraps dataSource.transaction() and provides per-type repositories from the transactional EntityManager. The calling service receives a repos object containing all repositories bound to the same transaction, eliminating the need to manually thread EntityManager through every method call.

Unit of Work implementation and usage
Unit of Work pattern benefits:
  1. 1

    Groups all repositories under a single shared transaction without threading EntityManager manually.

  2. 2

    The work callback receives repository instances already bound to the transactional manager.

  3. 3

    Add new entity types to the repos parameter as the domain grows — no service changes required.

  4. 4

    All writes commit atomically or roll back together — no partial state is ever persisted.

  5. 5

    Services remain focused on business logic; transaction infrastructure is fully encapsulated in UnitOfWork.