How does NestJS achieve platform agnosticism between Express and Fastify?

Q: How does NestJS achieve platform agnosticism between Express and Fastify?

// Default — Express adapter (implicit) const app = await NestFactory.create(AppModule); // Fastify adapter import { FastifyAdapter } from '@nestjs/platform-fastify'; const app = await NestFactory.create(AppModule, new FastifyAdapter()); await app.listen(3000); NestJS defines an AbstractHttpAdapter interface that both Express and Fastify implement. Controllers, guards, interceptors, and pipes work identically on both platforms. Only platform-specific code (e.g., using @Req(), @Res() directly) breaks portability. Fastify is significantly faster than Express but has a smaller ecosystem of middleware.

Difficulty: 5/10

adapter pattern, platform abstraction, performance tradeoffs

NestJS wraps the underlying HTTP framework behind an HttpAdapter interface. Core functionality like DI, decorators, and lifecycle is framework-independent. The adapter translates NestJS abstractions to Express or Fastify internals. You switch platforms by passing a different adapter to NestFactory.create() with no application code changes.

Switching from Express to Fastify

How platform agnosticism works:

1
NestJS defines an AbstractHttpAdapter interface that both Express and Fastify implement.
2
Controllers, guards, interceptors, and pipes work identically on both platforms.
3
Only platform-specific code (e.g., using @Req(), @Res() directly) breaks portability.
4
Fastify is significantly faster than Express but has a smaller ecosystem of middleware.

Scenario Questions

0-2 years experience

1You need to add a simple health‑check endpoint to a NestJS app that currently uses Express. How would you switch the project to Fastify without rewriting the controller logic?
2If you accidentally import an Express‑specific middleware in a Nest app that’s running on Fastify, what runtime error would you expect and why?

2-5 years experience

Follow-up Questions

What would you need to change in your code if a library only supports Express request objects?
Can you describe a scenario where switching adapters caused a subtle bug, and how you would debug it?
How does the choice of adapter affect Nest's built‑in exception filters?