When comparing purplecheerio-wave vs Sails.js, the Slant community recommends Sails.js for most people. In the question“What are the best Express.js alternatives?” Sails.js is ranked 5th while purplecheerio-wave is ranked 10th. The most important reason people chose Sails.js is:
Sails.js is built with a focus on building real time communication apps such as chat or multiplayer games, so naturally it has Socket.io extremely well supported.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Auto-generated Documentation
All the documentation for the services is auto-generated based on the configuration files and schema used to specify the services.
Pro Robust and scalable micro services platform
Quickly gets fully functional and secure micro-services started.
Pro Test harness is in built
All the web services specified in the configuration can be tested with an inbuilt harness.
Pro Inbuilt Security
All the web services can be configured with security options that include https
The location of the certificates are configurable.
Other forms of security like authentication can be specified.
Pro Schema Validation for parameters and data payload
The JSON Schema standard compatible input parameters and payloads can be specified and auto validated at run time.
Pro Configurable Route Specification
All routes can be specified in a configuration file and the corresponding classes can be implemented in separate files.
Pro Transparent support for Socket.io
Sails.js is built with a focus on building real time communication apps such as chat or multiplayer games, so naturally it has Socket.io extremely well supported.
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.
Pro JSON API generated for free
Exposes public JSON API for free. No additional routing to be defined. Makes it pretty easy to access data from anywhere.
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 So easy to deploy and lift
Pro Great documentation and structure
Clear documentation and easy to understand. The file structure gives you a way to understand where you can start to develop when you encounter a new Sails project
Cons
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).