What is a feature module in NestJS and why should you use them instead of putting everything in AppModule?

Q: What is a feature module in NestJS and why should you use them instead of putting everything in AppModule?

// Feature module — owns everything about 'users' @Module({ imports: [TypeOrmModule.forFeature([User])], controllers: [UsersController], providers: [UsersService], exports: [UsersService], }) export class UsersModule {} // AppModule stays clean — just wires feature modules together @Module({ imports: [UsersModule, ProductsModule, OrdersModule], }) export class AppModule {} Single responsibility — each module owns one domain and nothing else. Independent testability — feature modules can be tested in isolation with a TestingModule. Clear ownership — team members know exactly where code for a domain lives. Lazy loading — heavy feature modules can be loaded on demand without touching AppModule. AppModule stays small — acts only as the composition root, not a dumping ground.

Difficulty: 5/10

module organization, dependency injection, scalability

A feature module groups all the code for a single domain — its controllers, services, repositories, and DTOs — into one cohesive unit. AppModule only imports feature modules rather than declaring every provider itself. This improves navigation, independent testability, clear ownership, and enables lazy loading.

Feature module pattern

Benefits of feature modules:

1
Single responsibility — each module owns one domain and nothing else.
2
Independent testability — feature modules can be tested in isolation with a TestingModule.
3
Clear ownership — team members know exactly where code for a domain lives.
4
Lazy loading — heavy feature modules can be loaded on demand without touching AppModule.
5
AppModule stays small — acts only as the composition root, not a dumping ground.

Scenario Questions

0-2 years experience

Follow-up Questions