Get Advice Icon

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

Next.js
Next.js

725
356
+ 1
59
Sails.js
Sails.js

240
193
+ 1
226
Add tool

Next.js vs Sails.js: What are the differences?

Next.js: A small framework for server-rendered universal JavaScript apps *. Next.js is a minimalistic framework for server-rendered React applications; *Sails.js:** Realtime MVC Framework for Node.js. Sails is designed to mimic the MVC pattern of frameworks like Ruby on Rails, but with support for the requirements of modern apps: data-driven APIs with scalable, service-oriented architecture.

Next.js belongs to "Frameworks (Full Stack)" category of the tech stack, while Sails.js can be primarily classified under "Microframeworks (Backend)".

"Automatic server rendering and code splitting" is the top reason why over 9 developers like Next.js, while over 41 developers mention "Data-driven apis " as the leading cause for choosing Sails.js.

Next.js and Sails.js are both open source tools. It seems that Next.js with 38.2K GitHub stars and 4.6K forks on GitHub has more adoption than Sails.js with 20.6K GitHub stars and 1.85K GitHub forks.

According to the StackShare community, Next.js has a broader approval, being mentioned in 79 company stacks & 66 developers stacks; compared to Sails.js, which is listed in 32 company stacks and 12 developer stacks.

What is Next.js?

Next.js is a minimalistic framework for server-rendered React applications.

What is Sails.js?

Sails is designed to mimic the MVC pattern of frameworks like Ruby on Rails, but with support for the requirements of modern apps: data-driven APIs with scalable, service-oriented architecture.
Get Advice Icon

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

Why do developers choose Next.js?
Why do developers choose Sails.js?

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

    Be the first to leave a con
    What companies use Next.js?
    What companies use Sails.js?

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

    What tools integrate with Next.js?
    What tools integrate with Sails.js?

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

    What are some alternatives to Next.js and Sails.js?
    Create React App
    Create React apps with no build configuration.
    Gatsby
    Gatsby lets you build blazing fast sites with your data, whatever the source. Liberate your sites from legacy CMSs and fly into the future.
    Hexo
    Hexo is a fast, simple and powerful blog framework. It parses your posts with Markdown or other render engine and generates static files with the beautiful theme. All of these just take seconds.
    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.
    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.
    See all alternatives
    Decisions about Next.js and Sails.js
    Divine Bawa
    Divine Bawa
    at PayHub Ghana Limited | 13 upvotes 100K views
    Apollo
    Apollo
    Next.js
    Next.js
    styled-components
    styled-components
    React
    React
    graphql-yoga
    graphql-yoga
    Prisma
    Prisma
    MySQL
    MySQL
    GraphQL
    GraphQL
    Node.js
    Node.js

    I just finished a web app meant for a business that offers training programs for certain professional courses. I chose this stack to test out my skills in graphql and react. I used Node.js , GraphQL , MySQL for the #Backend utilizing Prisma as a database interface for MySQL to provide CRUD APIs and graphql-yoga as a server. For the #frontend I chose React, styled-components for styling, Next.js for routing and SSR and Apollo for data management. I really liked the outcome and I will definitely use this stack in future projects.

    See more
    David Ritsema
    David Ritsema
    Frontend Architect at Herman Miller | 7 upvotes 19.6K views
    atHerman MillerHerman Miller
    prismic.io
    prismic.io
    Next.js
    Next.js
    React
    React
    Node.js
    Node.js

    When we started thinking about technology options for our own Design System, we wanted to focus on two primary goals

    1. Build a design system site using design system components - a living prototype
    2. Explore new ways of working to position our technical capabilities for the future

    We have a small team of developers responsible for the initial build so we knew that we couldn鈥檛 spend too much time maintaining infrastructure on the Backend. We also wanted freedom to make decisions on the Frontend with the ability to adapt over time.

    For this first iteration we decided to use Node.js, React, and Next.js. Content will be managed via headless CMS in prismic.io.

    1. Next.js so that we can run React serverside without worrying about server code.
    2. prismic.io so that our content is accessible via API and our frontend is fully independent.
    See more
    Martin Johannesson
    Martin Johannesson
    Senior Software Developer at IT Minds | 10 upvotes 15.1K views
    atIT MindsIT Minds
    AMP
    AMP
    PWA
    PWA
    React
    React
    MongoDB
    MongoDB
    Next.js
    Next.js
    GraphQL
    GraphQL
    Apollo
    Apollo
    PostgreSQL
    PostgreSQL
    TypeORM
    TypeORM
    Node.js
    Node.js
    TypeScript
    TypeScript
    #Serverless
    #Backend
    #B2B

    At IT Minds we create customized internal or #B2B web and mobile apps. I have a go to stack that I pitch to our customers consisting of 3 core areas. 1) A data core #backend . 2) A micro #serverless #backend. 3) A user client #frontend.

    For the Data Core I create a backend using TypeScript Node.js and with TypeORM connecting to a PostgreSQL Exposing an action based api with Apollo GraphQL

    For the micro serverless backend, which purpose is verification for authentication, autorization, logins and the likes. It is created with Next.js api pages. Using MongoDB to store essential information, caching etc.

    Finally the frontend is built with React using Next.js , TypeScript and @Apollo. We create the frontend as a PWA and have a AMP landing page by default.

    See more
    Michael Mota
    Michael Mota
    CEO & Founder at AlterEstate | 4 upvotes 885 views
    Next.js
    Next.js
    Graphene
    Graphene
    GraphQL
    GraphQL
    Django
    Django

    I've been using Django for quite a long time and in my opinion I would never switch from it. My company is currently using Django with REST framework and a part in GraphQL using Graphene. On the frontend we use Next.js and so far everything has been running quite good. I've found limitations but manage to solve it.

    As someone mentioned before, if you are comfortable with Django, don't switch. There's no need since with django you can basically achieve anything. Of course this will depend on the project you want to build, but the scalability and flexibility django can offer it's just out of this world. (Don't want to sound like a fan boy haha but it really is).

    See more
    Interest over time
    Reviews of Next.js and Sails.js
    No reviews found
    How developers use Next.js and Sails.js
    Avatar of Cotalented
    Cotalented uses Sails.jsSails.js

    Sails serves the API backend

    How much does Next.js cost?
    How much does Sails.js cost?
    Pricing unavailable
    Pricing unavailable
    News about Next.js
    More news
    News about Sails.js
    More news