FeathersJS vs Sails.js: What are the differences?
What is FeathersJS? Real-time, micro-service web framework for NodeJS. 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.
What is 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.
FeathersJS and Sails.js can be primarily classified as "Microframeworks (Backend)" tools.
"Datastore Agnostic" is the top reason why over 2 developers like FeathersJS, while over 41 developers mention "Data-driven apis " as the leading cause for choosing Sails.js.
FeathersJS and Sails.js are both open source tools. Sails.js with 20.6K GitHub stars and 1.85K forks on GitHub appears to be more popular than FeathersJS with 11K GitHub stars and 473 GitHub forks.
TestLegends, HYPH, and Giguana are some of the popular companies that use Sails.js, whereas FeathersJS is used by DeliciousDB, Datafactor GmbH, and Koola. Sails.js has a broader approval, being mentioned in 32 company stacks & 12 developers stacks; compared to FeathersJS, which is listed in 19 company stacks and 14 developer stacks.
What is FeathersJS?
What is Sails.js?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using FeathersJS?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
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.