NestJS · Senior · Question 11 of 75
Where does Nest's overhead usually matter, and where doesn't it?
- ✓Correct answer: Framework overhead is small compared with I/O; request-scoped providers, heavy interceptor chains and serialization can matter at high RPS
- 2Nest adds no overhead at all
- 3Nest is always several times slower than plain Express for any workload
Explanation
Profile before optimizing. Switching to Fastify, avoiding request scope and using schema-based serialization are common wins.