Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to Safari
Join our communityTop Con
•••Top Pro
•••Top Con
•••
SociableApheleia's Experience
Top Con
•••Top Pro
•••Top Pro
•••Top Con
•••
The Waterline ORM is a bit limited. Associations were finally added after much time and many requests. However, they are (as of 2015) still incomplete. It is not a great ORM for MongoDB. You will very likely be using native MongoDB queries throughout your code more than you might like (for example, in the event you want to use Mongo's $inc to increment something). It's strange that Sails did not simply leverage an existing ORM for their frameworks. Many people fall into the trap of wanting to build their own despite many other existing solutions. It is only then that they realize just how much work goes into an ORM. Fortunately you can bring in whatever packages you want to use with Sails.js. See More
Sails was created to add stronger conventions to Express apps, as well as to have an ORM which could work transparently with both NoSQL and SQL databases. It works on a bit of a higher level on the development stack as Express, and the fact that it's built on top of it means that Sails does not have to deal with the most lower level stuff (such as critical performance and consistency issues across many different modules, like the Express router, cookie parser, body parser, etc...) See More
One of the major benefits that Sails has is performance. But it's not as efficient when starting up. sails lift takes quite a lot of time to execute completely (although it is doing a lot of things behind the scenes - if you run it with the --verbose option, you can see all the different things it's doing). Granted, this would be perfectly fine if you had to execute sails lift just once, but unfortunately every time that you change anything you have to stop and start lift again. See More
CLI builds a very robust and well documented API explorer out of the box and generates OpenAPI 3.0 spec. See More
All the first-party frontend integrations revolve around React, even the Vue ones, which will duplicate quite a bit of vue functionality. You can however use the vanilla-js client library which is not opinionated about frontend frameworks, but lacks several time saving tool integrations such as state management and reactivity. See More
Feathers makes extensive use of modules (which are called Feathers services). These services work like ExpressJS middleware and can be used with app.use('/path', serviceObject). Services help developers keep their applications modular and as minimal as possible, without any unnecessary libraries or bloat. See More
Feather can sync events happening in two different Node processes or even servers in real-time. For example: an event happens in server A, the user connected to server B is instantly notified of that event. This is done through a central Redis or Mongo collection or through a websocket libraries' clustering library. See More
Not only express, but every Node framework has this problem. While there exist plugins and libraries that allow developers to use relational databases in their web applications, they are not very good and usually it's a hassle and more trouble than it's worth to use a relational database with Node and express. See More