StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Application & Data
  3. Microframeworks
  4. Microframeworks
  5. NestJS vs Total.js

NestJS vs Total.js

OverviewDecisionsComparisonAlternatives

Overview

Total.js
Total.js
Stacks20
Followers62
Votes37
GitHub Stars4.4K
Forks446
NestJS
NestJS
Stacks2.7K
Followers3.0K
Votes326
GitHub Stars73.3K
Forks8.1K

NestJS vs Total.js: What are the differences?

Introduction: NestJS and Total.js are both web application frameworks that can be used to build server-side applications. While they serve a similar purpose, there are some key differences between the two.

  1. TypeScript vs JavaScript: One of the main differences between NestJS and Total.js is the programming language they are built upon. NestJS is built upon TypeScript, which is a superset of JavaScript. TypeScript adds static typing and other features to JavaScript, making it more robust and maintainable. On the other hand, Total.js is built solely on JavaScript.

  2. Modularity and Scalability: NestJS is designed with modularity and scalability in mind. It provides a modular architecture that allows developers to easily separate their application into modules and re-use them across different projects. NestJS also provides powerful dependency injection and module loading capabilities. Total.js, on the other hand, does not have the same level of modularity and scalability features as NestJS.

  3. Support for Express: NestJS is built on top of Express, a popular web framework for Node.js. This means that NestJS can take advantage of all the features and middleware provided by Express. Total.js, on the other hand, has its own custom web server and does not have native support for Express.

  4. Community and Ecosystem: NestJS has a large and active community, with a strong ecosystem of third-party libraries and plugins. This means that developers using NestJS can benefit from a wide range of open-source tools and resources. Total.js, while it also has a community and ecosystem, is generally not as large and active as NestJS.

  5. Documentation and Learning Curve: NestJS has comprehensive and well-documented official documentation, which makes it easier for developers to learn and use the framework. It also has a large number of tutorials, articles, and videos available online. Total.js, on the other hand, has less extensive documentation and fewer learning resources available.

In Summary, NestJS is built on TypeScript, offers modularity and scalability, has native support for Express, has a large community, and offers extensive documentation. Total.js, on the other hand, is built on JavaScript, has limited modularity and scalability features, has its own custom web server, has a smaller community, and has less extensive documentation.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on Total.js, NestJS

juan9222
juan9222

Jul 25, 2020

Needs advice

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.

616k views616k
Comments
Louai
Louai

Full Stack Web Developer

May 15, 2020

Needs adviceonNode.jsNode.jsTypeScriptTypeScriptExpressJSExpressJS

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

549k views549k
Comments
Slimane
Slimane

Jul 9, 2020

Needs adviceonSpring BootSpring BootNestJSNestJSNode.jsNode.js

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.

917k views917k
Comments

Detailed Comparison

Total.js
Total.js
NestJS
NestJS

It is a Framework for Node.js platfrom written in pure JavaScript similar to PHP's Laravel or Python's Django or ASP.NET MVC

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.

Super fast development; Extremely low maintenance costs; Rock solid stability; Incredible performance; Easy scaling
Extensible - Gives you true flexibility by allowing use of any other libraries thanks to modular architecture.; Versatile - An adaptable ecosystem that is a fully-fledged backbone for all kinds of server-side applications.; Progressive - Takes advantage of latest JavaScript features, bringing design patterns and mature solutions to node.js world.
Statistics
GitHub Stars
4.4K
GitHub Stars
73.3K
GitHub Forks
446
GitHub Forks
8.1K
Stacks
20
Stacks
2.7K
Followers
62
Followers
3.0K
Votes
37
Votes
326
Pros & Cons
Pros
  • 5
    Rapid development
  • 5
    Fast
  • 4
    Great support
  • 4
    Low-code tools
  • 3
    Npm
Cons
  • 3
    Lack of source code documentation
  • 2
    Messes up global namespace and default prototypes
  • 2
    Developed as "one man show"
  • 2
    Poor design - 4000 line files
  • 2
    Poor design
Pros
  • 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
Cons
  • 10
    User base is small. Less help on Stackoverflow
  • 10
    Difficult to debug
  • 5
    Angular-like architecture
  • 3
    Javascript
  • 3
    Updates with breaking changes
Integrations
npm
npm
Node.js
Node.js
PostGraphile
PostGraphile
Sentry
Sentry
No integrations available

What are some alternatives to Total.js, NestJS?

Node.js

Node.js

Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices.

Rails

Rails

Rails is a web-application framework that includes everything needed to create database-backed web applications according to the Model-View-Controller (MVC) pattern.

Django

Django

Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design.

Laravel

Laravel

It is a web application framework with expressive, elegant syntax. It attempts to take the pain out of development by easing common tasks used in the majority of web projects, such as authentication, routing, sessions, and caching.

.NET

.NET

.NET is a general purpose development platform. With .NET, you can use multiple languages, editors, and libraries to build native applications for web, mobile, desktop, gaming, and IoT for Windows, macOS, Linux, Android, and more.

ASP.NET Core

ASP.NET Core

A free and open-source web framework, and higher performance than ASP.NET, developed by Microsoft and the community. It is a modular framework that runs on both the full .NET Framework, on Windows, and the cross-platform .NET Core.

ExpressJS

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.

Symfony

Symfony

It is written with speed and flexibility in mind. It allows developers to build better and easy to maintain websites with PHP..

Spring

Spring

A key element of Spring is infrastructural support at the application level: Spring focuses on the "plumbing" of enterprise applications so that teams can focus on application-level business logic, without unnecessary ties to specific deployment environments.

Spring Boot

Spring Boot

Spring Boot makes it easy to create stand-alone, production-grade Spring based Applications that you can "just run". We take an opinionated view of the Spring platform and third-party libraries so you can get started with minimum fuss. Most Spring Boot applications need very little Spring configuration.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase