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

Next.js

2.2K
2.2K
+ 1
211
Sails.js

303
430
+ 1
260
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.

Decisions about Next.js and Sails.js
Lucas Litton
Founder & CEO at Macombey · | 13 upvotes · 193.5K views

Next.js is probably the most enjoyable React framework our team could have picked. The development is an extremely smooth process, the file structure is beautiful and organized, and the speed is no joke. Our work with Next.js comes out much faster than if it was built on pure React or frameworks alike. We were previously developing all of our projects in Meteor before making the switch. We left Meteor due to the slow compiler and website speed. We deploy all of our Next.js projects on Vercel.

See more

Hey guys,

My backend set up is Prisma / GraphQL-Yoga at the moment, and I love it. It's so intuitive to learn and is really neat on the frontend too, however, there were a few gotchas when I was learning! Especially around understanding how it all pieces together (the stack). There isn't a great deal of information out there on exactly how to put into production my set up, which is a backend set up on a Digital Ocean droplet with Prisma/GraphQL Yoga in a Docker Container using Next & Apollo Client on the frontend somewhere else. It's such a niche subject, so I bet only a few hundred people have got a website with this stack in production. Anyway, I wrote a blog post to help those who might need help understanding it. Here it is, hope it helps!

See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Next.js
Pros of Sails.js
  • 30
    Automatic server rendering and code splitting
  • 25
    Built with React
  • 23
    Easy setup
  • 19
    Universal JavaScript
  • 18
    Zero setup
  • 14
    TypeScript
  • 11
    Static site generator
  • 9
    Just JavaScript
  • 8
    Simple deployment
  • 8
    Incremental static regeneration
  • 8
    Frictionless development
  • 7
    Testing
  • 7
    Filesystem as an API
  • 7
    Isomorphic React applications
  • 6
    Everything is a function
  • 5
    Well Documented
  • 4
    Has many examples and integrations
  • 2
    Not nuxt
  • 46
    Data-driven apis
  • 44
    Waterline ORM
  • 34
    Mvc
  • 30
    Easy rest
  • 22
    Real-time
  • 18
    Open source
  • 17
    Service-oriented architecture
  • 16
    Scalable
  • 8
    Convension over configuration
  • 7
    Rails-like asset pipeline
  • 7
    Node machines and machinepacks
  • 5
    Easy route/controller generation
  • 4
    Ruby on Rails basic stuff for JS devs
  • 1
    WebSocket support
  • 1
    CLI for scaffolding project pieces

Sign up to add or upvote prosMake informed product decisions

Cons of Next.js
Cons of Sails.js
  • 5
    Structure is weak compared to Angular(2+)
  • 4
    Not Vue
  • 2
    Is no Angular
  • 2
    Not flutter
  • 1
    Shitty
  • 1
    Not Angular 2
  • 4
    Waterline ORM
  • 2
    Defaults to VueJS

Sign up to add or upvote consMake informed product decisions