Recs.
Updated
SpecsUpdate
Pros
Pro ORM that can be plugged into any database, or even custom web service
Sails.js uses Waterline ORM at its backend which means you can store your data in any datastore that you like; all you have to do is make a change to the Waterline adapter, this will allow you to store your data in MySQL/Redis or any other kind of database.
Pro MVC architecture
This could be a huge plus, if you prefer to build your apps using the Model View Controller architecture. Using Sails.js you'll find the task of separating the business logic from the user interface and keeping the interactions between them in a separate layer, extremely easy.
Cons
Con Heavyweight framework with lots of "magic"
While having a lot of features out of the box is great for a small proof of concept, it becomes hugely detrimental in any long-term, production-grade project. One of the major strengths of the Node ecosystem is the ability to pick and choose the tools you need, and Sails forces a ridiculous amount of cruft on developers. The many features the rely on convention also mean a steep learning curve and surprising behaviours that can be difficult to track down.
Con Poor ORM
The built-in Waterline is not well designed and is not suitable for production environments. Populating more than 1 level deep is a nightmare, there is no transaction support, new features/bug fixes are not implemented anywhere near a timely manner (the most requested feature 'deep populate' has been lingering in their github issues list for over a year and a half now).