Need advice about which tool to choose?Ask the StackShare community!

ExpressJS

31K
23.1K
+ 1
1.6K
NestJS

2.5K
2.8K
+ 1
326
Add tool

ExpressJS vs NestJS: What are the differences?

Key Differences between ExpressJS and NestJS

ExpressJS and NestJS are both popular frameworks used for building web applications in Node.js. While they share some similarities, there are several key differences that set them apart.

  1. Modularity and Scalability: NestJS is designed with a modular architecture in mind, using modules, controllers, providers, and decorators to organize and structure the application. This approach promotes scalability and makes it easier to maintain and extend the codebase. On the other hand, ExpressJS is more flexible and allows developers to have complete control over the application structure, but this can also lead to more complexity when dealing with larger projects.

  2. Dependency Injection: NestJS supports dependency injection out of the box, making it easier to manage dependencies and write unit tests. The framework utilizes TypeScript decorators to define injectable components and automates the process of resolving and injecting dependencies. ExpressJS, on the other hand, does not have built-in support for dependency injection and requires external libraries or custom implementations for managing dependencies.

  3. Decorators and Metadata: NestJS leverages decorators and metadata to define and configure its components. This allows developers to easily annotate classes, methods, and properties with additional functionality. ExpressJS, on the other hand, does not provide a built-in mechanism for decorators and relies more on traditional JavaScript programming patterns for defining routes, middleware, and other components.

  4. Built-in TypeScript Support: NestJS is built with TypeScript in mind and provides seamless integration with the language. The framework leverages TypeScript's static typing, decorators, and advanced features to enhance development productivity and maintainability. While ExpressJS can also be used with TypeScript, it does not provide the same level of integration with the language, requiring developers to manually handle type annotations and bindings.

  5. Convention over Configuration: NestJS follows the principle of "convention over configuration" and enforces a set of conventions and best practices for structuring the application. This can help maintain consistency across projects and simplifies the learning curve for new developers. ExpressJS, on the other hand, is more flexible and allows developers to define their own application structure and conventions.

  6. Ecosystem and Community: While both frameworks have active communities and a large number of plugins and extensions available, ExpressJS has been around for a longer time and has a more mature ecosystem. It has a vast selection of middleware, libraries, and tools built specifically for ExpressJS. NestJS, being a relatively newer framework, is rapidly growing its ecosystem, but might have fewer options compared to ExpressJS.

In Summary, NestJS and ExpressJS have distinct differences in terms of modularity, dependency injection, decorators, TypeScript support, application structure conventions, and ecosystem maturity. The choice between them depends on the specific requirements of the project and the development team's preferences.

Advice on ExpressJS and NestJS
Needs advice
on
DjangoDjangoNestJSNestJS
and
Spring FrameworkSpring Framework

Hi there, I'm deciding the technology to use in my project.

I need to build software that has:

  • Login
  • Register
  • Main View (access to a user account, News, General Info, Business hours, software, and parts section).
  • Account Preferences.
  • Web Shop for Parts (Support, Download Sections, Ticket System).

The most critical functionality is a WebSocket that connects between a car that sends real-time data through serial communication, and a server performs diagnosis on the car and sends the results back to the user.

See more
Replies (4)
Recommends
on
NestJSNestJS

You can use NestJs with microservice architecture.where you can also use socket.io for web socket. you can use MongoDB (For real-time data) & MySQL for customer management.if you don't want to implement websocket.you can use firebase.it gives realtime database & firestore.which can handle millions of connections and scale it up.

See more
Mohammad-Ali A'râbi
Software Engineer at AppTec GmbH · | 5 upvotes · 205.7K views
Recommends
on
NestJSNestJS

I would also go with NestJS. I would say Java is unnecessarily complicated and limited. And Python is not typed. TypeScript is powerful and typed and goes well with NestJS, especially using RxJS.

Django does not enforce backend-frontend separation, which probably was a good thing back in the days, but not anymore. But on the other hand enforces the project structure to you, which I don't like.

See more
Amit Parameshwar
NodeJS Intern at CartRabbit · | 3 upvotes · 561.7K views
Recommends
on
Node.jsNode.js

Just a simple Node.JS app with templating engine for UI can be sufficient for what you want to achieve.

See more
Recommends
on
Spring FrameworkSpring Framework

Spring boot with Spring Security[JWT], Websocket, Thymeleaf or Mustache, and styling with Bootstrap.

See more
Slimane Deb
Needs advice
on
NestJSNestJS
and
Spring BootSpring Boot
in

I am currently planning to build a project from scratch. I will be using Angular as front-end framework, but for the back-end I am not sure which framework to use between Spring Boot and NestJS. I have worked with Spring Boot before, but my new project contains a lot of I/O operations, in fact it will show a daily report. I thought about the new Spring Web Reactive Framework but given the idea that Node.js is the most popular on handling non blocking I/O I am planning to start learning NestJS since it is based on Angular philosophy and TypeScript which I am familiar with. Looking forward to hear from you dear Community.

See more
Replies (2)
Recommends
on
NestJSNestJS

NestJS is an excellent framework (they both are). I would say the fact that you're working with Angular makes NestJS a great match, unless you're splitting front and back end between developers. But even in that case I would still go with NestJS for a new project.

Regarding the single threading point, take a look at PM2 which helps to run Node in multiple processes (we use it with NestJS) https://pm2.keymetrics.io/docs/usage/cluster-mode/

Also regarding web server performance in general this is an interesting post showing how Node with outperform Java in a web situation (be careful though, best to check a few posts to make sure these aren't totally biased benchmarks!): https://www.tandemseven.com/blog/performance-java-vs-node/

See more
Recommends
on
KotlinKotlin

Node.js has only 1 real thread per process; Java JIT will mostly run faster than JS one; So if it happens to be not only I/O... Why do you need most popular, not simply popular? Does Node.js have tech advantages?

See more
Louai Hamada
Full Stack Web Developer · | 7 upvotes · 509.8K views
Needs advice
on
ExpressJSExpressJSNestJSNestJS
and
Node.jsNode.js

I'm planning with a small team to create an application which is a platform for restaurants. I'm on the backend almost alone currently. I'm going to use Node.js for that, and I'm very fond of TypeScript, and I worked before mostly with ExpressJS. The team may get bigger as the application becomes bigger and more successful, so I have the Scalability concern in mind now, and I was considering these options: 1) Use Node+Express+Typescript 2) Use Node+NestJs (which utilizes Typescript by default)

Option 2 is enticing to me because recently I came to love NestJS and it provides more scalability for the project and uses Typescript in the best way and uses Express under the hood. Also I come from an Angular 2 background, which I think is the best frontend framework (my opinion, and I know React quite well), which makes Nest feel familiar to me because of the similarity between Nest and Angular. Option 1 on the other hand uses Express which is a minimalist framework, very popular one, but it doesn't provide the same scalability and brings decision fatigue about what to combine with it and may not utilize Typescript in the best way. Yet, on the other hand, it is flexible and it may be easier to manipulate things in different ways with it. Another very important thing is that it would be easier in my view to hire Node developers with skills in Express than NestJs. The majority of Node developers are much more familiar with JavaScript and Express.

What is your advice and why? I would love to hear especially from developers who worked on both Express and Nest

See more
Replies (6)
Wender Machado
Full Stack Engineer at RG Sistemas · | 9 upvotes · 397.1K views
Recommends
on
NestJSNestJS

I highly recommend NestJS because:

  • It's a framework you already like;
  • Typescript is growing fast, being increasingly adopted in the community;
  • All layers are well defined, not needing to think much about the organization;
  • Great documentation;
  • Nest CLI increases the development speed and keep the pattern;

Only using express and knowing that project can grow, you'ill need to define the structure well so that it doesn't get out of control.

See more
Rhoger Anacleto
Developer at Magrathea Labs · | 5 upvotes · 397.1K views
Recommends
on
NestJSNestJS

Hi Louai,

I am quite sure that you know the answer to your problem. And I am here to help you to follow your arrow. I have worked with the most popular Nodejs frameworks and I can sure you that there's no stack better than NestJS (at all). Typescript is the best thing that happened with Javascript, this is a fact. Ans NestJS make a such wonderful job using all the best Typescript tools. NestJS is the most mature and organized API manager. Its modular dependence injection, the use of DDD, the solid idea of single responsibility, it's unit a and e2e testing support, its documentation is the most incredible work in the world of Nodejs. You won't regret choosing this framework, even if your application grows a lot. If you follow the documentation tips you will be able to create an amazing and organized application.

ps: I am not part of the NestJS team, I am just a guy tired of wasting time with dumb and bad Frameworks and its bad documentations. I find relief in NestJS with all the time it's saved to me, it helped me to improve my job and let me create great things with Nodejs.

See more
Recommends
on
NestJSNestJS

First of all, my experience using either Node.js with Express or NestJS is not wide. I liked NestJS due to it's similarity to Angular, so when you know Angluar and like TypeScript you are going to love NestJS, it will be instantly very familiar and easy to use, it's adds a good structure to the project out of the box and well, it uses TypeScript, which is a more structured language - it's good for scalability. As for performance concern s - NestJS is based on Node, it just brings Angular's modular structure to it, so the question is more about how is the additional layer influences the performance - I cannot answer that.

See more
Recommends
on
NestJSNestJS

I would definitely suggest NestJs over other options because NestJs gives a lot of tooling. it would definitely suggest NestJs over other options because NestJs gives a lot of tooling & it gives a lot of functionality out of the box. If your team worked with angular 2+ then it will really easy to learn.

See more
Recommends
on
NestJSNestJS

Hi, I'm in a similar position, but related to personal projects. After falling in love with few frameworks in the first day and rejecting them in day 2, I started learning nestJS last week. I currently develop personal side projects using cakephp, and I intend to migrate to nest + vue. This week I'm taking a nestJS course in order to be sure that this is what I want by praticing a little. If you didn't do it yet, I suggest you try to code a todo app or a similar example API using nest, so you can "feel" if this is indeed what you want to use in this larger-scale project.

Some of the characteristics that got my attention to nestJS are typescript, a lot of annotations/decorations, an oppinionated approach to organizing the project, nice documentation and discord, and it's evolution at npm trends shows me it's probably not going to vanish or get buggy anytime soon.

See more
Recommends
on
hapihapi

Have you checked out Hapi as an alternative? I'ts not Typescript by default though. If that doesn't seem too interesting, it sounds like you want to go with NestJS :)

See more
Decisions about ExpressJS and NestJS
Radoslaw Fabisiak

We builded Duomly with: BE: Node.JS & Nest.JS & TypeScript & PostgreSQL and FE: React & Sass & Javascript.

The whole of the stack is JS related what helps us to keep development on a track. When building backend we decided to go go for TS & Nest.js because we had experience with Javascript and still wanted to have control over types.

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of ExpressJS
Pros of NestJS
  • 380
    Simple
  • 336
    Node.js
  • 244
    Javascript
  • 193
    High performance
  • 152
    Robust routing
  • 73
    Middlewares
  • 71
    Open source
  • 59
    Great community
  • 37
    Hybrid web applications
  • 16
    Well documented
  • 9
    Sinatra inspired
  • 9
    Rapid development
  • 7
    Socket connection
  • 7
    Isomorphic js.. superfast and easy
  • 5
    Light weight
  • 4
    Resource available for learning
  • 4
    Npm
  • 3
    Event loop
  • 3
    Callbacks
  • 2
    Data stream
  • 54
    Powerful but super friendly to work with
  • 42
    Fast development
  • 40
    Easy to understand documentation
  • 36
    Angular style syntax for the backend
  • 32
    NodeJS ecosystem
  • 31
    Typescript
  • 27
    Its easy to understand since it follows angular syntax
  • 18
    Good architecture
  • 13
    Integrates with Narwhal Extensions
  • 12
    Typescript makes it well integrated in vscode
  • 8
    Graphql support easy
  • 7
    Agnosticism
  • 5
    Easily integrate with others external extensions
  • 1
    Official courses

Sign up to add or upvote prosMake informed product decisions

Cons of ExpressJS
Cons of NestJS
  • 27
    Not python
  • 17
    Overrated
  • 14
    No multithreading
  • 9
    Javascript
  • 5
    Not fast
  • 2
    Easily Insecure for Novices
  • 10
    Difficult to debug
  • 10
    User base is small. Less help on Stackoverflow
  • 5
    Angular-like architecture
  • 3
    Updates with breaking changes
  • 3
    Javascript
  • 1
    Frontend in backend
  • 1
    Unstable

Sign up to add or upvote consMake informed product decisions

- No public GitHub repository available -

What is ExpressJS?

Express is a minimal and flexible node.js web application framework, providing a robust set of features for building single and multi-page, and hybrid web applications.

What is NestJS?

Nest is a framework for building efficient, scalable Node.js server-side applications. It uses progressive JavaScript, is built with TypeScript (preserves compatibility with pure JavaScript) and combines elements of OOP (Object Oriented Programming), FP (Functional Programming), and FRP (Functional Reactive Programming). Under the hood, Nest makes use of Express, but also, provides compatibility with a wide range of other libraries, like e.g. Fastify, allowing for easy use of the myriad third-party plugins which are available.

Need advice about which tool to choose?Ask the StackShare community!

Jobs that mention ExpressJS and NestJS as a desired skillset
What companies use ExpressJS?
What companies use NestJS?
See which teams inside your own company are using ExpressJS or NestJS.
Sign up for StackShare EnterpriseLearn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with ExpressJS?
What tools integrate with NestJS?

Sign up to get full access to all the tool integrationsMake informed product decisions

Blog Posts

Node.jsnpmKubernetes+6
1
1401
JavaScriptGitHubNode.js+29
14
13382
GitHubPythonNode.js+26
29
15937
Jun 19 2015 at 6:37AM

ReadMe.io

JavaScriptGitHubNode.js+25
12
2338
What are some alternatives to ExpressJS and NestJS?
Koa
Koa aims to be a smaller, more expressive, and more robust foundation for web applications and APIs. Through leveraging generators Koa allows you to ditch callbacks and greatly increase error-handling. Koa does not bundle any middleware.
React
Lots of people use React as the V in MVC. Since React makes no assumptions about the rest of your technology stack, it's easy to try it out on a small feature in an existing project.
Flask
Flask is intended for getting started very quickly and was developed with best intentions in mind.
Django
Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design.
Golang
Go is expressive, concise, clean, and efficient. Its concurrency mechanisms make it easy to write programs that get the most out of multicore and networked machines, while its novel type system enables flexible and modular program construction. Go compiles quickly to machine code yet has the convenience of garbage collection and the power of run-time reflection. It's a fast, statically typed, compiled language that feels like a dynamically typed, interpreted language.
See all alternatives