What is the repository pattern and why use it in NestJS?

Q: What is the repository pattern and why use it in NestJS?

// Repository interface — ORM-agnostic contract export interface IUsersRepository { findById(id: number): Promise ; findByEmail(email: string): Promise ; save(user: Partial ): Promise ; delete(id: number): Promise ; } // TypeORM implementation @Injectable() export class TypeOrmUsersRepository implements IUsersRepository { constructor( @InjectRepository(UserEntity) private repo: Repository , ) {} findById(id: number) { return this.repo.findOne({ where: { id } }); } findByEmail(email: string) { return this.repo.findOne({ where: { email } }); } async save(data: Partial ) { return this.repo.save(data); } async delete(id: number) { await this.repo.delete(id); } } // Module — bind interface token to implementation @Module({ imports: [TypeOrmModule.forFeature([UserEntity])], providers: [ { provide: 'IUsersRepository', useClass: TypeOrmUsersRepository }, UsersService, ], }) export class UsersModule {} // Service — depends on interface, not TypeORM @Injectable() export class UsersService { constructor( @Inject('IUsersRepository') private repo: IUsersRepository, ) {} } Testability — swap the real implementation for a mock by changing one provider in the test module. ORM independence — switching from TypeORM to Prisma only requires a new IUsersRepository implementation. Domain clarity — the interface expresses what the domain needs, not what the ORM can do. Single responsibility — data access logic is isolated from business logic in the service. Use InjectionToken or a string token as the interface binding key; inject with @Inject('IUsersRepository').

Difficulty: 5/10

abstraction, dependency injection, data access

The repository pattern abstracts data access behind a typed interface. Services depend on the interface rather than the ORM directly, making code testable with mock implementations, ORM-agnostic, and easier to change. The interface becomes the contract between the domain layer and the data layer.

Repository interface, implementation, and DI binding

Repository pattern benefits:

1
Testability — swap the real implementation for a mock by changing one provider in the test module.
2

What is the repository pattern and why use it in NestJS?

Difficulty: 5/10

abstraction, dependency injection, data access

The repository pattern abstracts data access behind a typed interface. Services depend on the interface rather than the ORM directly, making code testable with mock implementations, ORM-agnostic, and easier to change. The interface becomes the contract between the domain layer and the data layer.

Repository interface, implementation, and DI binding

Repository pattern benefits:

1
Testability — swap the real implementation for a mock by changing one provider in the test module.
2

What is the repository pattern and why use it in NestJS?

The repository pattern abstracts data access behind a typed interface. Services depend on the interface rather than the ORM directly, making code testable with mock implementations, ORM-agnostic, and easier to change. The interface becomes the contract between the domain layer and the data layer.

What is the repository pattern and why use it in NestJS?

The repository pattern abstracts data access behind a typed interface. Services depend on the interface rather than the ORM directly, making code testable with mock implementations, ORM-agnostic, and easier to change. The interface becomes the contract between the domain layer and the data layer.

Scenario Questions

Follow-up Questions