Every few months, a new Node.js framework promises to revolutionize how we build backends. And every few months, I find myself reaching for Express anyway.

It's not that I'm opposed to new toolsβ€”I use Next.js for most frontend work and I'm genuinely excited about what Bun is doing. But when I need to spin up an API quickly, Express gives me exactly what I need without the overhead.

The Case for Boring Technology

Express has been around since 2010. That's ancient in JavaScript years. But that age brings stability, a massive ecosystem of middleware, and documentation for virtually any problem you'll encounter.

When I'm building for clients, I'm not trying to pad my resume with cutting-edge tech. I'm trying to ship reliable software. Express lets me do that without fighting my tools.

When to Look Elsewhere

That said, Express isn't always the answer. For type-safe APIs, I've been enjoying tRPC with Next.js. For high-performance needs, Fastify is worth considering. The right tool depends on the job.

But for a straightforward REST API? Express still gets it done.