feathers VS SailsJS

At the time of writing, the project has almost 14k stars on GitHub and 26k weekly downloads on npm. Feathers also includes an excellent documentation and is well known for being lightweight and easy to integrate with different databases.

The Feathers framework uses the Socket.IO module so that you receive and give updates in real-time. It also gives you control over your data through sockets, flexible plugins, and a RESTful API and resources.

Feathers - Build prototypes in minutes,

Its always best to work with the stack you are most familiar with. So for me that would

1. FeathersJS for backend [1]

2. Postgres DB

3. Angular for front end + bootstrap

4. Postmark for transactional email (for new signup email verification, forgot password, 2-factor login) [2]

5. Digital Ocean for VPS

6. Ansible for deploying everything

7. Namecheap for domain

8. DNS configuration done on Digital Ocean

Typescript for both Angular and FeathersJS

I've done this a few times and all together it would take me about 3 - 5 hours.

[1] https://feathersjs.com/

GitHub stars: 13515(github.com)

More info‍

In the next version (v5, codename dove) there will be an express-transport and a koa-transport. The koa-transport was [merged earlier this year by daffl](https://github.com/feathersjs/feathers/pull/2315).

Maybe feathersjs is worth to take a look. I started the migration of some internal backends to feathers, coming from plain express and dit not look back. Its a thin service based abstraction layer build on top of express. The next major release will support koa or express under the hood.

This project uses Feathers. An open source web framework for building modern real-time applications.

You could look into https://feathersjs.com/ for server side.

maybe look into sails

Sails.js: Realtime MVC framework for Node.js

Sails.js [0] has been around for years. I don't know how good/bad it is, but there are lot of big name shops using it.

0. https://sailsjs.com/

This is fairly close https://sailsjs.com. I've used it on some side projects and it definitely felt like it made doing node apps faster than doing things by hand.

This amazing framework will help you to build a robust Node.js API. It’s important to know that there are other options to take like Sails, Meteor, Happi, among others. In this case we will use Express which is the most used one but it doesn’t limit you to use other one. You can read the whole Express documentation here

In that realm...Node has Sails.js, for example.

When I started my programming career about 6~7 years ago my first job was about doing PHP applications for a Customs Agency I used to use Yii Framework which is an MVC Framework for PHP. Later on in my journey I ended up using Sails.js which is another MVC framework (this time for node though). In F# we could try to go with dotnet new mvc -lang F# or dotnet new webapp but that would be the least idiomatic F# solution since ASP.NET assumes (at least on net5.0 and lower) that you will use OOP and while that's certainly something that can be done in F# it's not the ideal solution.

I'm a professional front-end web developer & I'm looking for Node's frameworks that are opinionated, easy learning curve & provide many features out of the box. Sometimes, I have narrow my criteria down to Sails & Meteor. I think I'll go with Meteor. Do you have any feedback for me regarding this?

Sails.js