Fastify Got Over Thirty-Six Thousand Stars Because Node Teams Wanted Express-Like Clarity With Less Overhead and Fewer Performance Excuses

The click-friendly summary is fair: Fastify got hot because it looked at slow Node API habits and politely suggested that better defaults, schemas, and throughput might actually matter.

GitHub shows Fastify at roughly 36,305 stars, and that number reflects a framework that hit the right backend nerve: familiar enough for Node teams, faster and more structured than the old default patterns.

What Fastify is for

Fastify is strong for:

1. JSON APIs
2. high-throughput Node services
3. schema-driven validation
4. plugin-based backend architecture
5. TypeScript-friendly APIs

It became popular because it treats performance and validation as built-in concerns rather than afterthoughts.

Start a Fastify server

npm init -y
npm install fastify

Example:

const fastify = require("fastify")({ logger: true });

fastify.get("/health", async () => {
  return { ok: true, framework: "fastify" };
});

fastify.listen({ port: 3000, host: "0.0.0.0" });

Why it got adopted

Fastify improved on common Node pain:

1. faster request handling
2. JSON schema validation
3. better plugin structure
4. lower overhead
5. stronger production defaults

That made a lot of “good enough” Express setups look less compelling.

How to deploy it

Node

NODE_ENV=production node server.js

Docker

FROM node:22-alpine
WORKDIR /app
COPY package*.json ./
RUN npm ci --omit=dev
COPY . .
EXPOSE 3000
CMD ["node", "server.js"]

Then:

docker build -t my-fastify-app .
docker run -p 3000:3000 my-fastify-app

What it disrupted

Fastify did not replace every Node backend, but it forced backend teams to confront whether their old routing stack was leaving performance and structure on the table for no good reason.

Sources

• GitHub: fastify/fastify
• Fastify documentation