NestJS

What is it?

NestJS is an opinionated backend framework for Node.js built on top of Express or Fastify. It wraps Node's primitives with TypeScript decorators, modules, providers, and a powerful dependency-injection container, borrowing patterns from Angular and Spring to make large backends navigable.

What does it do?

NestJS handles HTTP routing, validation, authentication, WebSockets, gRPC, GraphQL, queues, scheduled jobs, and microservice messaging under a single consistent programming model. Guards, interceptors, and pipes compose cross-cutting concerns; the built-in testing harness makes unit and e2e tests straightforward.

Where is it used?

NestJS powers production backends at Adidas, Capgemini, Roche, Autodesk, and thousands of startups. It is the default pick for teams that want Node's ecosystem speed but also want enterprise structure — layered services, strict typing, and a clear place for every concern from controllers to repositories.

When & why it emerged

NestJS was released in 2017 by Kamil Mysliwiec to bring structure to the Wild West of Node.js backends. Express gives you a router and nothing else; anything past a toy app requires teams to re-invent the same patterns. NestJS codified those patterns into a batteries-included framework without locking you into a specific HTTP adapter.

Why we use it at Internative

We pick NestJS for backends that a team of 3+ engineers will maintain for 3+ years. Its DI container, module boundaries, and ecosystem (Prisma, TypeORM, BullMQ, Mongoose adapters) map cleanly onto the domain-driven designs we deliver. TypeScript + NestJS is our default when a client says 'we want something more structured than Express but not Java'.