NestJS vs Node.js vs Padrino

NestJS
NestJS

95
96
39
Node.js
Node.js

27K
21K
7.9K
Padrino
Padrino

18
14
8

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.

What is 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.

What is Padrino?

Padrino is a ruby framework built upon the excellent Sinatra Microframework. Padrino was created to make it fun and easy to code more advanced web applications while still adhering to the spirit that makes Sinatra great!

Want advice about which of these to choose?Ask the StackShare community!

Why do developers choose NestJS?
Why do developers choose Node.js?
Why do developers choose Padrino?

Sign up to add, upvote and see more prosMake informed product decisions

What are the cons of using NestJS?
What are the cons of using Node.js?
What are the cons of using Padrino?
    Be the first to leave a con
      Be the first to leave a con

      Sign up to add, upvote and see more consMake informed product decisions

      What companies use NestJS?
      What companies use Node.js?
      What companies use Padrino?

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

      What tools integrate with NestJS?
      What tools integrate with Node.js?
      What tools integrate with Padrino?
        No integrations found

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

        What are some alternatives to NestJS, Node.js, and Padrino?
        AdonisJS
        It is a Node.js Framework which is highly focused on developer ergonomics, stability and confidence.
        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 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
        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.
        ASP.NET
        .NET is a developer platform made up of tools, programming languages, and libraries for building many different types of applications.
        See all alternatives
        Decisions about NestJS, Node.js, and Padrino
        No stack decisions found
        Interest over time
        Reviews of NestJS, Node.js, and Padrino
        Avatar of mihaicracan
        Web Developer, Freelancer
        Review ofNode.jsNode.js

        I have benchmarked Node.js and other popular frameworks using a real life application example. You can find the results here: https://medium.com/@mihaigeorge.c/web-rest-api-benchmark-on-a-real-life-application-ebb743a5d7a3

        How developers use NestJS, Node.js, and Padrino
        Avatar of MaxCDN
        MaxCDN uses Node.jsNode.js

        We decided to move the provisioning process to an API-driven process, and had to decide among a few implementation languages:

        • Go, the server-side language from Google
        • NodeJS, an asynchronous framework in Javascript

        We built prototypes in both languages, and decided on NodeJS:

        • NodeJS is asynchronous-by-default, which suited the problem domain. Provisioning is more like “start the job, let me know when you’re done” than a traditional C-style program that’s CPU-bound and needs low-level efficiency.
        • NodeJS acts as an HTTP-based service, so exposing the API was trivial

        Getting into the headspace and internalizing the assumptions of a tool helps pick the right one. NodeJS assumes services will be non-blocking/event-driven and HTTP-accessible, which snapped into our scenario perfectly. The new NodeJS architecture resulted in a staggering 95% reduction in processing time: requests went from 7.5 seconds to under a second.

        Avatar of Trello
        Trello uses Node.jsNode.js

        The server side of Trello is built in Node.js. We knew we wanted instant propagation of updates, which meant that we needed to be able to hold a lot of open connections, so an event-driven, non-blocking server seemed like a good choice. Node also turned out to be an amazing prototyping tool for a single-page app. The prototype version of the Trello server was really just a library of functions that operated on arrays of Models in the memory of a single Node.js process, and the client simply invoked those functions through a very thin wrapper over a WebSocket. This was a very fast way for us to get started trying things out with Trello and making sure that the design was headed in the right direction. We used the prototype version to manage the development of Trello and other internal projects at Fog Creek.

        Avatar of AngeloR
        AngeloR uses Node.jsNode.js

        All backend code is done in node.js

        We have a SOA for our systems. It isn't quite Microservices jsut yet, but it does provide domain encapsulation for our systems allowing the leaderboards to fail without affecting the login or education content.

        We've written a few internal modules including a very simple api framework.

        I ended up picking Node.js because the game client is entirely in JavaScript as well. This choice made it a lot easier for developers to cross borders between being "client side" game developers and "server side" game developers. It also meant that the pool of knowledge/best practices is applicable almost across the company.

        Avatar of Tony Manso
        Tony Manso uses Node.jsNode.js

        Node.js is the foundation for the server. Using Express.js for serving up web content, and sockets.io for synchronizing communications between all clients and the server, the entire game runs as Javascript in Node.js.

        I don't know how well this will scale if/when I have hundreds of people connected simultaneously, but I suspect that when that time comes, it may be just a matter of increasing the hardware.

        As for why I chose Node.js... I just love JavaScript! My code is all original, meaning that I didn't have to inherit anyone's bad Javascript. I'm perfectly capable of creating my own bad Javascript, thank you! Also, npm rocks!

        Avatar of Tarun Singh
        Tarun Singh uses Node.jsNode.js

        Used node.js server as backend. Interacts with MongoDB using MongoSkin package which is a wrapper for the MongoDB node.js driver. It uses express for routing and cors package for enabling cors and eyes package for enhancing readability of logs. Also I use nodemon which takes away the effort to restart the server after making changes.

        Avatar of NaoLogic
        NaoLogic uses NestJSNestJS

        All the REST API is written in NestJS

        How much does NestJS cost?
        How much does Node.js cost?
        How much does Padrino cost?
        Pricing unavailable
        Pricing unavailable
        Pricing unavailable
        News about NestJS
        More news
        News about Padrino
        More news