NestJS vs Express vs Fastify comparison - Performance Comparison

Performance: NestJS vs Express vs Fastify comparison

MEDIUM IMPACT

This comparison affects server response time and throughput, impacting how fast pages or APIs respond to user requests.

Choosing a Node.js backend framework for fast API responses

NestJS

import Fastify from 'fastify';
const app = Fastify();
app.get('/', async (request, reply) => { return 'Hello World'; });
app.listen(3000);

Fastify uses optimized routing and serialization, reducing overhead and improving throughput.

📈 Performance Gainreduces latency by ~30-50% compared to Express, handles more requests per second

Choosing a Node.js backend framework for fast API responses

NestJS

import express from 'express';
const app = express();
app.get('/', (req, res) => res.send('Hello World'));
app.listen(3000);

Express has a simple design but uses middleware and routing layers that add overhead, causing slower response times under load.

📉 Performance Costadds ~10-15ms latency per request under moderate load

Performance Comparison

Framework	Routing Efficiency	Middleware Overhead	Response Speed	Verdict
Express	Moderate	High	Slower	[X] Bad
NestJS	Moderate	Moderate	Moderate	[!] OK
Fastify	High	Low	Fastest	[OK] Good

Rendering Pipeline

Server frameworks handle incoming HTTP requests, route them to handlers, process logic, and send responses. Performance depends on routing efficiency, middleware overhead, and serialization speed.

→Routing

→Middleware Processing

→Response Serialization

⚠️ BottleneckMiddleware and routing layers add CPU overhead and increase response time.

Optimization Tips

1Use Fastify for best raw HTTP performance and throughput.

2Choose NestJS for scalable architecture with moderate performance cost.

3Avoid excessive middleware in Express to reduce latency.

Performance Quiz - 3 Questions

Which Node.js framework generally provides the fastest raw HTTP response times?

A Fastify

B Express

C NestJS

D Koa

DevTools: Network and Performance panels

How to check: Use the Network panel to measure server response times and the Performance panel to record request handling duration.

What to look for: Look for lower server response times and shorter scripting durations indicating faster backend processing.

Practice

1. Which framework is known for providing a structured architecture with decorators and dependency injection?

easy

A. Fastify

B. Express

C. NestJS

D. Koa

Solution

1. Step 1: Understand framework features

   NestJS is designed with a modular architecture, using decorators and dependency injection to organize code clearly.

2. Step 2: Compare with other frameworks

   Express is minimal and flexible but lacks built-in structure; Fastify focuses on speed but not on architectural patterns.

3. Final Answer:

   NestJS -> Option C

4. Quick Check:

   Structured framework = NestJS [OK]

Hint: Structured + decorators = NestJS [OK]

Common Mistakes:

• Confusing Express's flexibility with structure
• Thinking Fastify has built-in dependency injection
• Choosing Koa which is unrelated here

2. Which of the following is the correct way to create a Fastify server instance?

easy

A. const app = fastify();

B. const app = express();

C. const app = new NestFactory();

D. const app = new Koa();

Solution

1. Step 1: Recall Fastify server creation syntax

   Fastify servers are created by calling the fastify() function, not using new keyword.

2. Step 2: Eliminate other options

   Express uses express(), NestJS uses NestFactory.create(), and Koa uses new Koa().

3. Final Answer:

   const app = fastify(); -> Option A

4. Quick Check:

   Fastify instance = fastify() [OK]

Hint: Fastify uses fastify() function call [OK]

Common Mistakes:

• Using new keyword with fastify
• Confusing Express and Fastify syntax
• Using NestFactory directly for Fastify

3. Given the following code snippet, what will be the main difference in performance between NestJS using Express and Fastify?

const app = await NestFactory.create(AppModule, { logger: true });
await app.listen(3000);

medium

A. NestJS with Express is faster due to simpler middleware

B. NestJS with Fastify is faster due to optimized HTTP handling

C. Both have identical performance because NestJS abstracts the server

D. NestJS with Express supports HTTP/2 by default, Fastify does not

Solution

1. Step 1: Understand NestJS adapters

   NestJS can use Express or Fastify under the hood. Fastify is designed for speed and efficiency.

2. Step 2: Compare performance traits

   Fastify has optimized HTTP handling and lower overhead, making it faster than Express in most cases.

3. Final Answer:

   NestJS with Fastify is faster due to optimized HTTP handling -> Option B

4. Quick Check:

   Fastify = faster HTTP handling [OK]

Hint: Fastify is faster than Express in NestJS [OK]

Common Mistakes:

• Assuming Express is faster due to simplicity
• Thinking NestJS removes all performance differences
• Confusing HTTP/2 support defaults

4. You wrote a NestJS app using Fastify adapter but get an error: TypeError: app.listen is not a function. What is the most likely cause?

medium

A. You forgot to import FastifyModule in AppModule

B. Fastify does not support listen method

C. You called app.listen before await

D. You did not use NestFactory.create with Fastify adapter

Solution

1. Step 1: Check how NestJS app is created with Fastify

   To use Fastify, you must pass the Fastify adapter to NestFactory.create().

2. Step 2: Understand error cause

   If you skip the adapter, NestJS defaults to Express, but if you mix Fastify code without adapter, app.listen may be undefined.

3. Final Answer:

   You did not use NestFactory.create with Fastify adapter -> Option D

4. Quick Check:

   Fastify adapter required for app.listen [OK]

Hint: Use Fastify adapter in NestFactory.create [OK]

Common Mistakes:

• Assuming FastifyModule import is enough
• Calling listen without await causes different error
• Thinking Fastify lacks listen method

5. You want to build a high-performance REST API with automatic validation, modular structure, and fast response times. Which combination best fits this requirement?

hard

A. NestJS using Fastify adapter with class-validator and modules

B. Fastify with no framework on top

C. NestJS using Express adapter without validation

D. Express with manual middleware and no structure

Solution

1. Step 1: Identify requirements

   High performance, automatic validation, and modular structure require a framework with features and speed.

2. Step 2: Match frameworks to needs

   Express alone lacks structure and automatic validation; Fastify alone lacks modularity; NestJS provides structure and validation, and Fastify adapter adds speed.

3. Final Answer:

   NestJS using Fastify adapter with class-validator and modules -> Option A

4. Quick Check:

   Structure + validation + speed = NestJS + Fastify [OK]

Hint: Combine NestJS structure + Fastify speed + validation [OK]

Common Mistakes:

• Choosing Express for automatic validation
• Ignoring modularity in Fastify alone
• Using NestJS with Express loses speed advantage