Express vs Fastify vs Hono: how I pick a Node.js framework
I've shipped production APIs on all three. Here's when I reach for each one.
Anish Kumar1 min readBackend#nodejs#backend#api
I've built production backends with Express, Fastify, and Hono. They all handle HTTP well, so the choice comes down to where the code will run and what the team needs.
Express — the safe default
Express has the largest ecosystem, and almost every Node.js developer already knows it. It's still my choice for internal tools and teams that need to onboard people quickly.
Fastify — when throughput and schemas matter
Fastify validates requests and serializes responses from JSON schemas, which makes it noticeably faster and catches bad input early. It's a great fit for data-heavy services, like financial reporting APIs.
app.post(
"/reports",
{ schema: { body: ReportInput, response: { 200: ReportOutput } } },
async (req) => generateReport(req.body),
);Hono — when it runs everywhere
Hono is tiny, built on Web Standards, and runs on Node.js, Bun, and edge runtimes. I use it for multi-tenant APIs where I want the same code to deploy anywhere.
const app = new Hono<{ Variables: { tenantId: string } }>();
app.use("/api/*", async (c, next) => {
c.set("tenantId", c.req.header("x-tenant-id") ?? "");
await next();
});My rule of thumb
| Need | Pick |
|---|---|
| Familiar, huge ecosystem | Express |
| Raw performance + validation | Fastify |
| Edge / multi-runtime | Hono |