Alternatives to NestJS logo

Alternatives to NestJS

AdonisJS, FeathersJS, Koa, LoopBack, and hapi are the most popular alternatives and competitors to NestJS.
2K
2.6K
+ 1
295

What is NestJS and what are its top alternatives?

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.
NestJS is a tool in the Frameworks (Full Stack) category of a tech stack.
NestJS is an open source tool with 53.9K GitHub stars and 6.4K GitHub forks. Here’s a link to NestJS's open source repository on GitHub

Top Alternatives to NestJS

  • AdonisJS
    AdonisJS

    It is a Node.js Framework which is highly focused on developer ergonomics, stability and confidence. ...

  • FeathersJS
    FeathersJS

    Feathers is a real-time, micro-service web framework for NodeJS that gives you control over your data via RESTful resources, sockets and flexible plug-ins. ...

  • Koa
    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. ...

  • LoopBack
    LoopBack

    A highly-extensible, open-source Node.js framework that enables you to create dynamic end-to-end REST APIs with little or no coding. Connect to multiple data sources, write business logic in Node.js, glue on top of your existing services and data, connect using JS, iOS & Android SDKs. ...

  • hapi
    hapi

    hapi is a simple to use configuration-centric framework with built-in support for input validation, caching, authentication, and other essential facilities for building web applications and services. ...

  • 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. ...

  • Django
    Django

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

  • 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. ...

NestJS alternatives & related posts

AdonisJS logo

AdonisJS

181
417
110
A Node.js web framework
181
417
+ 1
110
PROS OF ADONISJS
  • 25
    Laravel like
  • 22
    MVC
  • 21
    Easy to learn
  • 19
    Beautiful code
  • 10
    ORM Mapper
  • 6
    Service Providers
  • 2
    Easy to understand documentation
  • 2
    Fast development
  • 1
    Schema migrations
  • 1
    Typescript
  • 1
    Ace command-line tool
CONS OF ADONISJS
  • 4
    Small community
  • 1
    Poor documentation

related AdonisJS posts

Shared insights
on
NestJSNestJSAdonisJSAdonisJS

I'm using AdonisJS and NestJS in two projects! both frameworks are good!

See more
FeathersJS logo

FeathersJS

157
330
70
Real-time, micro-service web framework for NodeJS
157
330
+ 1
70
PROS OF FEATHERSJS
  • 12
    Real-time
  • 7
    Choose any ORM
  • 7
    Datastore Agnostic
  • 6
    Flexible Plugins
  • 5
    Choose Socketio or Primus
  • 4
    Easy Rest
  • 4
    Isomorphic Services API
  • 4
    Open source
  • 3
    Scalable
  • 3
    Easy to use with Graphql
  • 3
    Documentation
  • 3
    Service-oriented architecture
  • 3
    Data-driven APIs
  • 3
    Uses express, will support other options soon
  • 3
    Advanced Composable Service Middleware called holds
CONS OF FEATHERSJS
    Be the first to leave a con

    related FeathersJS posts

    Recently I have been working on an open source stack to help people consolidate their personal health data in a single database so that AI and analytics apps can be run against it to find personalized treatments. We chose to go with a #containerized approach leveraging Docker #containers with a local development environment setup with Docker Compose and nginx for container routing. For the production environment we chose to pull code from GitHub and build/push images using Jenkins and using Kubernetes to deploy to Amazon EC2.

    We also implemented a dashboard app to handle user authentication/authorization, as well as a custom SSO server that runs on Heroku which allows experts to easily visit more than one instance without having to login repeatedly. The #Backend was implemented using my favorite #Stack which consists of FeathersJS on top of Node.js and ExpressJS with PostgreSQL as the main database. The #Frontend was implemented using React, Redux.js, Semantic UI React and the FeathersJS client. Though testing was light on this project, we chose to use AVA as well as ESLint to keep the codebase clean and consistent.

    See more

    Fontumi focuses on the development of telecommunications solutions. We have opted for technologies that allow agile development and great scalability.

    Firebase and Node.js + FeathersJS are technologies that we have used on the server side. Vue.js is our main framework for clients.

    Our latest products launched have been focused on the integration of AI systems for enriched conversations. Google Compute Engine , along with Dialogflow and Cloud Firestore have been important tools for this work.

    Git + GitHub + Visual Studio Code is a killer stack.

    See more
    Koa logo

    Koa

    563
    457
    12
    Next generation web framework for node.js
    563
    457
    + 1
    12
    PROS OF KOA
    • 6
      Async/Await
    • 5
      JavaScript
    • 1
      REST API
    CONS OF KOA
      Be the first to leave a con

      related Koa posts

      Antonio Kobashikawa
      Web developer | Blogger | Freelancer at Rulo Kobashikawa · | 6 upvotes · 217.9K views

      We are using Node.js and ExpressJS to build a REST services that is middleware of a legacy system. MongoDB as database. Vue.js helps us to make rapid UI to test use cases. Frontend is build for mobile with Ionic . We like using JavaScript and ES6 .

      I think next step could be to use Koa but I am not sure.

      See more
      Paul Whittemore
      Developer and Owner at Appurist Software · | 1 upvote · 187.9K views
      Shared insights
      on
      FastifyFastifyKoaKoaExpressJSExpressJS

      Will base most server-side APIs on Fastify . Smaller, faster, easier. Faster than Koa; and twice as fast as ExpressJS.

      See more
      LoopBack logo

      LoopBack

      280
      545
      33
      Build modern API applications that require complex integrations
      280
      545
      + 1
      33
      PROS OF LOOPBACK
      • 11
        Need a nodejs ReST-API, DB, AAA, Swagger? Then loopback
      • 9
        Easy Database Migration
      • 6
        Code generator
      • 4
        The future of API's
      • 2
        GraphQL
      • 1
        Typescript
      CONS OF LOOPBACK
      • 7
        Community is slow
      • 1
        Backward compatibility

      related LoopBack posts

      Shared insights
      on
      NestJSNestJSJestJestLoopBackLoopBack

      We inherited this project and the backend is using LoopBack v3. I haven't taken a look at Loopback.io v4, but I'm planning to replace it. The reason being is that Loopback v3 documentation is a bit confusing and we are having trouble packaging the build using Webpack. Not to mention, integrating unit tests (latest Jest).

      I still think Loopback is a great tool, but their documentation is really "messy" and hard to navigate through. There's also a constraint of time from our side. So what's the best option out there?

      Should I try upgrading to Loopback v4, or trying other stuff? (i.e. NestJS)

      Thanks!

      See more
      Samuel Olugbemi
      Software Engineer at Payzone UK · | 6 upvotes · 167.2K views
      Shared insights
      on
      LoopBackLoopBackExpressJSExpressJS
      at

      I use LoopBack because it is: * It is truly and Unbelievably Extensible * it is default integrated with OpenAPI (Swagger) Spec Driven REST API * I write lesser codes, because most of the user stories have been covered using the code generation * It's documentation is more compact and well detailed than ExpressJS * It is very easy to learn, hence you can build a basic Rest API App in minutes * It has built in NPM packages required to build my Rest API which saves me time on installation and configuration * The Datasource/Service/Controller concept is just Brilliant (that's mostly all you need to get your app speaking with an External API services) * The support for SOAP and Rest API services is amazing!

      See more
      hapi logo

      hapi

      411
      431
      87
      Server Framework for Node.js
      411
      431
      + 1
      87
      PROS OF HAPI
      • 27
        Makes me Hapi making REST APIs
      • 14
        Simpler than other REST libraries
      • 14
        Configuration
      • 13
        Quality Driven Ecosystem
      • 13
        Modularization
      • 5
        Easy testability
      • 1
        Better validation
      • 0
        Restify
      CONS OF HAPI
        Be the first to leave a con

        related hapi posts

        What is the best way to increase your income as a freelancer in 2019? What frameworks should be the best to learn? React Node.js Docker Kubernetes Sequelize Mongoose MongoDB ExpressJS hapi Based on trends I've picked up a JS full stack. If you need to work under startups you may replace React with Vue.js . If you want to work in outsourcing Angular 2+ may be better.

        What is your opinion?

        See more
        ExpressJS logo

        ExpressJS

        27.1K
        20.8K
        1.6K
        Sinatra inspired web development framework for node.js -- insanely fast, flexible, and simple
        27.1K
        20.8K
        + 1
        1.6K
        PROS OF EXPRESSJS
        • 378
          Simple
        • 333
          Node.js
        • 242
          Javascript
        • 192
          High performance
        • 150
          Robust routing
        • 71
          Middlewares
        • 70
          Open source
        • 57
          Great community
        • 37
          Hybrid web applications
        • 13
          Well documented
        • 9
          Sinatra inspired
        • 9
          Rapid development
        • 7
          Isomorphic js.. superfast and easy
        • 5
          Socket connection
        • 5
          Light weight
        • 4
          Npm
        • 4
          Resource available for learning
        • 3
          Event loop
        • 3
          Callbacks
        • 2
          Data stream
        CONS OF EXPRESSJS
        • 27
          Not python
        • 17
          Overrated
        • 14
          No multithreading
        • 9
          Javascript
        • 5
          Not fast
        • 2
          Easily Insecure for Novices

        related ExpressJS posts

        Simon Reymann
        Senior Fullstack Developer at QUANTUSflow Software GmbH · | 26 upvotes · 3.3M views

        Our whole Node.js backend stack consists of the following tools:

        • Lerna as a tool for multi package and multi repository management
        • npm as package manager
        • NestJS as Node.js framework
        • TypeScript as programming language
        • ExpressJS as web server
        • Swagger UI for visualizing and interacting with the API’s resources
        • Postman as a tool for API development
        • TypeORM as object relational mapping layer
        • JSON Web Token for access token management

        The main reason we have chosen Node.js over PHP is related to the following artifacts:

        • Made for the web and widely in use: Node.js is a software platform for developing server-side network services. Well-known projects that rely on Node.js include the blogging software Ghost, the project management tool Trello and the operating system WebOS. Node.js requires the JavaScript runtime environment V8, which was specially developed by Google for the popular Chrome browser. This guarantees a very resource-saving architecture, which qualifies Node.js especially for the operation of a web server. Ryan Dahl, the developer of Node.js, released the first stable version on May 27, 2009. He developed Node.js out of dissatisfaction with the possibilities that JavaScript offered at the time. The basic functionality of Node.js has been mapped with JavaScript since the first version, which can be expanded with a large number of different modules. The current package managers (npm or Yarn) for Node.js know more than 1,000,000 of these modules.
        • Fast server-side solutions: Node.js adopts the JavaScript "event-loop" to create non-blocking I/O applications that conveniently serve simultaneous events. With the standard available asynchronous processing within JavaScript/TypeScript, highly scalable, server-side solutions can be realized. The efficient use of the CPU and the RAM is maximized and more simultaneous requests can be processed than with conventional multi-thread servers.
        • A language along the entire stack: Widely used frameworks such as React or AngularJS or Vue.js, which we prefer, are written in JavaScript/TypeScript. If Node.js is now used on the server side, you can use all the advantages of a uniform script language throughout the entire application development. The same language in the back- and frontend simplifies the maintenance of the application and also the coordination within the development team.
        • Flexibility: Node.js sets very few strict dependencies, rules and guidelines and thus grants a high degree of flexibility in application development. There are no strict conventions so that the appropriate architecture, design structures, modules and features can be freely selected for the development.
        See more

        Repost

        Overview: To put it simply, we plan to use the MERN stack to build our web application. MongoDB will be used as our primary database. We will use ExpressJS alongside Node.js to set up our API endpoints. Additionally, we plan to use React to build our SPA on the client side and use Redis on the server side as our primary caching solution. Initially, while working on the project, we plan to deploy our server and client both on Heroku . However, Heroku is very limited and we will need the benefits of an Infrastructure as a Service so we will use Amazon EC2 to later deploy our final version of the application.

        Serverside: nodemon will allow us to automatically restart a running instance of our node app when files changes take place. We decided to use MongoDB because it is a non relational database which uses the Document Object Model. This allows a lot of flexibility as compared to a RDMS like SQL which requires a very structural model of data that does not change too much. Another strength of MongoDB is its ease in scalability. We will use Mongoose along side MongoDB to model our application data. Additionally, we will host our MongoDB cluster remotely on MongoDB Atlas. Bcrypt will be used to encrypt user passwords that will be stored in the DB. This is to avoid the risks of storing plain text passwords. Moreover, we will use Cloudinary to store images uploaded by the user. We will also use the Twilio SendGrid API to enable automated emails sent by our application. To protect private API endpoints, we will use JSON Web Token and Passport. Also, PayPal will be used as a payment gateway to accept payments from users.

        Client Side: As mentioned earlier, we will use React to build our SPA. React uses a virtual DOM which is very efficient in rendering a page. Also React will allow us to reuse components. Furthermore, it is very popular and there is a large community that uses React so it can be helpful if we run into issues. We also plan to make a cross platform mobile application later and using React will allow us to reuse a lot of our code with React Native. Redux will be used to manage state. Redux works great with React and will help us manage a global state in the app and avoid the complications of each component having its own state. Additionally, we will use Bootstrap components and custom CSS to style our app.

        Other: Git will be used for version control. During the later stages of our project, we will use Google Analytics to collect useful data regarding user interactions. Moreover, Slack will be our primary communication tool. Also, we will use Visual Studio Code as our primary code editor because it is very light weight and has a wide variety of extensions that will boost productivity. Postman will be used to interact with and debug our API endpoints.

        See more
        Django logo

        Django

        33.3K
        30.1K
        4K
        The Web framework for perfectionists with deadlines
        33.3K
        30.1K
        + 1
        4K
        PROS OF DJANGO
        • 656
          Rapid development
        • 480
          Open source
        • 414
          Great community
        • 369
          Easy to learn
        • 270
          Mvc
        • 224
          Beautiful code
        • 216
          Elegant
        • 199
          Free
        • 196
          Great packages
        • 185
          Great libraries
        • 74
          Restful
        • 72
          Comes with auth and crud admin panel
        • 72
          Powerful
        • 69
          Great documentation
        • 64
          Great for web
        • 51
          Python
        • 39
          Great orm
        • 37
          Great for api
        • 28
          All included
        • 25
          Fast
        • 23
          Web Apps
        • 20
          Used by top startups
        • 20
          Clean
        • 19
          Easy setup
        • 17
          Sexy
        • 14
          Convention over configuration
        • 13
          Allows for very rapid development with great libraries
        • 13
          ORM
        • 12
          The Django community
        • 10
          King of backend world
        • 9
          Great MVC and templating engine
        • 8
          Full stack
        • 7
          Batteries included
        • 7
          Its elegant and practical
        • 6
          Have not found anything that it can't do
        • 6
          Very quick to get something up and running
        • 6
          Cross-Platform
        • 6
          Fast prototyping
        • 6
          Mvt
        • 5
          Zero code burden to change databases
        • 5
          Easy to develop end to end AI Models
        • 5
          Easy Structure , useful inbuilt library
        • 4
          Great peformance
        • 4
          Python community
        • 4
          Map
        • 4
          Easy
        • 4
          Many libraries
        • 4
          Modular
        • 4
          Easy to use
        • 4
          Easy to change database manager
        • 3
          Just the right level of abstraction
        • 3
          Scaffold
        • 3
          Full-Text Search
        • 1
          Scalable
        • 1
          Node js
        • 0
          Rails
        • 0
          Fastapi
        CONS OF DJANGO
        • 25
          Underpowered templating
        • 22
          Autoreload restarts whole server
        • 21
          Underpowered ORM
        • 15
          URL dispatcher ignores HTTP method
        • 10
          Internal subcomponents coupling
        • 8
          Not nodejs
        • 7
          Admin
        • 7
          Configuration hell
        • 5
          Not as clean and nice documentation like Laravel
        • 3
          Bloated admin panel included
        • 3
          Python
        • 3
          Not typed
        • 2
          InEffective Multithreading
        • 2
          Overwhelming folder structure

        related Django posts

        Dmitry Mukhin

        Simple controls over complex technologies, as we put it, wouldn't be possible without neat UIs for our user areas including start page, dashboard, settings, and docs.

        Initially, there was Django. Back in 2011, considering our Python-centric approach, that was the best choice. Later, we realized we needed to iterate on our website more quickly. And this led us to detaching Django from our front end. That was when we decided to build an SPA.

        For building user interfaces, we're currently using React as it provided the fastest rendering back when we were building our toolkit. It’s worth mentioning Uploadcare is not a front-end-focused SPA: we aren’t running at high levels of complexity. If it were, we’d go with Ember.js.

        However, there's a chance we will shift to the faster Preact, with its motto of using as little code as possible, and because it makes more use of browser APIs. One of our future tasks for our front end is to configure our Webpack bundler to split up the code for different site sections. For styles, we use PostCSS along with its plugins such as cssnano which minifies all the code.

        All that allows us to provide a great user experience and quickly implement changes where they are needed with as little code as possible.

        See more

        Hey, so I developed a basic application with Python. But to use it, you need a python interpreter. I want to add a GUI to make it more appealing. What should I choose to develop a GUI? I have very basic skills in front end development (CSS, JavaScript). I am fluent in python. I'm looking for a tool that is easy to use and doesn't require too much code knowledge. I have recently tried out Flask, but it is kinda complicated. Should I stick with it, move to Django, or is there another nice framework to use?

        See more
        Node.js logo

        Node.js

        163.2K
        137.7K
        8.5K
        A platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications
        163.2K
        137.7K
        + 1
        8.5K
        PROS OF NODE.JS
        • 1.4K
          Npm
        • 1.3K
          Javascript
        • 1.1K
          Great libraries
        • 1K
          High-performance
        • 802
          Open source
        • 485
          Great for apis
        • 475
          Asynchronous
        • 420
          Great community
        • 390
          Great for realtime apps
        • 296
          Great for command line utilities
        • 82
          Websockets
        • 82
          Node Modules
        • 69
          Uber Simple
        • 59
          Great modularity
        • 58
          Allows us to reuse code in the frontend
        • 42
          Easy to start
        • 35
          Great for Data Streaming
        • 32
          Realtime
        • 28
          Awesome
        • 25
          Non blocking IO
        • 18
          Can be used as a proxy
        • 17
          High performance, open source, scalable
        • 16
          Non-blocking and modular
        • 15
          Easy and Fun
        • 14
          Easy and powerful
        • 13
          Same lang as AngularJS
        • 13
          Future of BackEnd
        • 12
          Fullstack
        • 11
          Fast
        • 10
          Cross platform
        • 10
          Scalability
        • 9
          Simple
        • 8
          Mean Stack
        • 7
          Great for webapps
        • 7
          Easy concurrency
        • 6
          Typescript
        • 6
          React
        • 6
          Fast, simple code and async
        • 6
          Friendly
        • 5
          Great speed
        • 5
          Easy to use and fast and goes well with JSONdb's
        • 5
          Scalable
        • 5
          Its amazingly fast and scalable
        • 5
          Control everything
        • 5
          Fast development
        • 4
          Isomorphic coolness
        • 4
          Easy to use
        • 4
          It's fast
        • 3
          Great community
        • 3
          Scales, fast, simple, great community, npm, express
        • 3
          TypeScript Support
        • 3
          Sooper easy for the Backend connectivity
        • 3
          Not Python
        • 3
          One language, end-to-end
        • 3
          Easy
        • 3
          Easy to learn
        • 3
          Less boilerplate code
        • 3
          Performant and fast prototyping
        • 3
          Blazing fast
        • 2
          Event Driven
        • 2
          Lovely
        • 2
          Npm i ape-updating
        • 1
          Creat for apis
        • 0
          Node
        CONS OF NODE.JS
        • 46
          Bound to a single CPU
        • 44
          New framework every day
        • 38
          Lots of terrible examples on the internet
        • 31
          Asynchronous programming is the worst
        • 23
          Callback
        • 18
          Javascript
        • 11
          Dependency based on GitHub
        • 11
          Dependency hell
        • 10
          Low computational power
        • 7
          Very very Slow
        • 7
          Can block whole server easily
        • 6
          Callback functions may not fire on expected sequence
        • 3
          Unneeded over complication
        • 3
          Unstable
        • 3
          Breaking updates
        • 2
          No standard approach
        • 1
          Bad transitive dependency management
        • 1
          Can't read server session

        related Node.js posts

        Nick Rockwell
        SVP, Engineering at Fastly · | 44 upvotes · 2.3M views

        When I joined NYT there was already broad dissatisfaction with the LAMP (Linux Apache HTTP Server MySQL PHP) Stack and the front end framework, in particular. So, I wasn't passing judgment on it. I mean, LAMP's fine, you can do good work in LAMP. It's a little dated at this point, but it's not ... I didn't want to rip it out for its own sake, but everyone else was like, "We don't like this, it's really inflexible." And I remember from being outside the company when that was called MIT FIVE when it had launched. And been observing it from the outside, and I was like, you guys took so long to do that and you did it so carefully, and yet you're not happy with your decisions. Why is that? That was more the impetus. If we're going to do this again, how are we going to do it in a way that we're gonna get a better result?

        So we're moving quickly away from LAMP, I would say. So, right now, the new front end is React based and using Apollo. And we've been in a long, protracted, gradual rollout of the core experiences.

        React is now talking to GraphQL as a primary API. There's a Node.js back end, to the front end, which is mainly for server-side rendering, as well.

        Behind there, the main repository for the GraphQL server is a big table repository, that we call Bodega because it's a convenience store. And that reads off of a Kafka pipeline.

        See more
        Conor Myhrvold
        Tech Brand Mgr, Office of CTO at Uber · | 41 upvotes · 5.7M views

        How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:

        Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.

        Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:

        https://eng.uber.com/distributed-tracing/

        (GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)

        Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark

        See more