Alternatives to NestJS logo

Alternatives to NestJS

AdonisJS, FeathersJS, Koa, LoopBack, and hapi are the most popular alternatives and competitors to NestJS.
160
165
+ 1
72

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 22.2K GitHub stars and 1.7K GitHub forks. Here’s a link to NestJS's open source repository on GitHub

NestJS alternatives & related posts

AdonisJS logo

AdonisJS

33
21
0
33
21
+ 1
0
A Node.js web framework
    Be the first to leave a pro
    AdonisJS logo
    AdonisJS
    VS
    NestJS logo
    NestJS

    related FeathersJS posts

    Docker
    Docker
    Docker Compose
    Docker Compose
    Jenkins
    Jenkins
    Kubernetes
    Kubernetes
    Amazon EC2
    Amazon EC2
    Heroku
    Heroku
    FeathersJS
    FeathersJS
    Node.js
    Node.js
    ExpressJS
    ExpressJS
    PostgreSQL
    PostgreSQL
    React
    React
    Redux
    Redux
    Semantic UI React
    Semantic UI React
    AVA
    AVA
    ESLint
    ESLint
    nginx
    nginx
    GitHub
    GitHub
    #Containerized
    #Containers
    #Backend
    #Stack
    #Frontend

    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
    Lucas Nogueira
    Lucas Nogueira
    Full Stack developer at Paschoalotto · | 3 upvotes · 21.3K views
    Quasar Framework
    Quasar Framework
    Node.js
    Node.js
    ExpressJS
    ExpressJS
    FeathersJS
    FeathersJS
    MongoDB
    MongoDB
    Netlify
    Netlify

    Quasar Framework Node.js ExpressJS FeathersJS MongoDB Netlify I just love this stack, it's VERY fast to start working on your own stuff instead of internal details.

    See more
    Koa logo

    Koa

    268
    199
    2
    268
    199
    + 1
    2
    Next generation web framework for node.js
    Koa logo
    Koa
    VS
    NestJS logo
    NestJS

    related Koa posts

    Antonio Kobashikawa
    Antonio Kobashikawa
    Web developer | Blogger | Freelancer at Rulo Kobashikawa · | 5 upvotes · 59.6K views
    Node.js
    Node.js
    ExpressJS
    ExpressJS
    MongoDB
    MongoDB
    Vue.js
    Vue.js
    Ionic
    Ionic
    JavaScript
    JavaScript
    ES6
    ES6
    Koa
    Koa

    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
    Paul Whittemore
    Developer and Owner at Appurist Software · | 1 upvotes · 33.3K views
    Fastify
    Fastify
    Koa
    Koa
    ExpressJS
    ExpressJS

    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

    104
    73
    7
    104
    73
    + 1
    7
    Build modern API applications that require complex integrations
    LoopBack logo
    LoopBack
    VS
    NestJS logo
    NestJS

    related LoopBack posts

    Samuel Olugbemi
    Samuel Olugbemi
    Software Engineer at Payzone UK · | 6 upvotes · 23.8K views
    atPayzone UKPayzone UK
    LoopBack
    LoopBack
    ExpressJS
    ExpressJS

    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
    React
    React
    LoopBack
    LoopBack
    Node.js
    Node.js
    ExpressJS
    ExpressJS
    Elasticsearch
    Elasticsearch
    Kibana
    Kibana
    Logstash
    Logstash
    Sequelize
    Sequelize
    Mocha
    Mocha
    Chai
    Chai
    Visual Studio Code
    Visual Studio Code

    React LoopBack Node.js ExpressJS Elasticsearch Kibana Logstash Sequelize Mocha Chai Visual Studio Code are the combo of technologies being used by me to build BestPrice Extension with all its micro-services & Web-based fragments

    See more

    related hapi posts

    Teo Deleanu
    Teo Deleanu
    Developer · | 3 upvotes · 14.8K views
    atAppSeedAppSeed
    React
    React
    Node.js
    Node.js
    Docker
    Docker
    Kubernetes
    Kubernetes
    Sequelize
    Sequelize
    Mongoose
    Mongoose
    MongoDB
    MongoDB
    ExpressJS
    ExpressJS
    hapi
    hapi
    Vue.js
    Vue.js
    Angular 2
    Angular 2

    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
    Node.js logo

    Node.js

    30.9K
    24.7K
    7.9K
    30.9K
    24.7K
    + 1
    7.9K
    A platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications
    Node.js logo
    Node.js
    VS
    NestJS logo
    NestJS

    related Node.js posts

    Nick Parsons
    Nick Parsons
    Director of Developer Marketing at Stream · | 34 upvotes · 291.3K views
    atStreamStream
    Stream
    Stream
    Go
    Go
    JavaScript
    JavaScript
    ES6
    ES6
    Node.js
    Node.js
    Babel
    Babel
    Yarn
    Yarn
    Python
    Python
    #FrameworksFullStack
    #Languages

    Winds 2.0 is an open source Podcast/RSS reader developed by Stream with a core goal to enable a wide range of developers to contribute.

    We chose JavaScript because nearly every developer knows or can, at the very least, read JavaScript. With ES6 and Node.js v10.x.x, it’s become a very capable language. Async/Await is powerful and easy to use (Async/Await vs Promises). Babel allows us to experiment with next-generation JavaScript (features that are not in the official JavaScript spec yet). Yarn allows us to consistently install packages quickly (and is filled with tons of new tricks)

    We’re using JavaScript for everything – both front and backend. Most of our team is experienced with Go and Python, so Node was not an obvious choice for this app.

    Sure... there will be haters who refuse to acknowledge that there is anything remotely positive about JavaScript (there are even rants on Hacker News about Node.js); however, without writing completely in JavaScript, we would not have seen the results we did.

    #FrameworksFullStack #Languages

    See more
    Nick Rockwell
    Nick Rockwell
    CTO at NY Times · | 28 upvotes · 408K views
    atThe New York TimesThe New York Times
    MySQL
    MySQL
    PHP
    PHP
    React
    React
    Apollo
    Apollo
    GraphQL
    GraphQL
    Node.js
    Node.js
    Kafka
    Kafka
    Apache HTTP Server
    Apache HTTP Server

    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
    ASP.NET logo

    ASP.NET

    13K
    344