Need advice about which tool to choose?Ask the StackShare community!
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.
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.
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!
Pros of Next.js
- Automatic server rendering and code splitting46
- Built with React38
- Easy setup32
- Universal JavaScript24
- Zero setup22
- TypeScript22
- Static site generator19
- Simple deployment12
- Incremental static regeneration12
- Just JavaScript11
- Filesystem as an API10
- Frictionless development10
- Well Documented8
- Testing8
- Everything is a function8
- Isomorphic React applications7
- Has many examples and integrations7
- File based routing + hooks built in3
- Deployment2
Pros of Sails.js
- Data-driven apis49
- Waterline ORM47
- Mvc37
- Easy rest32
- Real-time25
- Open source21
- Service-oriented architecture19
- Scalable18
- Convension over configuration10
- Rails-like asset pipeline9
- Node machines and machinepacks9
- Easy route/controller generation7
- Ruby on Rails basic stuff for JS devs6
- CLI for scaffolding project pieces3
- WebSocket support3
- Supportive community1
Sign up to add or upvote prosMake informed product decisions
Cons of Next.js
- Structure is weak compared to Angular(2+)8
Cons of Sails.js
- Waterline ORM5
- Defaults to VueJS4
- Standard MVC0