When you’re building a single service, Express feels effortless minimal setup, total control. But once your system grows into multiple moving parts, that freedom starts to cost you structure. That’s where NestJS shines. Designed with modularity, dependency injection, and TypeScript at its core, NestJS provides the structure large, distributed systems need. Its microservices package supports communication over Kafka, RabbitMQ, Redis, MQTT, and more out of the box. Each module can scale independently, integrate cleanly, and stay consistent across teams. That’s why many companies use NestJS to build event-driven or microservice-based architectures that remain maintainable over time. It’s open source and actively maintained here: 🔗 github.com/nestjs/nest When you move from a single service to a distributed system, NestJS doesn’t just simplify, it scales with you. . . . #software #fullstack #javascript #nodejs #express #nestjs #softwarearchitecture #systemdesign #microservice #monolith
I don't know much about nestjs, but express is not messy either. It all make sense when you understand the concept & flow
After the first time I built an API using NestJS and TypeORM , I will fight hard to make sure that Nest is in any future server side Typescript projects I'm a part of.
NestJS is cool, you should try it. It's like giving your code a backbone. Does it handle the chaos of scaling well? What's your experience with it?
After Node.js with Express.js I am keen to learn typescript and next as well, but the thing is that I don't know what time is the best to put your skills to work
Our thoughts exactly! thats why we build the first ai automation framework based on NestJS. We would be honored for you to try it and share your thoughts. https://app.loopstack.ai
NestJS is a good framework well, but not is good start ‘cause is a higher level of abstraction and if you don’t understand behind the scenes, you're learning a higher level abstraction an d sometimes you need to know the things out of box.
i think its developer fault to not write clean code when they are using express, not express fault
express and nest are just tools ... misusing it will lead to hard to maintain project
When you start to build distributed systems you will start to write pure JS code with no or minimal dependencies.
Express was always intended to be a foundational framework. A framework for building higher level abstractions. It's fine for confined use-cases but you can't really compare it at depth to something more opinionated. I think the image you've used there is a bit misleading. NestJS is just one route you can take but as you can see in the image above it has a somewhat confusing topology for middle tier services. We're in the habit these days of building modular monoliths with telemetry that helps us refine our domains and scale accordingly. If something needs to be isolated and scaled independently it can easily be broken out. That's where my arguments around using Express alone would stem from.