Every now and again, most developers when starting a new project, will consider new technologies and reevaluate existing work horses. And this is where the NestJS vs Express question comes up. But first a little context.
Node.js grew from an exciting way to take the V8 engine out of the Chrome web browser to one of the core technologies on the market. It has enabled JavaScript to transcend its original function as a frontend scripting language into a fully serviceable all-purpose programming language.
Many developers (myself included) enjoy the possibility of using the same language for frontend and backend development. Not only is it more comfortable, but it also makes communication easier between team members. If my backend used Laravel or Django as a framework, then I would have to read PHP or Python, respectively, to understand what the code was doing.
Now, don’t take this as an endorsement of having one single programming language to rule them all. I’ll be the first to admit that JavaScript, out of all the options on the market, is the least suitable for that position. Having said that, it’s nice to have the option for a simple and readable language as a foundation for your backend.
Node.js as a backend solution is practically synonymous with Express.js, so much so that people consider it the de facto standard server framework for Node.js. But it’s not the only option out there, and NestJS is a strong contender that aims to fill a similar role in the JavaScript ecosystem.
What Is a Framework?
Before delving into the nitty and gritty, it’s important to understand what is being compared. Both NestJS and Express.js are frameworks, specifically for building backend web applications.
A framework is an opinionated set of tools that serves as a basis or a starting point for creating something. In formal terms: a software framework is an abstraction that provides generic functionality. It can be selectively changed by user-written code, thus providing application-specific software.
In other words, it serves as a generic solution that can be customized by the developer. This is meant to speed up development time by providing basic tools that would otherwise take a lot of time to get up and running. Think of it like this: starting from scratch is like drawing a painting on an empty canvas, and using a framework is like creating the painting from a sketch.
Express.js
What are the implications of being a top-tier dog on the market? Express.js is massive in terms of its community. Finding tutorials, assistance, and useful tricks is a breeze, but its biggest perk is by far the overwhelming amount of plugins ready to spice up Express.js.
You see, Express is what we call a lightweight unopinionated framework.That means, fresh out of the box, it’s as basic as they come, providing very little in terms of functionality. Starting from scratch is going to take more work since a lot of the basic stuff has to be built from the ground up.
In exchange, the developer has more freedom; to go back to our sketch metaphor, you can get more creative when you don’t have to paint within the lines.
Fortunately, if you prefer speed over flexibility, plugins are there to speed up the process, so in a way, if you want the flexibility of a minimalist framework with the option of incorporating more robust solutions, then Express.js development services and the framework is for you.
Having said that, it’s not all sunshine and rainbows. Different plugins might be incompatible with one another, so there is that extra step of trying to figure out if a set of plugins will play nice with one another, or if you are going to have to debug.
NestJS
In many ways NestJS is the opposite of Express. It’s an extremely opinionated framework that adheres to the design paradigm of “convention over configuration.” In other words, we sacrifice flexibility for standardization and speed. NestJS is based on Angular, so as one would expect, it’s meant to be used with TypeScript. (You could still write in Javascript if you prefer.)
TypeScript is a superset of Javascript created by Microsoft, it’s meant to be used as a strictly typed alternative to Javascript that seeks to solve some of the common complaints about the language. When used correctly, it helps write bug-free code without losing the simplicity and readability of common Javascript.
NestJs forces the MVC architecture on the developer, which separates an application into three main logical components: the model, the view, and the controller. It’s one of the most popular architectures on the market, and NestJs offers a plethora of functions for each component.
NestJS vs. Express.js: Pros and Cons
Both frameworks are strong contenders for small projects; it would be a disservice to either product to single out a winner. Having said that, there are a few things to keep in mind.
| NestJS | Express.js | |
|---|---|---|
| Creation Year | 2017 | 2010 |
| Creator | Kamil Myśliwiec (GitHub) | TJ Holowaychuk (GitHub) |
| Documentation | NestJS Documentation | Express.js Documentation |
| Language Type | TypeScript (Compiled Language) | JavaScript (Interpreted Language) |
| Typing | Statically Typed | Dynamically Typed |
| Popularity | Growing rapidly with a strong community support. Widely used in modern web applications and microservices. | Highly popular and widely used for building web applications and APIs. |
| Applications | Web applications, microservices, APIs, real-time applications. | Web applications, RESTful APIs, single-page applications, middleware. |
| Performance | Excellent performance due to the use of TypeScript and compiled nature. | Fast and lightweight, suitable for handling high loads and quick response times. |
| Stability | Stable with regular updates and active development. | Stable and well-established, actively maintained by the community. |
| Learning Curve | Moderate learning curve, especially for developers new to TypeScript and decorators. | Relatively easy to learn, suitable for beginners and experienced developers. |
| Community Support | Active and growing community with extensive documentation and official support. | Large and well-established community with a wealth of online resources. |
| Development Time | Development time can be shorter due to built-in features and decorators. | Quick development process with simple syntax and straightforward architecture. |
| Key Advantages |
|
|
| Key Disadvantages |
|
|
| Famous Companies Using This Technology | Siemens, Accenture, Toyota | IBM, Accenture, Uber |
| Cross-Platform Support | NestJS offers cross-platform support, allowing developers to build applications for various platforms. | Express.js is platform-independent and can be used on different operating systems. |
NestJS is the foolproof solution. If you are a developer looking to dip your toes into the backend for the first time, or if your team is just starting, having the safeguards of an opinionated framework is a welcome asset. With NestJS you are going to learn about one of the most popular architectures in web development, and you are also learning the basics of the massively popular Angular. That’s killing two birds with one stone.
Having said that, NestJS is also fantastic for a pro. If the project you are going to be working on fits the NestJS mold, you’ll be saving dozens of hours of development time.
On the opposite side, there is a reason why Express.js is so popular. The amount of flexibility is hard to match, and it’s perfect for teams that want to experiment or try out nonstandardized solutions. Light frameworks like Express.js foster creativity and are a perfect fit for projects that require thinking outside of the box.
Performance-wise, both are equally capable, and as for scalability, while NestJS is a bit easier to scale, Express can offer the same if not more with a bit of work.
NestJS is like one of those Lego models of a Death Star: if you want to build a Death Star, then it’s the perfect solution for you. On the other hand, if you want to build a custom vehicle, you are better served by a generic Lego set, and that’s what Express.js is for.
