What is scope propagation in NestJS and why can it impact performance?

Difficulty: 6/10

Dependency Injection, Request Scope, Performance

When a provider is REQUEST-scoped, every provider that injects it also becomes REQUEST-scoped automatically — this propagates up the entire dependency chain. In high-throughput APIs this causes significant overhead because the full chain must be constructed and torn down on every request instead of reusing singletons.

Scope propagation is automatic and silent — NestJS promotes all consumers of a REQUEST-scoped provider to REQUEST scope without any explicit annotation. This can cause unexpected performance issues if a REQUEST-scoped provider is deep in a widely-used dependency chain.

Scope propagation chain example

How to mitigate scope propagation overhead:

1
Pass request context as a method argument instead of injecting REQUEST into a service.
2
Keep REQUEST-scoped providers at the outermost layer (controller or a thin adapter service).

What is scope propagation in NestJS and why can it impact performance?

Difficulty: 6/10

Dependency Injection, Request Scope, Performance

When a provider is REQUEST-scoped, every provider that injects it also becomes REQUEST-scoped automatically — this propagates up the entire dependency chain. In high-throughput APIs this causes significant overhead because the full chain must be constructed and torn down on every request instead of reusing singletons.

Scope propagation chain example

How to mitigate scope propagation overhead:

1
Pass request context as a method argument instead of injecting REQUEST into a service.
2
Keep REQUEST-scoped providers at the outermost layer (controller or a thin adapter service).

What is scope propagation in NestJS and why can it impact performance?

What is scope propagation in NestJS and why can it impact performance?

Scenario Questions

Follow-up Questions